diff options
| author | Peter Todd <pete@petertodd.org> | 2014-02-28 23:02:42 -0500 |
|---|---|---|
| committer | Peter Todd <pete@petertodd.org> | 2014-02-28 23:11:15 -0500 |
| commit | e5d0289c3e0df888277b92cf807aa86335203113 (patch) | |
| tree | 9539cd36c0aa7af44dda6e2052a176d94a1931a9 | |
| parent | e07791556156baf4dc1d938738af4e8c02d47027 (diff) | |
| download | bips-e5d0289c3e0df888277b92cf807aa86335203113.tar.xz | |
Document 520-byte serialized script limit
| -rw-r--r-- | bip-0016.mediawiki | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/bip-0016.mediawiki b/bip-0016.mediawiki index 2f58858..5251ba6 100644 --- a/bip-0016.mediawiki +++ b/bip-0016.mediawiki @@ -96,6 +96,11 @@ On February 1, 2012, the block-chain will be examined to determine the number of If a majority of hashing power does not support the new validation rules, then rollout will be postponed (or rejected if it becomes clear that a majority will never be achieved). +===520-byte limitation on serialized script size=== + +As a consequence of the requirement for backwards compatiblity the serialized script is itself subject to the same rules as any other PUSHDATA operation, including the rule that no data greater than 520 bytes may be pushed to the stack. Thus is it not possible to spend a P2SH output if the redemption script it refers to is >520 bytes in length. For instance while the OP_CHECKMULTISIG opcode can itself accept up to 20 pubkeys, with 33-byte compressed pubkeys it is only possible to spend a P2SH output requiring a maximum of 15 pubkeys to redeem: 3 bytes + 15 pubkeys * 34 bytes/pubkey = 513 bytes. + + ==Reference Implementation== https://gist.github.com/gavinandresen/3966071 |