Client-side validation
Also covering RGB, Taro, Taproot Assets, and Shielded CSV
Client-side validation protocols allow a Bitcoin transaction to commit to some data whose validity is determined separate from the validity of the transaction under Bitcoin’s consensus rules. The client-side validation can take advantage of consensus rules, such as only allowing an output to be spent once within a valid block chain, but it may also impose additional rules known only to those interested in the validation.
A conceptually simple client-side validation protocol might assign an off-chain state (like an amount of owned tokens) with a particular UTXO. Only the set of validators needs to know about that assignment; it does not need to be published anywhere public, such as the blockchain. When the UTXO is spent, the user can update the state and use spending transactions to assign the new state to a new UTXO. This mechanism is known as single-use seals, and it leverages anti-double-spending property of bitcoin.
As an example, if Alice currently controls the UTXO associated with the token and Bob wants to buy it from her, she can provide him with evidence of the original assignment and then he can use his validated copy of the block chain plus client-side validation to verify the history of every transfer of the token leading up to Alice. He can also verify that a transaction created by Alice is correctly formatted to assign the token to a UTXO that Bob controls.
RGB is a client-side validation protocol for working with arbitrary reachable state and Turing-complete state evolution rules. It uses taproot-embedded OP_RETURN commitments (named tapret) to allow transactions to commit to smart contract state.
Taproot Assets, formerly called Taro, is a protocol heavily inspired by RGB that uses taproot’s commitment structure to allow transactions to commit to tokens. Unlike RGB, it does not allow state types other than token and doesn’t have Turing completeness. Taproot’s construction itself derives from pay-to-contract. As the name suggests, initial protocol development is specifically focused on the transfer of assets (that is, digital tokens that represent assets).
Both protocols are designed to be compatible with offchain transactions, such as LN payments. Similar to the lifecycle of an LN channel, an onchain setup transaction is published that commits the tokens to the mutual control of involved parties; a series of offchain transactions each commits to the current allocation of the tokens between the parties; and a transaction containing the final commitment is published onchain.
Only wallets that want to support RGB or Taproot Assets need to understand the protocol, and only a wallet that wants to send or receive a specific token or other client-side validation contract needs to know anything about that contract. To everyone else, transactions created with RGB and Taproot Assets look like regular Bitcoin transactions.
Primary code and documentation
Optech newsletter and website mentions
2024
- Shielded client-side validation proposed
- LND #9095 and LND #9072 improve custom channel features to improve taproot assets support
- Taproot Assets v0.4.0-alpha released
2023
2022
See also
Previous Topic:
Channel jamming attacks
Next Topic:
CLTV expiry delta