BIP 345 — OP_VAULT

BIP 345 (OP_VAULT) proposed a consensus soft fork adding opcodes purpose-built for vaults: coins withdrawn from a vault would enter a delay period during which they could be swept to a pre-committed recovery path, mitigating key theft. Repository status: Closed — the proposal is no longer being advanced in the BIPs repository.

Debate relevance: Comes up in covenant debates as the dedicated-vault design point of comparison against general-purpose primitives (CTV, OP_CAT, APO). Its Closed status is itself a talking point about proposal attrition. Common misstatements: Citing OP_VAULT as a live activation candidate — its repository status is Closed. Also, vault-like constructions are also claimed as use cases of CTV and other proposals; 'vaults' on stage rarely means BIP 345 specifically.