#

bip

(42 articles)

Taproot

Taproot is a consensus-layer upgrade to the Bitcoin protocol that was activated in November 2021 as a softfork (BIPs 340, 341, and 342). Designed to improve Bitcoin's privacy, efficiency, and flexibility, Taproot introduces three interconnected innovations: Schnorr signatures, Merkelized Abstract Syntax Trees (MAST), and Tapscript.

bitcoinbipsoft_fork

SegWit

Segregated Witness (abbreviated as SegWit) is an implemented protocol upgrade intended to provide protection from transaction malleability and increase block capacity by changing the structure of transactions.

bitcoinbipsoft_fork

Post Quantum Migration and Legacy Signature Sunset

This proposal (BIP number to be defined) follows the implementation of post-quantum (PQ) signatures and introduces a pre-announced sunset of legacy ECDSA/Schnorr signatures. It turns quantum security into a private incentive: fail to upgrade and you will be unable to spend your funds, creating a certainty where none previously existed.

bitcoinbipsoft_fork

OP_TXHASH

TXHASH allows the user to specify a range of individual bits of the spending transaction to be included in the transaction template.

bitcoinbipcovenant

TLUV

OP_TAPLEAF_UPDATE_VERIFY (TLUV) is an opcode that takes information about the taproot input being spent, makes modifications described in a tapscript, and requires that the result be equivalent to the scriptPubKey in the output in the same position as the input. Where it differs from previous proposals is that it allows the created tapscript to specify modifications to both the internal key and a tapscript tree (MAST).

bitcoinbipcovenant

ANYPREVOUT

SIGHASH_ANYPREVOUT (APO) describes a new type of public key for tapscript (BIP 342) transactions. It allows signatures for these public keys to not commit to the exact UTXO being spent. This enables dynamic binding of transactions to different UTXOs, provided they have compatible scripts.

bitcoinbipcovenant

OP_VAULT

OP_VAULT is a type of covenant that require two separate transactions to appear in two different blocks in order for a user to spend money from their wallet. The first transaction signals that someone is attempting to spend the money and gives the user a chance to block the second transaction that completes the spend.

bitcoinbipcovenant

OP_CHECKTEMPLATEVERIFY

OP_CHECKTEMPLATEVERIFY (CTV) is a proposed new opcode that takes a commitment and requires any transaction executing the opcode to match the commitment in the following fields: its version, locktime, signature scripts, number of inputs, sequences, number of outputs, outputs, and the location of the input being spent within the spending transaction.

bitcoinbipcovenant

OP_CHECKSIGFROMSTACK

OP_CHECKSIGFROMSTACK (OP_CSFS) is an opcode that allows checking whether a signature signs an arbitrary message. The opcode takes three parameters: a signature, a message, and a public key.

bitcoinbipcovenant

OP_CCV

OP_CHECKCONTRACTVERIFY (OP_CCV) is a proposed opcode that enables a new primitive called state-carrying UTXOs. This primitive allows a UTXO to contain a commitment to data that can be introspected and computed upon in Script, with the resulting data embedded in the output UTXOs. Together with an opcode that allows the creation of vector commitments, OP_CCV enables fraud proofs for arbitrary computations, widely extending the class of smart contracts that are possible in Script.

bitcoinbipcovenant

OP_CAT

OP_CAT was originally an opcode in Bitcoin. It was disabled in 2010 but slight variations on it are frequently proposed to be added to Bitcoin using a soft fork. Both the original OP_CAT and the new proposals for it concatenate two elements on the stack into a single element. The primary expected use for OP_CAT is for data provided by the creator of a script to be concatenated with data provided by someone spending from that script.

bitcoinbipcovenant

Direct Introspection

This covenant proposal main idea is to give the Script of a transaction's inputs direct access into the entire transaction's data. If the script can inspect any part of the transaction, it is by definition introspective and can enforce any possible constraint on the transaction's properties.

bitcoinbipcovenant

BIP-360: Pay to Tapscript Hash (P2TSH)

This BIP proposes a new output type: Pay-to-Tapscript-Hash (P2TSH), via a soft fork. P2TSH outputs operate with nearly the same functionality as P2TR (Pay-to-Taproot) outputs, but with the key path spend removed.

bitcoinbipsoft_fork

BIP-110: Reduced Data Temporary Softfork

This BIP proposes to temporarily limit the size of data fields at the consensus level, in order to correct distorted incentives caused by standardizing support for arbitrary data, and to refocus priorities on improving Bitcoin as money.

