This is the fourth article in a series Deep diving in the individual era proposals that have reached a point of maturity that deserves an in -depth collapse.
OP_VauntAnd James Obern presented at the BIP 345 (with the addition of Greg Sanders as a co -author), is an era designed to implement the basements. In addition, this depends on CTV (or TXHash or other similar preconceived symbols) to complete the construction of a cellar.
Before entering how the suggestion itself works, let’s look at what it tries to do.
The purpose of the cellar is to improve your bitcoin storage safety. This is achieved by introducing a delay period during any attempt to spend from the cellar. Instead of being able to send Bitcoin directly from Vault, Vaurt restricts it so that it can only be sent to the title “Middle Groud”. While the coins that are withdrawn from a cellar in this middle case, can be spent at any time in a deep cold storage under your control (perfectly, Multisig is geographically distributed), and only To this deep cold storage. After a predetermined period of time, the coins can be spent on the ultimate destination.
This is something that can currently do through the previously signed transactions, but this brings a great degree of complexity, inconvenience, flexibility and the risk of money loss.
You require the use of previously signed transactions to decide early on the amount of money that will be withdrawn simultaneous Ownership To delete the special keys used safely to sign all these transactions in advance.
A big problem with this structure, regardless of the total restrictions of the amounts that were previously identified, is that reusing the title is not safe. In the pre -signed transaction cellar scheme, deposits are sent to the user address to sign the preliminary Vauult transaction, and this is deleted alongside all other keys concerned after signing Vauult transactions. The re -use is a bad practice, but you cannot prevent someone else from sending money to a address that you use before. Any money will be lost later forever, as all VAULT keys have been deleted.
Also, every deposit in the cellar requires a new set of new keys, a pre -signing signing ceremony again for the new set of transactions, ensuring a new set of keys securely deleted, and managing the appropriate storage for all this information including repeated backup. Each one deposit creates an opportunity for something to attach him while preparing a cellar, provides each deposit opportunity for a person who has endangered a system or device since the last deposit to try to steal your money.
The cellars of pre -signed transactions are stressful and complex, and provide adequate complexity, which each uses a risk that is not qualified to tamper with in a way that leads to lost money.
Improvements can be made with CTV, such as eliminating the need to delete the keys safely, but the rest of the complexity and risks remain. The amounts and fees should be pre -defined. The title can still re -use the box loss.
How works OP_Vaunt
OP_Vaunt is designed on Taproot, which means that the entire design uses Tapscript and depends on the presence of Taptrees and the course of spending on text programs. It also depends on the use of CTV (or TXHash/Similar Job) to build a full cellar.
The suggestion is actually two icons OPCODES, OP_Vautt, and OP_VAULT_RCOOOR. OP_Vaunt is used to operate Vauult withdrawals, and OP_vaut_Cover is used to sweep vibrant clouds in the deep recovery portfolio. The idea is to create TAPTREE that contains OP_VALT paths to withdraw, and UP_Valt_RCOOR paths to equip any money in the middle with a safe, safe wallet. This Taptree is your cellar.
OP_vault works by restricting how the transaction spending outputs appear on the amazing OP_Vaunt coin. The optical code is expected in the witness:
- TAPLEF text
- The number of data cuts to update the text program
- Directing index to withdraw
- The output index of any money belongs to the cellar
- A quantity of Satoshis returns to the cellar
OP_Vaunt guarantees that the healthy amount match To Taptree from which you spend. It also takes the TAPLEAF text program, the data variables provided, and combine it in the complete TAPLEAF text. Then it ensures that the outcome of the withdrawal has a text program identical with TAPTREE from the inputs that are spent, Excluded TAPLEAF is replaced by the TAPLEAF program that is assembled with data from the witness.
This last trick is possible because in order to check that TAPLEAF is part of Taptree in the first place, the internal nodes of the Merkle tree should be present to verify. Fixing the new text program with the internal leaves known to the rest of the tree ensures that this tree sheet has been changed only. The dynamic textual program template is defined at the time of the creation of a cellar. For the state of using a typical cellar, the text program template will simply be a CTV CTV path with retail provided when the withdrawal is run.
Op_Vaunt_recover is much simpler. It takes to divide the recovery text program and output index for recovery treatment. This output must contain a text program that matches the pre -determined retail, and the amount of money in the input that is recovered must go to this output.
Each of these text programs can be “with gates” with a script for authorization, i.e. providing a signature from a specific key in order to operate withdrawal or start recovery. This has some trading. If you lose the recovery license key, you will not be able to run the recovery treatment if your withdrawal is stolen. However, it allows you to start a recovery from UTXOS multiple cellar in the same transaction due to the identification of the outputs of each manually.
What is OP_Vaunt is good for
Clear cellar. OP_Vaunt cleanly dealt with all the main restrictions of pre -signed treatment or CTV cellar. There are no previously restricted categories or prior fees, and there is no risk of reusing addresses, and there is no need to deal with a high security problem such as the main deletion every time you deposit.
It is more flexible than just a cellar though. This was the intended state of use when it was designed, but it is a more general era that ensures that Tabri is actually carried to the next UTXO when you want it, with pre -determined exit conditions that have a degree of flexibility.
You can make something very close to Drivechain with OP_Vaunt. Create a cellar template that contains an incredibly timelock timelock, with an order 3-6 months (similar to Drivechain withdrawals). You do not have a license portal for any text and make the template public. People can now simply deposit money in “Drivechain” by sending money to this Vauult text program. Anyone can suggest withdrawal by simply spending from the OP_VALT track and includes the CTV retail for withdrawal treatment. Miners can enforce this by rejecting any unpleasant withdrawal transactions, and if a harmful mine worker mines a malignant clouds, the upcoming honest mines can return funds.
This is what can only be done using the corresponding text program template as recommended in the BIP. The textual program that has been appointed to withdraw is arbitrary, and in this way it is likely to be very general in terms of the types of self -contracts that OP_vaut can offer.
Final ideas
OP_Vaunt clearly achieves the goal of enabling a suitable cellar that does not come with the restrictions, complications and risks with which the pre -signed transactions cellar (or even a simpler era with something like CTV). However, when doing this, it ended up providing a wide and generalized set of jobs to achieve this original goal.
The suggestion will permanently enable smooth and relatively safe cellar functions, but also opens many other doors. Drivechains is something that comes with a large degree of risks centered on the value extracted from mines (MEV). The negative aspects of this function must be weighted, incentive issues and consequences that can be, against the budget direction to enable a well -created cellar.
OP_Vaunt is a relatively mature suggestion, but it should not be handled with the function it offers lightly.