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

# Close Vault

Close spends a debt-free **Cleared** vault and returns its remaining BTC to the user's selected destination, after the Bitcoin transaction fee. It ends the vault instead of creating a successor vault.

<figure><img src="https://3381100491-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZOzQaoopNKdgkYJmuRPt%2Fuploads%2Fgit-blob-fbb9fc70d80c47336addcea3cf69d561a5bde886%2Fgitbook-close-vault.png?alt=media" alt="A Close transaction spends a Cleared vault with zero UNIT debt, returns remaining BTC to the user after fees and includes Cleared protocol metadata."><figcaption><p>Close a cleared vault</p></figcaption></figure>

### Requirements

* The input must be an unspent vault whose accepted state is Cleared. If debt remains, complete [Repaying UNIT](https://docs.ducatprotocol.com/how-ducat-works/vaults/repaying-unit.md) first.
* The owner and an authorised guardian group must sign the cooperative spend.
* The return output must meet the builder's applicable output constraints after fees.

Close is one Bitcoin transaction. The documented builder pays its fee from the vault input, returns BTC and includes Cleared protocol metadata. It does not consume UNIT, create a Rune burn or request an oracle price contract.

### Guardian participation

Debt-free does not mean independently spendable by the owner. Clearing the debt removes the liquidation paths, but the cooperative user-and-guardian condition remains. Guardian availability is therefore still required to close the vault.

Track the close transaction through confirmation and verify the destination and returned amount. A signed close request alone does not prove that the BTC has reached the destination.