bitcoinbipsoft_fork

Taproot

Taproot is a consensus-layer upgrade to the Bitcoin protocol that was activated in November 2021 as a softfork (BIPs 340, 341, and 342). Designed to improve Bitcoin's privacy, efficiency, and flexibility, Taproot introduces three interconnected innovations: Schnorr signatures, Merkelized Abstract Syntax Trees (MAST), and Tapscript.

bitcoinbipsoft_fork

Segwit

Segregated Witness (abbreviated as SegWit) is an implemented protocol upgrade intended to provide protection from transaction malleability and increase block capacity by changing the structure of transactions.

bitcoinbipsoft_fork

Post Quantum Migration and Legacy Signature Sunset

This proposal (BIP number to be defined) follows the implementation of post-quantum (PQ) signatures and introduces a pre-announced sunset of legacy ECDSA/Schnorr signatures. It turns quantum security into a private incentive: fail to upgrade and you will be unable to spend your funds, creating a certainty where none previously existed.

bitcoinbipsoft_fork

OP_TXHASH

TXHASH allows the user to specify a range of individual bits of the spending transaction to be included in the transaction template.

bitcoinbipcovenant

TLUV

OP_TAPLEAF_UPDATE_VERIFY (TLUV) is an opcode that takes information about the taproot input being spent, makes modifications described in a tapscript, and requires that the result be equivalent to the scriptPubKey in the output in the same position as the input. Where it differs from previous proposals is that it allows the created tapscript to specify modifications to both the internal key and a tapscript tree (MAST).

bitcoinbipcovenant

ANYPREVOUT

SIGHASH_ANYPREVOUT (APO) describes a new type of public key for tapscript (BIP 342) transactions. It allows signatures for these public keys to not commit to the exact UTXO being spent. This enables dynamic binding of transactions to different UTXOs, provided they have compatible scripts.

bitcoinbipcovenant

OP_VAULT

OP_VAULT is a type of covenant that require two separate transactions to appear in two different blocks in order for a user to spend money from their wallet. The first transaction signals that someone is attempting to spend the money and gives the user a chance to block the second transaction that completes the spend.

bitcoinbipcovenant

OP_CHECKTEMPLATEVERIFY

OP_CHECKTEMPLATEVERIFY (CTV) is a proposed new opcode that takes a commitment and requires any transaction executing the opcode to match the commitment in the following fields: its version, locktime, signature scripts, number of inputs, sequences, number of outputs, outputs, and the location of the input being spent within the spending transaction.

bitcoinbipcovenant

OP_CHECKSIGFROMSTACK

OP_CHECKSIGFROMSTACK (OP_CSFS) is an opcode that allows checking whether a signature signs an arbitrary message. The opcode takes three parameters: a signature, a message, and a public key.

bitcoinbipcovenant

OP_CCV

OP_CHECKCONTRACTVERIFY (OP_CCV) is a proposed opcode that enables a new primitive called state-carrying UTXOs. This primitive allows a UTXO to contain a commitment to data that can be introspected and computed upon in Script, with the resulting data embedded in the output UTXOs. Together with an opcode that allows the creation of vector commitments, OP_CCV enables fraud proofs for arbitrary computations, widely extending the class of smart contracts that are possible in Script.

bitcoinbipcovenant

OP_CAT

OP_CAT was originally an opcode in Bitcoin. It was disabled in 2010 but slight variations on it are frequently proposed to be added to Bitcoin using a soft fork. Both the original OP_CAT and the new proposals for it concatenate two elements on the stack into a single element. The primary expected use for OP_CAT is for data provided by the creator of a script to be concatenated with data provided by someone spending from that script.

bitcoinbipcovenant

Direct Introspection

This covenant proposal main idea is to give the Script of a transaction's inputs direct access into the entire transaction's data. If the script can inspect any part of the transaction, it is by definition introspective and can enforce any possible constraint on the transaction's properties.

bitcoinbipcovenant

BIP-360: Pay to Tapscript Hash (P2TSH)

This BIP proposes a new output type: Pay-to-Tapscript-Hash (P2TSH), via a soft fork. P2TSH outputs operate with nearly the same functionality as P2TR (Pay-to-Taproot) outputs, but with the key path spend removed.

bitcoinbipsoft_fork

BIP-110: Reduced Data Temporary Softfork

This BIP proposes to temporarily limit the size of data fields at the consensus level, in order to correct distorted incentives caused by standardizing support for arbitrary data, and to refocus priorities on improving Bitcoin as money..

bitcoinbipsoft_fork

