Script - Revision history

Spaced-out-thoughts: Fix spelling of occuring --> occurring

2025-02-06T15:19:23Z

Fix spelling of occuring --> occurring

← Older revision		Revision as of 15:19, 6 February 2025
Line 744:		Line 744:
	\|80		\|80
	\|0x50		\|0x50
	\|'''Transaction is invalid''' unless ~~occuring~~ in an unexecuted OP_IF branch		\|'''Transaction is invalid''' unless occurring in an unexecuted OP_IF branch
	\|-		\|-
	\|OP_VER		\|OP_VER
	\|98		\|98
	\|0x62		\|0x62
	\|'''Transaction is invalid''' unless ~~occuring~~ in an unexecuted OP_IF branch		\|'''Transaction is invalid''' unless occurring in an unexecuted OP_IF branch
	\|-		\|-
	\|OP_VERIF		\|OP_VERIF
	\|101		\|101
	\|0x65		\|0x65
	\|'''Transaction is invalid even when ~~occuring~~ in an unexecuted OP_IF branch'''		\|'''Transaction is invalid even when occurring in an unexecuted OP_IF branch'''
	\|-		\|-
	\|OP_VERNOTIF		\|OP_VERNOTIF
	\|102		\|102
	\|0x66		\|0x66
	\|'''Transaction is invalid even when ~~occuring~~ in an unexecuted OP_IF branch'''		\|'''Transaction is invalid even when occurring in an unexecuted OP_IF branch'''
	\|-		\|-
	\|OP_RESERVED1		\|OP_RESERVED1
	\|137		\|137
	\|0x89		\|0x89
	\|'''Transaction is invalid''' unless ~~occuring~~ in an unexecuted OP_IF branch		\|'''Transaction is invalid''' unless occurring in an unexecuted OP_IF branch
	\|-		\|-
	\|OP_RESERVED2		\|OP_RESERVED2
	\|138		\|138
	\|0x8a		\|0x8a
	\|'''Transaction is invalid''' unless ~~occuring~~ in an unexecuted OP_IF branch		\|'''Transaction is invalid''' unless occurring in an unexecuted OP_IF branch
	\|-		\|-
	\|OP_NOP1, OP_NOP4-OP_NOP10		\|OP_NOP1, OP_NOP4-OP_NOP10

Theymos: Good catch, but the error was in the other direction

2024-11-30T19:05:43Z

Good catch, but the error was in the other direction

← Older revision		Revision as of 19:05, 30 November 2024
Line 32:		Line 32:
	=== Notation on this page ===		=== Notation on this page ===

	In the tables below, the inputs and outputs are both described by items as if they were pushed on the stack in that order. So for example, "x1 x2" indicates pushing value x1 on the stack, then x2, such that x1 is at the bottom of the stack, and x2 is at the top. When writing scripts as human-readable opcodes, the push opcodes and the associated data are usually written as <code><data></code>. For example, a P2SH script would be written as <code>OP_HASH160 <data> OP_EQUAL</code>, where <code><data></code> in this context means the byte <code>~~0x20~~</code> followed by the 32 bytes of the data itself. You should also ensure that you use the appropriate push instruction if your data is very large. See the table below for details.		In the tables below, the inputs and outputs are both described by items as if they were pushed on the stack in that order. So for example, "x1 x2" indicates pushing value x1 on the stack, then x2, such that x1 is at the bottom of the stack, and x2 is at the top. When writing scripts as human-readable opcodes, the push opcodes and the associated data are usually written as <code><data></code>. For example, a P2SH script would be written as <code>OP_HASH160 <data> OP_EQUAL</code>, where <code><data></code> in this context means the byte <code>0x14</code> followed by the 20 bytes of the data itself. You should also ensure that you use the appropriate push instruction if your data is very large. See the table below for details.

	=== Constants ===		=== Constants ===

Tetrapod: /* Notation on this page */ 0x20 is 32 in decimal, not 20

2024-11-30T04:55:18Z

Notation on this page: 0x20 is 32 in decimal, not 20

← Older revision		Revision as of 04:55, 30 November 2024
Line 32:		Line 32:
	=== Notation on this page ===		=== Notation on this page ===

	In the tables below, the inputs and outputs are both described by items as if they were pushed on the stack in that order. So for example, "x1 x2" indicates pushing value x1 on the stack, then x2, such that x1 is at the bottom of the stack, and x2 is at the top. When writing scripts as human-readable opcodes, the push opcodes and the associated data are usually written as <code><data></code>. For example, a P2SH script would be written as <code>OP_HASH160 <data> OP_EQUAL</code>, where <code><data></code> in this context means the byte <code>0x20</code> followed by the 20 bytes of the data itself. You should also ensure that you use the appropriate push instruction if your data is very large. See the table below for details.		In the tables below, the inputs and outputs are both described by items as if they were pushed on the stack in that order. So for example, "x1 x2" indicates pushing value x1 on the stack, then x2, such that x1 is at the bottom of the stack, and x2 is at the top. When writing scripts as human-readable opcodes, the push opcodes and the associated data are usually written as <code><data></code>. For example, a P2SH script would be written as <code>OP_HASH160 <data> OP_EQUAL</code>, where <code><data></code> in this context means the byte <code>0x20</code> followed by the 32 bytes of the data itself. You should also ensure that you use the appropriate push instruction if your data is very large. See the table below for details.

	=== Constants ===		=== Constants ===

