mirror of
https://github.com/bitcoinbook/bitcoinbook
synced 2024-11-23 00:28:14 +00:00
Made changes to ch05.asciidoc
This commit is contained in:
parent
02b78ca531
commit
ba022d5263
@ -342,7 +342,7 @@ Transactions are valid if the top result on the stack is TRUE (noted as +{0x01}+
|
||||
[[std_tx]]
|
||||
=== Standard Transactions
|
||||
|
||||
In the first few years of bitcoin's development, the developers introduced some limitations in the types of scripts that could be processed by the reference client. These limitations are encoded in a function called +isStandard()+, which defines five types of "standard" transactions. These limitations are temporary and may be lifted by the time you read this. Until then, the five standard types of transaction scripts are the only ones that will be accepted by the reference client and most miners who run the reference client. Although it is possible to create a nonstandard transaction containing a script that is not one of the standard types, you must find a miner who does not follow these limitations, to mine that transaction into a block.
|
||||
In the first few years of bitcoin's development, the developers introduced some limitations in the types of scripts that could be processed by the reference client. These limitations are encoded in a function called +isStandard()+, which defines five types of "standard" transactions. These limitations are temporary and might be lifted by the time you read this. Until then, the five standard types of transaction scripts are the only ones that will be accepted by the reference client and most miners who run the reference client. Although it is possible to create a nonstandard transaction containing a script that is not one of the standard types, you must find a miner who does not follow these limitations, to mine that transaction into a block.
|
||||
|
||||
Check the source code of the Bitcoin Core client (the reference implementation) to see what is currently allowed as a valid transaction script.
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user