<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://en.bitcoin.it/w/index.php?action=history&amp;feed=atom&amp;title=OP_VAULT</id>
	<title>OP VAULT - Revision history</title>
	<link rel="self" type="application/atom+xml" href="https://en.bitcoin.it/w/index.php?action=history&amp;feed=atom&amp;title=OP_VAULT"/>
	<link rel="alternate" type="text/html" href="https://en.bitcoin.it/w/index.php?title=OP_VAULT&amp;action=history"/>
	<updated>2026-09-07T14:01:05Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.43.9</generator>
	<entry>
		<id>https://en.bitcoin.it/w/index.php?title=OP_VAULT&amp;diff=71171&amp;oldid=prev</id>
		<title>NotATether: create OP_VAULT stub (BIP 345 Closed, vault opcodes, BIP 443 successor)</title>
		<link rel="alternate" type="text/html" href="https://en.bitcoin.it/w/index.php?title=OP_VAULT&amp;diff=71171&amp;oldid=prev"/>
		<updated>2026-09-06T03:58:10Z</updated>

		<summary type="html">&lt;p&gt;create OP_VAULT stub (BIP 345 Closed, vault opcodes, BIP 443 successor)&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;&amp;#039;&amp;#039;&amp;#039;OP_VAULT&amp;#039;&amp;#039;&amp;#039; 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.&lt;br /&gt;
&lt;br /&gt;
A typical BIP 345 vault is a Taproot output whose script tree contains at least two leaves. One leaf uses &amp;lt;code&amp;gt;OP_VAULT&amp;lt;/code&amp;gt; to authorize a trigger spend. The other uses &amp;lt;code&amp;gt;OP_VAULT_RECOVER&amp;lt;/code&amp;gt; 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.&lt;br /&gt;
&lt;br /&gt;
== See also ==&lt;br /&gt;
&lt;br /&gt;
* [[Taproot]]&lt;br /&gt;
* [[Script]]&lt;br /&gt;
&lt;br /&gt;
== External links ==&lt;br /&gt;
&lt;br /&gt;
* [https://github.com/bitcoin/bips/blob/master/bip-0345.mediawiki BIP 345: OP_VAULT]&lt;br /&gt;
* [https://github.com/bitcoin/bips/blob/master/bip-0443.mediawiki BIP 443: OP_CHECKCONTRACTVERIFY]&lt;br /&gt;
* [https://delvingbitcoin.org/t/withdrawing-op-vault-bip-345/1670 Withdrawing OP_VAULT (BIP 345)]&lt;br /&gt;
* [https://bitcoinops.org/en/topics/vaults/ Bitcoin Optech: Vaults]&lt;br /&gt;
&lt;br /&gt;
[[Category:Technical]]&lt;/div&gt;</summary>
		<author><name>NotATether</name></author>
	</entry>
</feed>