Taproot

Taproot is a consensus-layer upgrade to the Bitcoin protocol that was activated in November 2021 as a softfork (BIPs 340, 341, and 342). Designed to improve Bitcoin's privacy, efficiency, and flexibility, Taproot introduces three interconnected innovations: Schnorr signatures, Merkelized Abstract Syntax Trees (MAST), and Tapscript.

bitcoinbipsoft_fork

Segwit

Segregated Witness (abbreviated as SegWit) is an implemented protocol upgrade intended to provide protection from transaction malleability and increase block capacity by changing the structure of transactions.

bitcoinbipsoft_fork

Post Quantum Migration and Legacy Signature Sunset

This proposal (BIP number to be defined) follows the implementation of post-quantum (PQ) signatures and introduces a pre-announced sunset of legacy ECDSA/Schnorr signatures. It turns quantum security into a private incentive: fail to upgrade and you will be unable to spend your funds, creating a certainty where none previously existed.

bitcoinbipsoft_fork

OP_TXHASH

TXHASH allows the user to specify a range of individual bits of the spending transaction to be included in the transaction template.

bitcoinbipcovenant

TLUV

OP_TAPLEAF_UPDATE_VERIFY (TLUV) is an opcode that takes information about the taproot input being spent, makes modifications described in a tapscript, and requires that the result be equivalent to the scriptPubKey in the output in the same position as the input. Where it differs from previous proposals is that it allows the created tapscript to specify modifications to both the internal key and a tapscript tree (MAST).

bitcoinbipcovenant

ANYPREVOUT

SIGHASH_ANYPREVOUT (APO) describes a new type of public key for tapscript (BIP 342) transactions. It allows signatures for these public keys to not commit to the exact UTXO being spent. This enables dynamic binding of transactions to different UTXOs, provided they have compatible scripts.

bitcoinbipcovenant

OP_VAULT

OP_VAULT is a type of covenant that require two separate transactions to appear in two different blocks in order for a user to spend money from their wallet. The first transaction signals that someone is attempting to spend the money and gives the user a chance to block the second transaction that completes the spend.

bitcoinbipcovenant

OP_CHECKTEMPLATEVERIFY

OP_CHECKTEMPLATEVERIFY (CTV) is a proposed new opcode that takes a commitment and requires any transaction executing the opcode to match the commitment in the following fields: its version, locktime, signature scripts, number of inputs, sequences, number of outputs, outputs, and the location of the input being spent within the spending transaction.

bitcoinbipcovenant

OP_CHECKSIGFROMSTACK

OP_CHECKSIGFROMSTACK (OP_CSFS) is an opcode that allows checking whether a signature signs an arbitrary message. The opcode takes three parameters: a signature, a message, and a public key.

bitcoinbipcovenant

OP_CCV

OP_CHECKCONTRACTVERIFY (OP_CCV) is a proposed opcode that enables a new primitive called state-carrying UTXOs. This primitive allows a UTXO to contain a commitment to data that can be introspected and computed upon in Script, with the resulting data embedded in the output UTXOs. Together with an opcode that allows the creation of vector commitments, OP_CCV enables fraud proofs for arbitrary computations, widely extending the class of smart contracts that are possible in Script.

bitcoinbipcovenant

OP_CAT

OP_CAT was originally an opcode in Bitcoin. It was disabled in 2010 but slight variations on it are frequently proposed to be added to Bitcoin using a soft fork. Both the original OP_CAT and the new proposals for it concatenate two elements on the stack into a single element. The primary expected use for OP_CAT is for data provided by the creator of a script to be concatenated with data provided by someone spending from that script.

bitcoinbipcovenant

Direct Introspection

This covenant proposal main idea is to give the Script of a transaction's inputs direct access into the entire transaction's data. If the script can inspect any part of the transaction, it is by definition introspective and can enforce any possible constraint on the transaction's properties.

bitcoinbipcovenant

BIP-360: Pay to Tapscript Hash (P2TSH)

This BIP proposes a new output type: Pay-to-Tapscript-Hash (P2TSH), via a soft fork. P2TSH outputs operate with nearly the same functionality as P2TR (Pay-to-Taproot) outputs, but with the key path spend removed.

bitcoinbipsoft_fork

BIP-110: Reduced Data Temporary Softfork

This BIP proposes to temporarily limit the size of data fields at the consensus level, in order to correct distorted incentives caused by standardizing support for arbitrary data, and to refocus priorities on improving Bitcoin as money..

bitcoinbipsoft_fork