[PULL] Add scriptPubKey enforced sendescrow and redeemescrow API calls



Summary:

Gavin Andresen proposed the creation of a new type of bitcoin address that is an "m of n address" which requires m of n signatures to spend. He suggested publishing a really long address with all n public keys, citing his current 2-of-3 example as a new address type. Gavin also wondered if the straightforward "n PUBKEYS m CHECKMULTISIG" transaction type is the right thing to do and suggested that 2 of 2 and 2 of three should be done following the pattern of the standard DUP HASH160 etc. transaction type. Spending those transactions would mean putting the m signatures and the n public keys in the TxIn, but sending funds would only require the hash of the sum of the public keys. The major advantage of summing is shorter address for the end user to copy-paste. This is similar to the way the current implementation works that uses HASH160, but there's no attempt to save space by hashing the sum of the pubkeys.


Updated on: 2023-05-26T18:12:42.419952+00:00