Sealminer A4 Ultra Hydro
Bitcoin & Bitcoin Cash ASIC Miner
886TH
HASHRATE
9.45W/TH
EFFICIENCY
8373W
POWER
£844.64
EST. MONTHLY
NO PAYBACK
EST. ROI
This guide explains BIP 345 OP_VAULT in plain English. It covers the problem behind the BIP, why it matters and whether the proposal is part of Bitcoin today.
TL;DR
- What it is: BIP 345 specified OP_VAULT and OP_VAULT_RECOVER as two proposed tapscript opcodes for an interruptible withdrawal covenant. Together with OP_CHECKTEMPLATEVERIFY, the design aimed to let funds enter a delayed withdrawal path while preserving a predetermined recovery route.
- Why it matters: BIP 345 is useful history for understanding vault design, but it is not deployable Bitcoin functionality. Its enduring lesson is that delayed custody needs both consensus rules and a rigorously tested monitoring and recovery operation.
- Current position: BIP 119 itself is not active Bitcoin consensus behaviour.
BIP 345 OP_VAULT in simple English
BIP 345 OP_VAULT: BIP 345 is Closed, not Draft, Final or Deployed. Its scripts are historical proposal material and must not be presented as valid mainnet custody instructions.
Simple example
A node operator is checking BIP 345 OP_VAULT. Triggering creates an intermediate state whose delayed withdrawal can be redirected to recovery before finalisation. A vault taptree contains a normal OP_VAULT leaf and an OP_VAULT_RECOVER leaf.
Key terms in plain English
- BIP:
- Bitcoin Improvement Proposal: a document describing a proposed rule, standard or process. Its status must be checked separately.
- Consensus:
- The shared rules full nodes use to decide whether blocks and transactions are valid.
- Node:
- A computer running Bitcoin software that checks data and communicates with other peers.
Status
BIP 345 is Closed, not Draft, Final or Deployed. Its scripts are historical proposal material and must not be presented as valid mainnet custody instructions.
Proposed mechanism
A vault taptree contains a normal OP_VAULT leaf and an OP_VAULT_RECOVER leaf. Triggering creates an intermediate state whose delayed withdrawal can be redirected to recovery before finalisation.
CTV dependency
The design relied on BIP 119 OP_CHECKTEMPLATEVERIFY to commit the final withdrawal to selected outputs. BIP 119 itself is not active Bitcoin consensus behaviour.
Operational goal
The proposal sought reusable configurations, batching, partial withdrawals, targets chosen at trigger time and dynamic fee management without storing presigned bearer transactions forever.
Recovery model
Security depended on monitoring vault outpoints, detecting unexpected triggers quickly and retaining access to a deliberately protected recovery policy. A delay creates response time, not automatic safety.
Risk boundaries
Watchtower outages, compromised recovery keys, fee spikes, policy mistakes, address reuse and untested recovery ceremonies could still cause loss even in a hypothetical deployment.
Replacement context
The header names BIP 443 as the proposed replacement. Readers should follow the newer specification separately rather than treating BIP 345 parameter details as current direction. Build a revision-pinned evidence pack on an isolated node, wallet or protocol harness.
Frequently asked questions
What is the main point of BIP 345 OP_VAULT?
BIP 345 OP_VAULT: BIP 345 is Closed, not Draft, Final or Deployed. Its scripts are historical proposal material and must not be presented as valid mainnet custody instructions.
For BIP 345 OP_VAULT, what should a beginner know about status?
BIP 345 is Closed, not Draft, Final or Deployed. Its scripts are historical proposal material and must not be presented as valid mainnet custody instructions.
For BIP 345 OP_VAULT, what should a beginner know about proposed mechanism?
A vault taptree contains a normal OP_VAULT leaf and an OP_VAULT_RECOVER leaf.
For BIP 345 OP_VAULT, what should a beginner know about ctv dependency?
The design relied on BIP 119 OP_CHECKTEMPLATEVERIFY to commit the final withdrawal to selected outputs.
Conclusion
BIP 345 is useful history for understanding vault design, but it is not deployable Bitcoin functionality. Its enduring lesson is that delayed custody needs both consensus rules and a rigorously tested monitoring and recovery operation.
Primary sources
Check the current specification status and the documentation for the exact implementation you operate before moving production funds or changing a mining node.
Join the ASIC Mining Discussion
Members can read and join the discussion
Log in to read comments from other miners. Create a free account if you would like to ask a question or share your experience.
Membership helps us protect the discussion from spam and keep answers useful.