Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

bip-0141: clarify the sigop count calculation for CHECKMULTISIG #1054

Merged
merged 1 commit into from Feb 3, 2021
Merged

bip-0141: clarify the sigop count calculation for CHECKMULTISIG #1054

merged 1 commit into from Feb 3, 2021

Commits on Jan 11, 2021

  1. bip-0141: clarify the sigop count calculation for CHECKMULTISIG 

    Since the sigOpCount calculation was copied from P2SH, and P2SH
restricts the use of CHECKMULTISIG with pushed integers the reference
implementation would not take into account the number of public keys for
17 to 20 keys (not representable with an OP_N) even for P2WSH.
Therefore it fallbacks to accounting for 20 sigops in this case, which
this sentence seemed to mismatch with.

Btcd and Libbitcoin use the same calculation as in Bitcoin Core.

Signed-off-by: Antoine Poinsot <darosior@protonmail.com>
    @darosior
    darosior committed Jan 11, 2021
    Configuration menu
    Copy the full SHA
    644610f View commit details
    Browse the repository at this point in the history