bitcoin/bips
1
0
Fork 0
mirror of https://github.com/bitcoin/bips.git synced 2025-08-18 13:26:23 +00:00
Code Issues Releases Wiki Activity

BIP443: list stack elements in bottom-to-top order

Browse Source 
and a few minor fixups
This commit is contained in:
Johan T. Halseth 2025-06-02 14:09:04 -06:00 committed by Jon Atack
parent 88a1ae5782
commit 6a311752dd
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
bip-0443.mediawiki
View File

@ -38,7 +38,7 @@ This document is licensed under the 3-clause BSD license.
The ability to constrain the future of coins beyond what is possible with presigned transactions is at the core of
numerous attempts to improve bitcoin. Some of the proposed applications include:
* UTXO sharing schemes like Ark, CoinPools, Timeout Trees, etc. use various types of output restrictions in order to enable multiple parties to share the control of a UTXO, while ensuring that each participant controls their own `balance.
* UTXO sharing schemes like Ark, CoinPools, Timeout Trees, etc. use various types of output restrictions in order to enable multiple parties to share the control of a UTXO, while ensuring that each participant controls their own balance.
* <code>OP_VAULT</code><ref>[[bip-0345.mediawiki|BIP-345]]</ref> is a proposed opcode to implement a 2-step withdrawal process, enabling on-chain reactive security.
* <code>OP_CHECKTEMPLATEVERIFY</code><ref>[[bip-119.mediawiki|BIP-114]]</ref> is a long-proposed opcode to constrain a transaction to a ''template'' with a fixed set of outputs.
* Sidechains and rollups could be implemented via a UTXO encumbered with a recursive covenant, updating the sidechain state root every time it is spent.
@ -135,10 +135,10 @@ The tapscript opcode <code>OP_SUCCESS187</code> (<code>0xbb</code>) is constrain
<code>OP_CHECKCONTRACTVERIFY</code>.
When evaluating <code>OP_CHECKCONTRACTVERIFY</code> (<code>OP_SUCCESS187</code>,
<code>0xbb</code>), the expected format of the stack, shown bottom to top, is:
<code>0xbb</code>), the expected format of the stack, shown bottom-to-top, is:
<source>
<mode> <taptree> <pk> <index> <data>
<data> <index> <pk> <taptree> <mode>
</source>
where:
@ -462,4 +462,4 @@ without upgrade except for mining and block validation.
== Acknowledgements ==
TODO
TODO