diff options
| author | fanquake <fanquake@gmail.com> | 2023-08-03 17:33:20 +0100 |
|---|---|---|
| committer | fanquake <fanquake@gmail.com> | 2023-08-03 17:46:43 +0100 |
| commit | da3816e4e80ab917106a88d681b348f82581def5 (patch) | |
| tree | fd7ab7b3d201e6f95cabde45524539cb14267099 /ci/test/01_base_install.sh | |
| parent | 61849f0464f15f92814cd7408023a86e9c32567d (diff) | |
| parent | faafc35a779745d59fdb0e88698b579215f42b08 (diff) | |
| download | bitcoin-da3816e4e80ab917106a88d681b348f82581def5.tar.xz | |
Merge bitcoin/bitcoin#27832: doc: Clarify -datacarriersize, add -datacarriersize=2 tests
faafc35a779745d59fdb0e88698b579215f42b08 doc: Clarify that -datacarriersize applies to the full raw scriptPubKey, not the data push (MarcoFalke)
55550e7fe7e4ffe14637a901b568d1d7e1c716d4 test: Add -datacarriersize=2 tests (MarcoFalke)
Pull request description:
Clarify with a test that `-datacarriersize` applies to the serialized size of the scriptPubKey, not the size of the pushed data. So for example,
* `-datacarriersize=2` will reject a `raw(6a01aa)`, even though only one byte is pushed
* `-datacarriersize=0` (or `-datacarrier=0`) will reject a `raw(6a)`, even though no byte is pushed
* `-datacarriersize=0` (or `-datacarrier=0`) will reject a `raw(6a00)`, even though zero bytes are pushed
ACKs for top commit:
ajtowns:
ACK faafc35a779745d59fdb0e88698b579215f42b08
instagibbs:
ACK https://github.com/bitcoin/bitcoin/pull/27832/commits/faafc35a779745d59fdb0e88698b579215f42b08
Tree-SHA512: f01ace02798f596ac2a02461e9f2a6ef91b3b37c976ea0b3bc860e2d3efb0ace0fd8b779dd18249cee7f84ebbe5fd21d8506afd3a15edadc00b843ff3b4aacc7
Diffstat (limited to 'ci/test/01_base_install.sh')
0 files changed, 0 insertions, 0 deletions