> For the complete documentation index, see [llms.txt](https://docs.blerify.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.blerify.com/trust-registry/did-method/did-controller.md). # DID Controller Blerify DID Controller is a set of contracts designed to administer [DIDs](https://www.w3.org/TR/did-core/) whose [DID Registry](https://www.w3.org/TR/did-core/#dfn-verifiable-data-registry) is built on top of a blockchain network (e.g. [lac](https://github.com/lacchain/lacchain-did-registry/tree/master?tab=readme-ov-file#lacchain-did-method),[lac1](https://github.com/lacchain/LACChain-identity-contracts/blob/master/DidSpecs.md) and [ethr](https://github.com/decentralized-identity/ethr-did-resolver/blob/master/doc/did-method-spec.md) DID methods). Setting a contract instance of the DID Controller as the controller of a specific DID will allow to manage the [services](https://www.w3.org/TR/did-core/#services) and [verifications methods](https://www.w3.org/TR/did-core/#verification-methods) associated to such DID. ### **Terminology:** * Admin * Manager * Assignor ### **Capability:** Refers to a privilege inherently owned or granted. Such Capabilities are: * Assertion * Authentication * Key Agreement * Capability Invocation * Capability Delegation * Services ### **Base Considerations:** There are three main levels of control: * Admin level: Any actor with this privilege has full control over a particular identity instance living on a specified DID Registry, can do any action * Capability Manager level: Any actor with this privilege can only assign pre defined roles for [capabilities](https://github.com/BlerifyPlatform/did-controller/blob/main/docs/functional/DIDController.md#capability) or custom ones to "assignors" * Assignor level: Actor assigned with this privilege can just call the DID Registry through the DID Controller contract and just add a [verification relationship](https://www.w3.org/TR/did-core/#verification-relationships) or a [service](https://www.w3.org/TR/did-core/#services) to a user ### **Smart Contract Considerations:** * Due to the roles feature that DID Controller has it allows multiple agents controlling a particular DID Registry at the same time. * Due to gas limitations, full verification of the payload to be relayed is not made. The contract just resolves the type of property to be added to the DID Document (verification method,service, controller management action) and determines whether the agent calling the contract is authorized to perform such action. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## 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, and the optional `goal` query parameter: ``` GET https://docs.blerify.com/trust-registry/did-method/did-controller.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.