# Admin-reserved and Prohibited Key Derivation Protocols Ty Everett () ## Abstract We define a set of reserved protocol namespaces that can be employed by clients utilizing the [BRC-43](/key-derivation/0043.md) invoice numbering scheme to be set aside for administrative and internal use by the client software itself. This enables client software to manage its own internal state without the risk that application software will utilize the same internal protocols. ## Motivation [BRC-43](/key-derivation/0043.md)[1](#footnote-1) defines an open-ended way to create protocols and systems of interaction within a [BRC-42](/key-derivation/0042.md)[2](#footnote-2) key derivation architecture. However, client software implementing the [BRC-43](/key-derivation/0043.md)[1](#footnote-1) invoice numbering scheme needs a way to manage its own internal state, encrypt data and perform administrative tasks like permissions management without interference from applications. With this specification, we define a list of namespaces in which applications are never allowed to derive keys, and any client that follows this specification will refuse requests made by applications to perform these operations. ## Specification We reserve the following protocol IDs for the administrative and internal use of clients, no matter the security level: * Any protocol ID that starts with `admin` ## References * 1: [BRC-43](/key-derivation/0043.md): Security Levels, Protocol IDs, Key IDs and Counterparties * 2: [BRC-42](/key-derivation/0042.md): BSV Key Derivation Scheme (BKDS) --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://bsv.brc.dev/key-derivation/0044.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.