dido:public:ra:xapend:xapend.b_stds:defact:bitcoin:bips:bip_0011
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
dido:public:ra:xapend:xapend.b_stds:defact:bitcoin:bips:bip_0011 [2020/05/18 21:49] char |
dido:public:ra:xapend:xapend.b_stds:defact:bitcoin:bips:bip_0011 [2021/08/13 16:05] (current) murphy |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ==== BIP 0011 - M-of-N Standard Transactions ==== | ==== BIP 0011 - M-of-N Standard Transactions ==== | ||
| - | [[dido:public:ra:xapend.stds:defact:bitcoin| return to the Bitcoin Standards ]] | + | [[dido:public:ra:xapend:xapend.b_stds:defact:bitcoin:bips| return to the Bitcoin Improvement Proposals ]] |
| <table> | <table> | ||
| Line 16: | Line 16: | ||
| </table> | </table> | ||
| - | **Note**: The following is an excerpt from the official Bitcoin site. It is provided here as a convenience and is not authoritative. Refer to the original document(s) as the authoritative reference. | + | **Note**: The following is an excerpt from the official [[dido:public:ra:xapend:xapend.a_glossary:b:bitcoin|Bitcoin]] site. It is provided here as a convenience and is not authoritative. Refer to the original document(s) as the authoritative reference. |
| === Abstract === | === Abstract === | ||
| Line 26: | Line 26: | ||
| //A couple of motivating use cases:// | //A couple of motivating use cases:// | ||
| - | * //A wallet secured by a "wallet protection service" (WPS). 2-of-2 signatures required transactions will be used, with one signature coming from the (possibly compromised) computer with the wallet and the second signature coming from the WPS. When sending protected bitcoins, the user's bitcoin client will contact the WPS with the proposed transaction and it can then contact the user for confirmation that they initiated the transaction and that the transaction details are correct. Details for how clients and WPS's communicate are outside the scope of this BIP. Side note: customers should insist that their wallet protection service provide them with copies of the private key(s) used to secure their wallets that they can safely store off-line, so that their coins can be spent even if the WPS goes out of business.// | + | * //A [[dido:public:ra:xapend:xapend.a_glossary:b:bitcoin_wallet |
| + | |wallet]] secured by a "wallet protection service" (WPS). 2-of-2 signatures required transactions will be used, with one signature coming from the (possibly compromised) computer with the wallet and the second signature coming from the WPS. When sending protected bitcoins, the user's bitcoin [[dido:public:ra:xapend:xapend.a_glossary:c:client|client]] will contact the WPS with the proposed transaction and it can then contact the user for [[dido:public:ra:xapend:xapend.a_glossary:c:confirmation|confirmation]] that they initiated the transaction and that the transaction details are correct. Details for how clients and WPS's communicate are outside the scope of this BIP. Side note: customers should insist that their wallet protection service provide them with copies of the [[dido:public:ra:xapend:xapend.a_glossary:p:private_key|private key(s)]] used to secure their wallets that they can safely store off-line, so that their [[dido:public:ra:xapend:xapend.a_glossary:c:coins|coins]] can be spent even if the WPS goes out of business.// | ||
| - | * //Three-party escrow (buyer, seller and trusted dispute agent). 2-of-3 signatures required transactions will be used. The buyer and seller and agent will each provide a public key, and the buyer will then send coins into a 2-of-3 CHECKMULTISIG transaction and send the seller and the agent the transaction id. The seller will fulfill their obligation and then ask the buyer to co-sign a transaction (already signed by seller) that sends the tied-up coins to him (seller).// | + | * //Three-party escrow (buyer, seller and trusted dispute agent). 2-of-3 signatures required transactions will be used. The buyer and seller and agent will each provide a [[dido:public:ra:xapend:xapend.a_glossary:p:public_key|public key]], and the buyer will then send coins into a 2-of-3 CHECKMULTISIG transaction and send the seller and the agent the transaction id. The seller will fulfill their obligation and then ask the buyer to co-sign a transaction (already signed by seller) that sends the tied-up coins to him (seller).// |
| //If the buyer and seller cannot agree, then the agent can, with the cooperation of either buyer or seller, decide what happens to the tied-up coins. Details of how buyer, seller, and agent communicate to gather signatures or public keys are outside the scope of this BIP.// | //If the buyer and seller cannot agree, then the agent can, with the cooperation of either buyer or seller, decide what happens to the tied-up coins. Details of how buyer, seller, and agent communicate to gather signatures or public keys are outside the scope of this BIP.// | ||
dido/public/ra/xapend/xapend.b_stds/defact/bitcoin/bips/bip_0011.1589852976.txt.gz · Last modified: 2020/05/18 21:49 by char
