Multisigniture (multisig) refers to requiring more than one key to authorize a Bitcoin transaction.Consider the following scenario:
Suppose I am working with a company that wants to accept Bitcoin for international trades.Multisig is the the solution to this.
The company, for security reasons, would not want a single one of its employees to have access to the company BTC wallet's password. Any transaction would have to meet the approval of more than one employee.Is this possible already? If not, how could it be implemented with public-key cryptography?
A multi-signature address is an address that is associated with more than one ECDSA private key. The simplest type is an m-of-n address - it is associated with n private keys, and sending bitcoins from this address requires signatures from at least m keys. A multi-signature transaction is one that sends funds from a multi-signature address.
Creating a Multisigniture Address
A 2of3 multisig address can be created by following these steps:
addmultisigaddress returns the multisignature address. Be a little careful, the public keys are raw hexadecimal and don't contain checksums like bitcoin addresses do. You can then send funds into that 2-of-3 transaction using the normal sendtoaddress/sendmany RPC commands, or the GUI (or anything that's been updated to recognize multisig addresses).
- Gather (or generate) 3 bitcoin addresses, on whichever machines will be participating, using getnewaddress or getaccountaddress RPC commands (or copy and paste from the GUI).
- Get their public keys using the validateaddress RPC command 3 times.
- Then create a 2-of-3 multisig address using addmultisigaddress; e.g.
bitcoind addmultisigaddress 2 '["044322868cb17d64dcc22185ae2d4493111d73244c3668f8ac79ecc79c0ba8d30a6756d0fa20157 709af3281cc721c7f53321a8cabda29b77900b7e4fe0174b114","..second pubkey..","..third pubkey.."]'