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

# Vaults

A vault holds BTC collateral and records the UNIT debt associated with it. Its current state is a Bitcoin UTXO plus the spending conditions and protocol history needed to interpret that output. An update spends the current vault and creates its successor.

Ordinary updates require both the owner's signature and a guardian-group signature. An encumbered vault also has liquidation paths requiring a guardian-group signature and an oracle threshold preimage. The owner does not have a unilateral spending path in the documented implementation.

### Actions and transaction stages

| Action                                                                                  | Bitcoin transactions in the vault flow | Result                                                               |
| --------------------------------------------------------------------------------------- | -------------------------------------- | -------------------------------------------------------------------- |
| [Open Vault](https://docs.ducatprotocol.com/how-ducat-works/vaults/open-vault.md)       | Issue, then vault                      | Creates a collateralised vault and delivers newly active UNIT.       |
| [Deposit BTC](https://docs.ducatprotocol.com/how-ducat-works/vaults/deposit-btc.md)     | One vault update                       | Increases collateral without increasing debt.                        |
| [Borrow UNIT](https://docs.ducatprotocol.com/how-ducat-works/vaults/borrow-unit.md)     | Issue, then vault                      | Increases debt and delivers additional active UNIT.                  |
| [Repaying UNIT](https://docs.ducatprotocol.com/how-ducat-works/vaults/repaying-unit.md) | Burn, then vault                       | Reduces debt; full repayment produces a Cleared vault.               |
| [Withdraw BTC](https://docs.ducatprotocol.com/how-ducat-works/vaults/withdraw-btc.md)   | One vault update                       | Reduces collateral while preserving the required remaining position. |
| [Close Vault](https://docs.ducatprotocol.com/how-ducat-works/vaults/close-vault.md)     | One close transaction                  | Spends a Cleared vault and returns the remaining BTC after fees.     |

These counts describe the protocol action, not unrelated wallet funding or consolidation transactions. Two-transaction flows are linked through spent outputs. They are not an atomic Bitcoin consensus operation: the child depends on the parent, and each transaction has its own broadcast and confirmation status.

### Borrowing capacity

The published UNIT/USD parameters require a minimum 160% ratio for borrowing. The calculation uses **net collateral**, excluding the required minimum retained in the vault output:

```
net_BTC = (vault_sats - minimum_vault_sats) / 100,000,000
maximum_total_UNIT_debt = net_BTC × authenticated_BTC_USD_price / 1.60
additional_borrowing_capacity = maximum_total_UNIT_debt - existing_UNIT_debt
```

For example, $10,000 of net collateral supports up to 6,250 UNIT of total debt before rounding and any reduction in collateral to pay fees. This is not a promise that a vault remains above 160% after market prices change.

Depositing collateral or repaying debt can improve a position below the borrowing floor. The exact output, oracle commitments and other action checks must still be valid. A pending recovery transaction does not reserve the vault against a competing liquidation.

### Debt and ownership

UNIT received by the borrower can circulate independently of the vault. Sending UNIT to another wallet does not transfer or repay the vault's debt. Repayment requires the protocol's burn-and-update flow.

A full repayment removes the debt and liquidation commitments but retains the cooperative spending requirement. Use Close to release the remaining BTC. See [Vault State](https://docs.ducatprotocol.com/how-ducat-works/vault-state.md) for stored fields and [Protocol Parameters](https://docs.ducatprotocol.com/how-ducat-works/protocol-parameters.md) for the dated parameter reference.