Capsqrl: /* External Links */ Remove dead link, webbtc.com has changed owner (Hi, Reddit)

2024-07-02T06:29:12Z

External Links: Remove dead link, webbtc.com has changed owner (Hi, Reddit)

← Older revision		Revision as of 06:29, 2 July 2024
Line 988:		Line 988:
	*[https://bitcoin.sipa.be/miniscript] - Miniscript: a language for writing (a subset of) Bitcoin Scripts in a structured way, enabling analysis, composition, generic signing and more.		*[https://bitcoin.sipa.be/miniscript] - Miniscript: a language for writing (a subset of) Bitcoin Scripts in a structured way, enabling analysis, composition, generic signing and more.
	*[https://github.com/siminchen/bitcoinIDE Bitcoin IDE] – Bitcoin Script for dummies		*[https://github.com/siminchen/bitcoinIDE Bitcoin IDE] – Bitcoin Script for dummies
	*[https://webbtc.com/script Bitcoin Debug Script Execution] – web tool which executes a script opcode-by-opcode
	*[http://www.crmarsh.com/script-playground/ Script Playground] — convert Script to JavaScript		*[http://www.crmarsh.com/script-playground/ Script Playground] — convert Script to JavaScript
	*[https://bitauth.com/ide BitAuth IDE] — an Integrated Development Environment for Bitcoin Authentication		*[https://bitauth.com/ide BitAuth IDE] — an Integrated Development Environment for Bitcoin Authentication

Sipa at 22:25, 26 April 2024

2024-04-26T22:25:07Z

← Older revision		Revision as of 22:25, 26 April 2024
Line 730:		Line 730:
	\|}		\|}

	~~===Pseudo-words===~~
	~~These words are used internally for assisting with transaction matching. They are invalid if used in actual scripts.~~
	~~{\| class="wikitable"~~
	\|-
	~~!Word~~
	~~!Opcode~~
	~~!Hex~~
	~~!Description~~
	\|-
	~~\|OP_PUBKEYHASH~~
	~~\|253~~
	~~\|0xfd~~
	~~\|Represents a public key hashed with OP_HASH160.~~
	\|-
	~~\|OP_PUBKEY~~
	~~\|254~~
	~~\|0xfe~~
	~~\|Represents a public key compatible with OP_CHECKSIG.~~
	\|-
	~~\|OP_INVALIDOPCODE~~
	~~\|255~~
	~~\|0xff~~
	~~\|Matches any opcode that is not yet assigned.~~
	\|}

	=== Reserved words ===		=== Reserved words ===

NotATether: /* Notation on this page */

2024-01-17T09:39:04Z

Notation on this page

← Older revision		Revision as of 09:39, 17 January 2024
Line 32:		Line 32:
	=== Notation on this page ===		=== Notation on this page ===

	In the tables below, the inputs and outputs are both described by items as if they were pushed on the stack in that order. So for example, "x1 x2" indicates pushing value x1 on the stack, then x2, such that x1 is at the bottom of the stack, and x2 is at the top. When writing scripts as human-readable opcodes, the push opcodes and the associated data are usually written as <code><data></code>. For example, a P2SH script would be written as <code>OP_HASH160 <data> OP_EQUAL</code>, where <code><data></code> in this context means the byte <code>0x20</code> followed by the 20 bytes of the data itself.		In the tables below, the inputs and outputs are both described by items as if they were pushed on the stack in that order. So for example, "x1 x2" indicates pushing value x1 on the stack, then x2, such that x1 is at the bottom of the stack, and x2 is at the top. When writing scripts as human-readable opcodes, the push opcodes and the associated data are usually written as <code><data></code>. For example, a P2SH script would be written as <code>OP_HASH160 <data> OP_EQUAL</code>, where <code><data></code> in this context means the byte <code>0x20</code> followed by the 20 bytes of the data itself. You should also ensure that you use the appropriate push instruction if your data is very large. See the table below for details.

	=== Constants ===		=== Constants ===

Carter: /* External Links */ Added BitIDE to the list of tools (Bitcoin Core compatible alternative to BitAuth for users seeking an IDE - as BitAuth's op implementations reflect those of the Bitcoin Cash fork, not Bitcoin Core)

2024-01-14T02:33:34Z

External Links: Added BitIDE to the list of tools (Bitcoin Core compatible alternative to BitAuth for users seeking an IDE - as BitAuth's op implementations reflect those of the Bitcoin Cash fork, not Bitcoin Core)

← Older revision		Revision as of 02:33, 14 January 2024
Line 1,009:		Line 1,009:

	== External Links ==		== External Links ==
			*[https://bitide.qedprotocol.com/ BitIDE] - BitIDE: A web based Bitcoin Script IDE with built in debugger, meta-scripting, virtual op-codes, and local testnet.
	*[https://bitcoin.sipa.be/miniscript] - Miniscript: a language for writing (a subset of) Bitcoin Scripts in a structured way, enabling analysis, composition, generic signing and more.		*[https://bitcoin.sipa.be/miniscript] - Miniscript: a language for writing (a subset of) Bitcoin Scripts in a structured way, enabling analysis, composition, generic signing and more.
	*[https://github.com/siminchen/bitcoinIDE Bitcoin IDE] – Bitcoin Script for dummies		*[https://github.com/siminchen/bitcoinIDE Bitcoin IDE] – Bitcoin Script for dummies

NotATether: use 0x20, not OP_20

2024-01-12T16:30:25Z

use 0x20, not OP_20

← Older revision		Revision as of 16:30, 12 January 2024
Line 32:		Line 32:
	=== Notation on this page ===		=== Notation on this page ===

	In the tables below, the inputs and outputs are both described by items as if they were pushed on the stack in that order. So for example, "x1 x2" indicates pushing value x1 on the stack, then x2, such that x1 is at the bottom of the stack, and x2 is at the top. When writing scripts as human-readable opcodes, the push opcodes and the associated data are usually written as <code><data></code>. For example, a P2SH script would be written as <code>OP_HASH160 <data> OP_EQUAL</code>, where <code><data></code> in this context means <code>~~OP_20~~</code> followed by the 20 bytes of the data itself.		In the tables below, the inputs and outputs are both described by items as if they were pushed on the stack in that order. So for example, "x1 x2" indicates pushing value x1 on the stack, then x2, such that x1 is at the bottom of the stack, and x2 is at the top. When writing scripts as human-readable opcodes, the push opcodes and the associated data are usually written as <code><data></code>. For example, a P2SH script would be written as <code>OP_HASH160 <data> OP_EQUAL</code>, where <code><data></code> in this context means the byte <code>0x20</code> followed by the 20 bytes of the data itself.

	=== Constants ===		=== Constants ===

NotATether: /* Notation on this page */

2024-01-12T16:27:11Z

Notation on this page

← Older revision		Revision as of 16:27, 12 January 2024
Line 32:		Line 32:
	=== Notation on this page ===		=== Notation on this page ===

	In the tables below, the inputs and outputs are both described by items as if they were pushed on the stack in that order. So for example, "x1 x2" indicates pushing value x1 on the stack, then x2, such that x1 is at the bottom of the stack, and x2 is at the top. When writing scripts as human-readable opcodes, the push opcodes and the associated data are usually written as <code><data></code>. For example, a P2SH script would be written as <code>OP_HASH160 <data> OP_EQUAL</code>, where <code><data></code> in this context means <code>OP_20</code> followed by the 20 bytes of the data itself.		In the tables below, the inputs and outputs are both described by items as if they were pushed on the stack in that order. So for example, "x1 x2" indicates pushing value x1 on the stack, then x2, such that x1 is at the bottom of the stack, and x2 is at the top. When writing scripts as human-readable opcodes, the push opcodes and the associated data are usually written as <code><data></code>. For example, a P2SH script would be written as <code>OP_HASH160 <data> OP_EQUAL</code>, where <code><data></code> in this context means <code>OP_20</code> followed by the 20 bytes of the data itself.

	=== Constants ===		=== Constants ===

NotATether: /* Notation on this page */

2024-01-12T16:26:04Z

Notation on this page

← Older revision		Revision as of 16:26, 12 January 2024
Line 32:		Line 32:
	=== Notation on this page ===		=== Notation on this page ===

	In the tables below, the inputs and outputs are both described by items as if they were pushed on the stack in that order. So for example, "x1 x2" indicates pushing value x1 on the stack, then x2, such that x1 is at the bottom of the stack, and x2 is at the top. When writing scripts as human-readable opcodes, the push opcodes and the associated data are usually written as <code><data></code>. For example, a P2SH script would be written as <code>OP_HASH160 <data> OP_EQUAL</code>, where <code><data></code> in this context means <code>OP_20</code> followed by the 20 bytes of the data itself.		In the tables below, the inputs and outputs are both described by items as if they were pushed on the stack in that order. So for example, "x1 x2" indicates pushing value x1 on the stack, then x2, such that x1 is at the bottom of the stack, and x2 is at the top. When writing scripts as human-readable opcodes, the push opcodes and the associated data are usually written as <code><data></code>. For example, a P2SH script would be written as <code>OP_HASH160 <data> OP_EQUAL</code>, where <code><data></code> in this context means <code>OP_20</code> followed by the 20 bytes of the data itself.

	=== Constants ===		=== Constants ===