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

# Liquidations

Liquidation relies on both oracle release of a threshold preimage and guardian authorisation of the resulting transaction. Neither component alone is the full spending condition.

### Public commitment and secret preimage

The oracle signs a price contract containing the base price, timestamp, threshold price, network and threshold hash. The vault records this data, and its liquidation script includes the hash.

The hash is public. The threshold preimage is intended to remain secret until release. Once revealed, it is available to others and appears in the liquidation witness; secrecy cannot be restored by a later price recovery.

A matching preimage demonstrates knowledge of the committed key. Bitcoin does not determine whether releasing that key was justified by market prices.

### Guardian checks

A guardian group must still authorise the liquidation. Fresh signing checks include the target's threshold eligibility at the authenticated settlement price, debt conservation, collateral allocation, the protocol reserve payment and the resulting liquidator-vault ratio.

These checks are implemented in software. The hashlocked Bitcoin script does not contain a complete settlement formula. Guardian compromise or incorrect signing can therefore have consequences that an independent validator cannot undo.

A guardian may decline to sign when its checks fail. Do not assume an unspecified alternate price feed can replace the oracle identity or commitment required by the protocol.

### Multiple oracles and privacy

The current vault format can contain several oracle commitments, but the liquidation leaves are alternatives. One matching committed preimage plus a guardian-group signature can satisfy a path; it is not an all-oracle quorum.

An oracle request need not contain the vault's identity. That does not prevent correlation with public commitments, service requests or relay data. The protocol does not guarantee that an oracle stores no history.

Operational separation between the oracle and guardian group can reduce shared failure risk. It is not a cryptographic guarantee against collusion.

### Delay and market risk

Failure to release a required preimage, guardian unavailability, insufficient liquidator capital or delayed Bitcoin confirmation can postpone liquidation. Rapid BTC price changes can create a collateral shortfall before settlement.

Liquidation transfers debt; it does not immediately buy and burn UNIT. The liquidator remains exposed until repayment and any eventual close. A tax rebate reduces the reserve deduction but does not create external collateral or guarantee a profitable exit.

See [Basic Mechanics](https://docs.ducatprotocol.com/liquidations/basic-mechanics.md) and [Profit Settlement](https://docs.ducatprotocol.com/liquidations/profit-settlement.md) for the action and accounting rules.
