> For the complete documentation index, see [llms.txt](https://docs.stability.nexus/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stability.nexus/stablecoins/djed-overview/who-is-the-issuer.md). # Who is the issuer? A fully autonomous stablecoin smart-contract is like a self-driving car. Asking who is issuing the stablecoins is like asking who is driving a self-driving car. The answer is the contract itself in the former case and the car itself in the latter case. Considering the developers of an autonomous stablecoin smart-contract to be the issuers of the stablecoin would be as incorrect as considering the manufacturers of a self-driving car to be drivers of the car. Note that full autonomy and immutability are required for this interpretation. If there are entities capable of interfering with the execution of the smart contract, including by having the power to upgrade it and change its code, then those entities ought to be considered issuers, similarly to how anyone capable of overriding a self-driving car's driving algorithms ought to be considered a driver. --- # 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.stability.nexus/stablecoins/djed-overview/who-is-the-issuer.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.