> For the complete documentation index, see [llms.txt](https://docs.ducatprotocol.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ducatprotocol.com/trust-assumptions/overview.md). # Overview UNIT and Ducat operate as a meta-protocol, enforced by the MPC network and verifiable by anyone running a Ducat Node. * MPC Network: Functions similarly to Bitcoin miners by enforcing protocol rules. * Ducat Node: Acts like a Bitcoin node, enabling anyone to verify transactions and ensure protocol compliance. Ducat aims to build a protocol that remains closely aligned with Bitcoin, using existing concepts to establish a stablecoin that is: * A stable, dollar-pegged representation of Bitcoin * Secured by Bitcoin, backed by Bitcoin, and operating entirely within Bitcoin This design involves several trade-offs, particularly in areas such as: * Asset management * Supply control * Liquidations ### Trusted Systems DUCAT relies on two core systems: * Oracles: Maintain the soft peg to the US dollar * MPC Network: Enforces protocol rules and validates transactions These systems are supported by users running independent validators and reinforced by community consensus. Valid transactions are determined solely by data secured on the Bitcoin network. ### Resilience and Recovery Even in the event of a complete system compromise: * The network could restart independently with a new set of guardians * Invalid transactions could be ignored, restoring protocol integrity without external intervention This structure ensures Ducat remains robust, transparent, and faithful to Bitcoin’s decentralised ethos. --- # 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.ducatprotocol.com/trust-assumptions/overview.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.