Before you start
Computer tools, KeySigner on iPhone and Bitcoin Core regtest
- Use a shared Bitcoin wallet with an explicit threshold and its matching wallet descriptor. Each input needs signatures from the required number of members. Use a new regtest wallet and test coins.
Data and access
Who does what
Check the shared wallet's rule
In your KeySigner test deployment, have the administrator configure a Bitcoin account with three test keys and two required for payment. Run keysigner-btc multisig ACCOUNT --network regtest with your test account name. Compare the descriptor, address and threshold with your test configuration.
Check. The output shows a 2-of-3 descriptor and the expected regtest address. Compare all three public keys with your test configuration.
Prepare a payment from the shared address
Fund the shared address with regtest coins. Use Bitcoin Core to prepare payment.psbt with the shared wallet descriptor and the amounts for its inputs. Check that your change returns to the shared address.
Check. Decode the PSBT in Bitcoin Core and check the funded inputs, recipient amount, fee and shared-address change.
Try the payment with one member
Run keysigner-btc sign-psbt --network regtest --key PUBLIC_KEY payment.psbt with the first member's public key. Review and approve on that member's device. Save the partially signed file and check that keysigner-btc finalize-multisig refuses to finalize it.
Check. The first signature is present in the PSBT. Finalization with that file alone fails.
Add a second member and verify
Have a second member sign the same proposal with their wallet after comparing the recipient, amount and fee. Combine the signatures if the wallet returned a separate PSBT. Run keysigner-btc finalize-multisig on the file containing both signatures and check the result with Bitcoin Core on regtest.
Check. The finalized transaction has the reviewed outputs. Bitcoin Core accepts it on regtest.
Check your result
One member's signature cannot complete this payment. With two valid member signatures for each input, Bitcoin Core accepts the finalized transaction. Changing the members creates a different wallet address. Coins at the old address still require its original keys.
What we tested
Tested on . A local Bitcoin Core 32.1 regtest run used a simulated phone for the first signature and an independent test key for the second. Finalization failed with one signature. With both, Bitcoin Core accepted the resulting transaction on regtest.
If you get stuck
The wallet cannot finalize after two members approved
Confirm that both signatures are on the same unsigned transaction and apply to each input being spent. Compare the current proposal's descriptor with the descriptor that funded the coins.