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

# Validators

A Ducat validator reconstructs protocol state from Bitcoin transactions using the selected anchor and applicable protocol profile. Users may operate their own validator or use a service, but a generic Rune balance does not establish whether that balance is active UNIT under Ducat's rules.

### What is validated?

* The anchor, recognised Rune mint commitments and authorised keys.
* Protocol accounts used for UNIT issuance.
* Vault creation, borrowing, repayment, deposits, withdrawals, closure and liquidation.
* The relationship between spent vaults, successor outputs, debt balances and price commitments.
* UNIT quantities classified as reserve, active or burned.

Vault metadata uses `OP_RETURN OP_8`; Rune transfers use the Runes `OP_RETURN OP_13` encoding. These markers identify candidate data, not proof that an action is valid. Validation also requires the relevant inputs, history, signatures and protocol context.

### Active UNIT

The ledger distinguishes reserve UNIT from active UNIT. An accepted Open or Borrow action activates the borrowed quantity. Moving reserve runes to another address does not by itself activate them.

Repayment requires a linked, accepted burn of active UNIT. The validator checks that the vault's debt reduction is supported by that burn. See [Supply Control](https://docs.ducatprotocol.com/trust-assumptions/supply-control.md).

### Vault state

The BTC output value supplies the gross collateral amount. Compact vault metadata supplies debt and authenticated oracle commitments. Validators combine these with historical context to calculate ratios and track ownership and successor outputs.

For details, see [Vault State](https://docs.ducatprotocol.com/how-ducat-works/vault-state.md).

### Signing policy and confirmed replay

The implementation distinguishes strict validation of a proposed action from reconstruction of confirmed history.

* **Before signing:** collateral floors, liquidation settlement and other applicable economic-policy checks can reject a proposal.
* **During confirmed replay:** structural, authentication, debt-accounting and Bitcoin consensus checks still apply. Certain economic-policy differences are recorded as diagnostics while preserving the observed transition.

For example, liquidation replay can retain settlement or ratio diagnostics instead of pretending that the confirmed transfer did not occur. An indexed vault or active balance is therefore not, by itself, proof that every current signing-policy check passed. Inspect the action's policy diagnostics and historical profile as well as its balances.

This distinction keeps historical accounting separate from permission to sign a new transaction. It does not make policy violations safe or reverse their effects.

### Limits and governance

A validator can classify a Bitcoin transaction as invalid under Ducat rules; it cannot undo that transaction or recover spent collateral. Bitcoin validity and Ducat validity are different checks.

The schema contains governance-related terms and version identifiers. This page does not represent proposal counting or DUCAT voting as an operational feature of the documented deployment. See [Governance](https://docs.ducatprotocol.com/governance/governance.md).
