BIP 0016 QA

Send coins using GUI, RCP sendtoaddress, and RCP sendmany commands<br /> Result: coins sent in all cases

Run 0.6 bitcoind, get a public key with: ./bitcoind -testnet validateaddress $(./bitcoind -testnet getnewaddress)<br /> Generate a multisig 1-of-1 address: ./bitcoind addmultisigaddress 1 {public key from above}<br /> Send-to-self some bitcoins using that address<br /> Result: transaction is confirmed by network, displays properly in listtransactions. Result: balance is unaffected

Run 0.6 bitcoind, get 2 new bitcoin addresses<br /> Generate a multisig 1-of-2 address: ./bitcoind addmultisigaddress 1 {address1} {address2}<br /> Send-to-self some bitcoins using that address<br /> Result: transaction is confirmed by network, displays properly in listtransactions. Result: bitcoin balance is unaffected.

Repeat test procedures above, with the other new multisignature transaction types

Repeat test procedures above, but use two bitcoinds, prepared as follows:<br /> bitcoind 1 : Run getnewaddress and addmultisigaddress<br /> bitcoind 2 : Just addmultisigaddress<br /> Send coins from 2 to 1 using the address<br /> Result: transaction is accepted/confirmed by network<br /> Result: balance for 2 goes down, listtransactions for 2 displays correct result<br /> Result: balance for 1 goes up, listtransactions for 1 displays correct result<br />

Fund a new, empty wallet entirely with multisig transactions<br /> Wait for transactions to confirm<br /> Use sendtoaddress and sendmany to generate spend-from-multisig transactions<br /> Spend to both single-address and multisig address, and test send-to-other and send-to-self<br /> Result: transactions are accepted/confirmed by network<br /> Result: balance decreases, listtransactions displays correct information<br />

Result: balance and transactions displayed correctly

Send coins using GUI, RCP sendtoaddress, and RCP sendmany commands<br /> Result: coins sent in all cases

Mine coins using built-in miner<br /> Result: blocks accepted, show up on blockexplorer.com/testnet<br /> Result: mined blocks’ coinbase contains /P2SH/ string

Mine coins using getwork interface<br /> Result: blocks accepted, show up on blockexplorer.com/testnet<br /> Result: mined blocks’ coinbase contains /P2SH/ string

Mine coins using getmemorypool interface<br /> Result: blocks accepted, show up on blockexplorer.com/testnet<br /> Result: mined blocks’ coinbase contains /P2SH/ string

Mine coins using built-in miner<br /> Result: blocks accepted, show up on blockexplorer.com/testnet<br /> Result: mined blocks’ coinbase contains /P2SH/ string

Mine coins using getwork interface<br /> Result: blocks accepted, show up on blockexplorer.com/testnet<br /> Result: mined blocks’ coinbase contains /P2SH/ string

Mine coins using built-in miner<br /> Result: blocks accepted, show up on blockexplorer.com/testnet<br /> Result: mined blocks’ coinbase contains /P2SH/ string

Mine coins using getwork interface<br /> Result: blocks accepted, show up on blockexplorer.com/testnet<br /> Result: mined blocks’ coinbase contains /P2SH/ string

Mine coins using getmemorypool interface<br /> Result: blocks accepted, show up on blockexplorer.com/testnet<br /> Result: mined blocks’ coinbase contains /P2SH/ string

multisignature signing/verification<br /> multisignature invalid signature failure<br /> multisignature IsStandard() success/failure<br /> extraction of addresses from multisignature transactions<br /> BIP 16 IsStandard() success/failure (including failure with OP_PUSHDATA1/2/4)<br /> BIP 16 AreInputsStandard() success/failure<br /> BIP 16 compatibility with other 3 standard transaction types<br /> BIP 16 no-recursion test<br /> BIP 16 switchover date logic<br /> OP_CHECKMULTISIG counting of signature operations inside BIP 16 transactions<br />

Result: blocks created properly Result: blocks include /P2SH/ string in their coinbase

Result: blocks created properly Result: blocks include /P2SH/ string in their coinbase

Create two valid hash, invalid signature transactions in two blocks separated in time on a testnet-in-a-box chain<br /> Run a bitcoind to synchronize with the chain, with -paytoscripthashtime set in between the two blocks<br/> Result: first transaction/block accepted, second causes a chain split<br/> Re-run bitcoind with -paytoscripthashtime in the future<br/> Result: entire chain accepted