OP VAULT - Revision history

NotATether: Add Vault flow and Status sections

2026-09-13T07:29:26Z

Add Vault flow and Status sections

← Older revision		Revision as of 07:29, 13 September 2026
Line 1:		Line 1:
	'''OP_VAULT''' was a proposed pair of [[Taproot]] script opcodes defined in [https://github.com/bitcoin/bips/blob/master/bip-0345.mediawiki BIP 345]. Together with CHECKTEMPLATEVERIFY (CTV, BIP 119), the opcodes were intended to give consensus support for vault-style custody. A vault locks coins under a delayed withdrawal path while preserving an always-available recovery path. BIP 345 has BIP status Closed, with BIP 443 (OP_CHECKCONTRACTVERIFY) listed as the proposed replacement. The authors withdrew further advocacy for the vault-specific opcodes in May 2025 in favor of that more general covenant design, which can still express vault constructions.		'''OP_VAULT''' was a proposed pair of [[Taproot]] script opcodes defined in [https://github.com/bitcoin/bips/blob/master/bip-0345.mediawiki BIP 345]. Together with CHECKTEMPLATEVERIFY (CTV, BIP 119), the opcodes were intended to give consensus support for vault-style custody. A vault locks coins under a delayed withdrawal path while preserving an always-available recovery path. BIP 345 has BIP status Closed, with BIP 443 (OP_CHECKCONTRACTVERIFY) listed as the proposed replacement. The authors withdrew further advocacy for the vault-specific opcodes in May 2025 in favor of that more general covenant design, which can still express vault constructions.

			== Vault flow ==

	A typical BIP 345 vault is a Taproot output whose script tree contains at least two leaves. One leaf uses <code>OP_VAULT</code> to authorize a trigger spend. The other uses <code>OP_VAULT_RECOVER</code> to send funds to a predetermined recovery destination. Triggering the vault produces an intermediate output that still carries the recovery leaf and replaces the vault leaf with a timelocked CTV script describing the intended withdrawal. After the relative delay elapses, a withdrawal that matches the CTV template can claim the coins. At any time before that withdrawal confirms, a recovery spend can sweep the funds. BIP 345 never activated on Bitcoin mainnet.		A typical BIP 345 vault is a Taproot output whose script tree contains at least two leaves. One leaf uses <code>OP_VAULT</code> to authorize a trigger spend. The other uses <code>OP_VAULT_RECOVER</code> to send funds to a predetermined recovery destination. Triggering the vault produces an intermediate output that still carries the recovery leaf and replaces the vault leaf with a timelocked CTV script describing the intended withdrawal. After the relative delay elapses, a withdrawal that matches the CTV template can claim the coins. At any time before that withdrawal confirms, a recovery spend can sweep the funds. BIP 345 never activated on Bitcoin mainnet.
Line 6:		Line 8:

	CTV (BIP 119) supplies the template commitment for the delayed withdrawal path in the BIP 345 design. Without CTV or an equivalent covenant opcode, the intermediate vault state cannot force the exact withdrawal transaction shape the vault author intended. BIP 443 aims to generalize that contracting surface so vaults become one application among several rather than a dedicated opcode pair.		CTV (BIP 119) supplies the template commitment for the delayed withdrawal path in the BIP 345 design. Without CTV or an equivalent covenant opcode, the intermediate vault state cannot force the exact withdrawal transaction shape the vault author intended. BIP 443 aims to generalize that contracting surface so vaults become one application among several rather than a dedicated opcode pair.

			== Status ==

	Prototype tooling and review discussion treated OP_VAULT as unactivated research. No Bitcoin Core release enforces BIP 345. Custody products that market vaults today typically use multisignature policies, pre-signed transaction trees, or sidechain rules rather than mainnet OP_VAULT.		Prototype tooling and review discussion treated OP_VAULT as unactivated research. No Bitcoin Core release enforces BIP 345. Custody products that market vaults today typically use multisignature policies, pre-signed transaction trees, or sidechain rules rather than mainnet OP_VAULT.

			No Bitcoin Core release enforces BIP 345 opcodes. New vault designs are expected to target BIP 443 or other covenant proposals rather than revive OP_VAULT as a dedicated soft fork.


	== See also ==		== See also ==

NotATether: Expand See also links

2026-09-13T07:27:48Z

Expand See also links

← Older revision		Revision as of 07:27, 13 September 2026
Line 13:		Line 13:
	* [[Taproot]]		* [[Taproot]]
	* [[Script]]		* [[Script]]
			* [[Timelock]]
			* [[Simplicity]]

	== External links ==		== External links ==

NotATether: Add deployment status

2026-09-13T07:27:47Z

Add deployment status

← Older revision		Revision as of 07:27, 13 September 2026
Line 6:		Line 6:

	CTV (BIP 119) supplies the template commitment for the delayed withdrawal path in the BIP 345 design. Without CTV or an equivalent covenant opcode, the intermediate vault state cannot force the exact withdrawal transaction shape the vault author intended. BIP 443 aims to generalize that contracting surface so vaults become one application among several rather than a dedicated opcode pair.		CTV (BIP 119) supplies the template commitment for the delayed withdrawal path in the BIP 345 design. Without CTV or an equivalent covenant opcode, the intermediate vault state cannot force the exact withdrawal transaction shape the vault author intended. BIP 443 aims to generalize that contracting surface so vaults become one application among several rather than a dedicated opcode pair.

			Prototype tooling and review discussion treated OP_VAULT as unactivated research. No Bitcoin Core release enforces BIP 345. Custody products that market vaults today typically use multisignature policies, pre-signed transaction trees, or sidechain rules rather than mainnet OP_VAULT.

	== See also ==		== See also ==

NotATether: Add CTV dependency and BIP 443 framing

2026-09-13T07:27:45Z

Add CTV dependency and BIP 443 framing

← Older revision		Revision as of 07:27, 13 September 2026
Line 4:		Line 4:

	The design assumes [[Taproot]] script-path spends and a relative locktime on the withdrawal path so watchers have time to recover stolen or coerced triggers. BIP 345 does not define a complete wallet UX. Application software would still need to track vault outpoints, detect unexpected triggers, and broadcast recovery transactions before the delay expires. Because the BIP is Closed and advocacy moved to BIP 443, new vault-style proposals are expected to compose more general covenant opcodes rather than ship OP_VAULT itself.		The design assumes [[Taproot]] script-path spends and a relative locktime on the withdrawal path so watchers have time to recover stolen or coerced triggers. BIP 345 does not define a complete wallet UX. Application software would still need to track vault outpoints, detect unexpected triggers, and broadcast recovery transactions before the delay expires. Because the BIP is Closed and advocacy moved to BIP 443, new vault-style proposals are expected to compose more general covenant opcodes rather than ship OP_VAULT itself.

			CTV (BIP 119) supplies the template commitment for the delayed withdrawal path in the BIP 345 design. Without CTV or an equivalent covenant opcode, the intermediate vault state cannot force the exact withdrawal transaction shape the vault author intended. BIP 443 aims to generalize that contracting surface so vaults become one application among several rather than a dedicated opcode pair.

	== See also ==		== See also ==

NotATether: Add watcher delay and BIP 443 succession context

2026-09-12T21:11:02Z

Add watcher delay and BIP 443 succession context

← Older revision		Revision as of 21:11, 12 September 2026
Line 2:		Line 2:

	A typical BIP 345 vault is a Taproot output whose script tree contains at least two leaves. One leaf uses <code>OP_VAULT</code> to authorize a trigger spend. The other uses <code>OP_VAULT_RECOVER</code> to send funds to a predetermined recovery destination. Triggering the vault produces an intermediate output that still carries the recovery leaf and replaces the vault leaf with a timelocked CTV script describing the intended withdrawal. After the relative delay elapses, a withdrawal that matches the CTV template can claim the coins. At any time before that withdrawal confirms, a recovery spend can sweep the funds. BIP 345 never activated on Bitcoin mainnet.		A typical BIP 345 vault is a Taproot output whose script tree contains at least two leaves. One leaf uses <code>OP_VAULT</code> to authorize a trigger spend. The other uses <code>OP_VAULT_RECOVER</code> to send funds to a predetermined recovery destination. Triggering the vault produces an intermediate output that still carries the recovery leaf and replaces the vault leaf with a timelocked CTV script describing the intended withdrawal. After the relative delay elapses, a withdrawal that matches the CTV template can claim the coins. At any time before that withdrawal confirms, a recovery spend can sweep the funds. BIP 345 never activated on Bitcoin mainnet.

			The design assumes [[Taproot]] script-path spends and a relative locktime on the withdrawal path so watchers have time to recover stolen or coerced triggers. BIP 345 does not define a complete wallet UX. Application software would still need to track vault outpoints, detect unexpected triggers, and broadcast recovery transactions before the delay expires. Because the BIP is Closed and advocacy moved to BIP 443, new vault-style proposals are expected to compose more general covenant opcodes rather than ship OP_VAULT itself.

	== See also ==		== See also ==

NotATether: create OP_VAULT stub (BIP 345 Closed, vault opcodes, BIP 443 successor)

2026-09-06T03:58:10Z

create OP_VAULT stub (BIP 345 Closed, vault opcodes, BIP 443 successor)

New page

'''OP_VAULT''' was a proposed pair of [[Taproot]] script opcodes defined in [https://github.com/bitcoin/bips/blob/master/bip-0345.mediawiki BIP 345]. Together with CHECKTEMPLATEVERIFY (CTV, BIP 119), the opcodes were intended to give consensus support for vault-style custody. A vault locks coins under a delayed withdrawal path while preserving an always-available recovery path. BIP 345 has BIP status Closed, with BIP 443 (OP_CHECKCONTRACTVERIFY) listed as the proposed replacement. The authors withdrew further advocacy for the vault-specific opcodes in May 2025 in favor of that more general covenant design, which can still express vault constructions.

A typical BIP 345 vault is a Taproot output whose script tree contains at least two leaves. One leaf uses <code>OP_VAULT</code> to authorize a trigger spend. The other uses <code>OP_VAULT_RECOVER</code> to send funds to a predetermined recovery destination. Triggering the vault produces an intermediate output that still carries the recovery leaf and replaces the vault leaf with a timelocked CTV script describing the intended withdrawal. After the relative delay elapses, a withdrawal that matches the CTV template can claim the coins. At any time before that withdrawal confirms, a recovery spend can sweep the funds. BIP 345 never activated on Bitcoin mainnet.

== See also ==

* [[Taproot]]
* [[Script]]

== External links ==

* [https://github.com/bitcoin/bips/blob/master/bip-0345.mediawiki BIP 345: OP_VAULT]
* [https://github.com/bitcoin/bips/blob/master/bip-0443.mediawiki BIP 443: OP_CHECKCONTRACTVERIFY]
* [https://delvingbitcoin.org/t/withdrawing-op-vault-bip-345/1670 Withdrawing OP_VAULT (BIP 345)]
* [https://bitcoinops.org/en/topics/vaults/ Bitcoin Optech: Vaults]

[[Category:Technical]]