diff options
| author | MarcoFalke <falke.marco@gmail.com> | 2020-11-27 10:59:14 +0100 |
|---|---|---|
| committer | MarcoFalke <falke.marco@gmail.com> | 2020-11-27 10:59:24 +0100 |
| commit | e2ff5e7b35d71195278d2a2ed9485f141de33d7a (patch) | |
| tree | 6ef36ea0f3fd3471df6b95530247e464b90acf35 /src/qt/askpassphrasedialog.cpp | |
| parent | 50091592dd875a1c94030dbed74112b003732d68 (diff) | |
| parent | e416cfc92bf51f6fd088ab61c2306c5e73877dd0 (diff) | |
Merge #20497: [Refactor] Add MAX_STANDARD_SCRIPTSIG_SIZE to policy
e416cfc92bf51f6fd088ab61c2306c5e73877dd0 Add MAX_STANDARD_SCRIPTSIG_SIZE to policy (sanket1729)
Pull request description:
Bitcoin core has a standardness rule for max satisfaction script sig size.
This PR adds to the policy header file so that it is documented along with
along policy rules. The initial reasoning that 1650 is an implicit
limit(would not reach assuming all other policy rules are being
followed) is outdated.
As we now know, bitcoin transactions can have spend conditions are more than
just signatures and there may exist p2sh transactions involving 100 byte
preimages that maybe non-standard because of this rule. Because this
rule is no longer implicit, we should explicitly document it in policy
header file
ACKs for top commit:
sipa:
utACK e416cfc92bf51f6fd088ab61c2306c5e73877dd0
practicalswift:
cr ACK e416cfc92bf51f6fd088ab61c2306c5e73877dd0
theStack:
Code Review ACK e416cfc92bf51f6fd088ab61c2306c5e73877dd0
Tree-SHA512: 1a91ee23dfb6085807e04dd0687d7a443e0f3e0f52d0a995a6599dff28533b0b599afba2724735d93948a64a3e25d0bc016ce3e771c0bd453eef78b22dc2369d
Diffstat (limited to 'src/qt/askpassphrasedialog.cpp')
0 files changed, 0 insertions, 0 deletions