> 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/guardian-network.md).

# Guardian Network

Guardians are the protocol's co-signers. They validate proposed vault operations and provide the signatures that authorise the guardian side of Bitcoin spending conditions.

### FROST and guardian keys

FROST allows a threshold of participants to produce one Schnorr signature for a guardian public key without any one participant holding the complete signing key. The threshold and operator set are deployment-specific.

An on-chain guardian key represents a signing group. Multiple shares of that key are not multiple independent vault spending keys. A vault may also reference more than one authorised guardian key; its script contains the corresponding spending paths.

### Authorisation

For normal vault actions, the cooperative script requires both the user's signature and a guardian signature. For liquidation, a guardian signature and a matching oracle preimage authorise the spend without a new signature from the liquidated borrower.

Before signing, guardian software checks the transaction's protocol identity, authorised participants, price commitments, collateral and debt accounting, and action-specific rules. FROST supplies the signature; it does not itself decide whether those economic rules are satisfied.

### Control and availability

The normal spending path does not let guardians spend alone, but users also cannot spend through it alone. Guardian refusal or unavailability can therefore delay vault updates and closure.

The liquidation path introduces a different dependency: a valid guardian signature combined with the required oracle preimage can spend the collateral without the borrower. Describe this as a conditional spending arrangement, not an absence of guardian control.

Clearing a vault's debt removes its liquidation hashes in the documented construction. [Closing](/how-ducat-works/vaults/close-vault.md) that cleared vault still uses cooperative user/guardian signing.

### Transparency

Anyone with the required Bitcoin history and protocol configuration can use a [Ducat validator](/how-ducat-works/validators.md) to reconstruct vault state and UNIT accounting. Independent validation helps identify invalid protocol activity; it cannot reverse a Bitcoin transaction whose script conditions were satisfied.

The [trust assumptions](/trust-assumptions/overview.md) describe guardian availability, oracle compromise and the limits of independent validation.
