> 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/how-ducat-works/architecture.md).

# Architecture

Ducat combines Bitcoin settlement with guardian authorisation and independent metaprotocol validation.

<figure><img src="https://3381100491-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZOzQaoopNKdgkYJmuRPt%2Fuploads%2Fgit-blob-087881e34f382ebab5ff92206705a3b50efc88bb%2Fgitbook-architecture.png?alt=media" alt="Oracle commitments and Anchor configuration support wallet construction, guardian signing, Bitcoin settlement and validator reconstruction of vault state and active UNIT balances."><figcaption><p>Protocol architecture</p></figcaption></figure>

### Bitcoin spending conditions

An indebted vault has two kinds of Taproot script path:

* **Cooperative:** the vault owner's signature and an authorised guardian signature.
* **Liquidation:** an authorised guardian signature and a preimage matching one of the vault's oracle threshold hashes.

A guardian signature may be produced by several operators jointly using FROST. It is still the guardian side of the spending condition; the cooperative path also requires the user's separate signature.

Bitcoin checks these cryptographic conditions. It does not read the oracle's external market data or enforce the collateral ratio as a Bitcoin consensus rule.

### Guardian checks

Before co-signing, guardians validate the requested transaction, its inputs and outputs, applicable protocol parameters, oracle commitments, and the action's collateral and debt changes. For repayment, the linked burn must account for the debt reduction. For liquidation, the preimage and settlement must satisfy the applicable rules.

Guardian participation is a liveness dependency: a user cannot complete a cooperative vault spend without a valid guardian signature.

### Independent validation

Validators parse the confirmed Bitcoin history and reconstruct vault state and UNIT accounting. They can reject a transaction as a Ducat operation even if Bitcoin accepts the underlying transaction. That rejection does not undo a confirmed Bitcoin spend.

Strict signing checks and confirmed replay have different purposes. Replay retains certain economic-policy diagnostics alongside the observed state, while structural and authentication checks still apply. See [Validators](https://docs.ducatprotocol.com/how-ducat-works/validators.md) before treating an indexed transaction as proof of compliance with every current signing rule.

The [Vault State](https://docs.ducatprotocol.com/how-ducat-works/vault-state.md) and [Supply Control](https://docs.ducatprotocol.com/trust-assumptions/supply-control.md) pages describe what validators reconstruct.

### Future designs

Research into different spending constructions or future Bitcoin capabilities may reduce reliance on guardians. Such mechanisms are not an exit path provided by the spending conditions documented here.
