joshua/dash-docs
1
0
Fork 0
mirror of https://github.com/seigler/dash-docs synced 2025-07-27 01:36:13 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

Dev Docs Correction: CHECKMULTISIG Requires Sigs In Same Order As PubKeys

Browse source 
As reported by @gsalgado (thanks!), the docs incorrectly state that all
sigs are compared against all pubkeys.  This commit provides a corrected
description, additional details, and references in other parts of the
text where we mention multisig. (Fixes #622)
This commit is contained in:
David A. Harding 2014-10-28 21:33:26 -04:00
parent 82dcaf218a
commit 1ec71148da
No known key found for this signature in database
GPG key ID: 4B29C30FF29EC4B7
3 changed files with 74 additions and 11 deletions
Download patch file Download diff file Expand all files Collapse all files

5
_includes/guide_contracts.md
View file

@ -94,7 +94,10 @@ OP_0 [A's signature] [B's or C's signature] [serialized redeem script]
(Op codes to push the signatures and redeem script onto the stack are
not shown. `OP_0` is a workaround for an off-by-one error in the original
implementation which must be preserved for compatibility.)
implementation which must be preserved for compatibility. Note that
the signature script must provide signatures in the same order as the
corresponding public keys appear in the redeem script. See the description in
[`OP_CHECKMULTISIG`][op_checkmultisig] for details.)
When the transaction is broadcast to the network, each peer checks the
signature script against the P2SH output Charlie previously paid,