That is the third article in a sequence deep diving into particular person covenant proposals which have reached some extent of maturity meriting an in-depth breakdown.
TXHASH and CHECKTXHASHVERIFY (TXHASH), put ahead by Steven Roose and Brandon Black with a BIP quantity presently unassigned, is a “template based mostly” covenant that may conceptually seen as an extension or extra superior model of CHECKTEMPLATEVERIFY (CTV).
Earlier than entering into the nitty gritty of how TXHASH works, let’s refresh on the items of knowledge in a Bitcoin transaction.
At a excessive degree you’ve got the outputs, the inputs, and the witness (or script sig for non-Segwit transactions within the enter).
International transaction fields:
Model Marker, indicating Segwit with a flag worth Flag, indicating Segwit with a flag worth Enter rely Output rely nLocktime, used for timelocks
Every enter comprises:
TXID of the earlier transaction VOUT (index) of the output from that transaction being spent ScriptSig measurement ScriptSig (if a non-segwit transaction) Sequence quantity (used for RBF flagging and relative timelocks).
Every output comprises:
Quantity of satoshis assigned to the output ScriptPubKeySize, the dimensions of the locking script ScriptPubkey, the precise locking script
We are able to ignore the witness area when contemplating TXHASH or CHECKTXHASHVERIFY as neither opcode constrains the witness area to retain sure properties.
How TXHASH Works
Each TXHASH (tapscript solely) and CHECKTXHASHVERIFY (legacy script and tapscript) have totally different behaviors on the stack due to the variations between legacy script and tapscript. For the needs of this text, these variations aren’t materials, so we’re merely going to disregard them.
If CTV is a covenant opcode that constrains a bitcoin output to solely be spent in a singular and precisely outlined approach, TXHASH is a supercharged model of CTV that permits you to choose and select precisely what items of a transaction are constrained and have to be spent within the precisely pre-defined approach, and which items of a transaction could be no matter somebody needs at spending time.
It offers you the perfect of each worlds, requiring one thing be completed when spending a covenant restricted coin, however then permitting a person to do no matter they need with the remainder of the funds accessible to them or the transaction they’re crafting.
That is completed utilizing the ‘TxFieldSelector’.
CTV merely makes use of a single hash of the pre-defined transaction in an effort to confirm at spending time. With TXHASH, you want a strategy to talk what items of knowledge that hash is committing to, and what items of knowledge it isn’t. That’s the TxFieldSelector’s job.
TxFieldSelector is basically a sequence of bytes (that may be variable in size), with every bit speaking what fields in a transaction are dedicated to by the hash that will likely be verified in opposition to. This lets you choose particular fields of the transaction, nLocktime, model and many others. It lets you choose particular fields of the inputs and outputs, i.e. embody or not the sequence quantity, or the earlier output id, or the taproot annex (a datafield particular to taproot scripts). The outputs, whether or not to decide to the ScriptPubkey, the quantity values, each, or neither. You may also resolve precisely which outputs and inputs these restrictions apply to.
There’s some complexity and adaptability in how the TxFieldSelector is put collectively, and you’ll learn all of the finer particulars right here within the proposed BIP for those who’re concerned about these, however the chief level to remove is it permits you to choose precisely which components of the transaction are restricted by the covenant when somebody goes to spend the encumbered output, and which components aren’t, to a really granular diploma.
What Is TXHASH Helpful For
Firstly, TXHASH permits you to do every little thing that you could with CTV. So all the worth supplied by CTV to optimize the coordination prices of something presently doable with pre-signed transactions can be supplied by TXHASH. However it supercharges that functionality massively. As a substitute of getting to decide to the whole thing of a transaction, you possibly can commit to simply the components you care about.
This has two massive advantages in concept proper off the bat. Initially, in band price administration for layer twos turns into simpler to cope with. At present using anchor outputs is required to fee-bump layer two settlement transactions with Little one Pays For Guardian, the place a transaction spending an output from an unconfirmed one can add to the web charges for each. TXHASH permits you to decide to solely your counterparties outputs in a multiparty transaction, and go away yours free to do no matter you need with (caveat right here that different issues have to be completed to make this secure so a 3rd celebration can’t burn all your funds to charges), together with decrementing barely to RBF the transaction.
Second, the door is now open for multiparty protocols to permit granular ensures about what off-chain transactions are committing to. Some customers can now obtain a assure about how their cash will likely be spent, however not must care about what another group of customers does with theirs. I can make sure that one TxFieldSelector ensures my cash are dealt with correctly, and I don’t must care about the place anybody else’s cash go.
Together with CHECKSIGFROMSTACK (CSFS), TXHASH can facilitate a very generalized SIGHASH system. The SIGHASH flag is part of a signature that communicates what components of the transaction to examine the signature in opposition to. They’re presently:
SIGHASH_ALL – indicators all inputs and outputs SIGHASH_NONE – indicators all inputs and no outputs SIGHASH_SINGLE – indicators all inputs and the output with the identical index as this enter
None of those SIGHASH flags enable including any new inputs to a transaction with out invalidating them, however every has an ANYONECANPAY model that solely indicators its personal enter and the suitable outputs, permitting anybody else to then add new inputs, and new outputs for the ANYONECANPAY model of SIGHASH_NONE and SIGHASH_SINGLE.
By having the ability to “sideload” new TxFieldSelectors utilizing CSFS, customers can emulate a SIGHASH system that permits them to choose and select precisely which particular person items of a transaction the signature commits to or not.
TXHASH additionally permits imposing equality between the worth of inputs and outputs by utilizing particular person TxFieldSelectors that commit solely to a single worth area of an enter or output you want to examine, after which making certain their hashes are the identical on the stack.
Closing Ideas
TXHASH is a possible supercharging of CTV, enabling an extremely granular diploma of introspection of the spending transaction which could be extremely highly effective, particularly together with one thing like CSFS.
Nevertheless, that energy is expressive sufficient that it opens up the door to an extremely giant design area. One that might probably have a fabric impact on the general incentives of Bitcoin. Issues like making certain quantity equality throughout outputs or inputs is getting very near the territory of what’s wanted for trustless automated change on-chain. That could be a severe supply of Miner Extractable Worth (MEV), which has been a really severe incentive and centralization downside for different blockchains to cope with.
TXHASH ought to completely not be dismissed, because it gives extremely highly effective primitives for protocol builders to make the most of, however the potential second order implications of what individuals will construct with it must be weighed in opposition to the positives.
