BIP 0010 - Revision history

934: Update BIP text with latest version from https://github.com/bitcoin/bips/blob/c66583158b9cde82/bip-0010.mediawiki

2024-04-22T17:07:46Z

Update BIP text with latest version from https://github.com/bitcoin/bips/blob/c66583158b9cde82/bip-0010.mediawiki

← Older revision		Revision as of 17:07, 22 April 2024
Line 97:		Line 97:
	In this transaction, there are two inputs, one of 150 BTC and the other of 12 BTC. This transaction combines 162 BTC to create two outputs, one of 160 BTC, one 1.9995 BTC, and a tx fee of 0.0005. In this TxDP, both inputs have been signed, and thus could broadcast immediately.		In this transaction, there are two inputs, one of 150 BTC and the other of 12 BTC. This transaction combines 162 BTC to create two outputs, one of 160 BTC, one 1.9995 BTC, and a tx fee of 0.0005. In this TxDP, both inputs have been signed, and thus could broadcast immediately.

	The style of communication is taken directly from PGP/GPG, which uses blocks of ASCII like this to communicate encrypted messages and signatures. This serialization is compact, and will be ~~interpretted~~ the same in all character encodings. It can be copied inline into an email, or saved in a text file. The advantage over the analogous PGP encoding is that there are some human readable elements to it, for users that wish to examine the TxDP packet manually, instead of requiring a program to parse the core elements of the TxDP.		The style of communication is taken directly from PGP/GPG, which uses blocks of ASCII like this to communicate encrypted messages and signatures. This serialization is compact, and will be interpreted the same in all character encodings. It can be copied inline into an email, or saved in a text file. The advantage over the analogous PGP encoding is that there are some human readable elements to it, for users that wish to examine the TxDP packet manually, instead of requiring a program to parse the core elements of the TxDP.

	A party receiving this TxDP can simply add their signature to the appropriate _TXINPUT_ line. If that is the last signature required, they can broadcast it themselves. Any software that implements this standard should be able to combine multiple TxDPs into a single TxDP. However, even without the programmatic support, a user could manually combine them by copying the appropriate _TXSIGS_ lines between serializations, though it is not the recommended method for combining TxDPs.		A party receiving this TxDP can simply add their signature to the appropriate _TXINPUT_ line. If that is the last signature required, they can broadcast it themselves. Any software that implements this standard should be able to combine multiple TxDPs into a single TxDP. However, even without the programmatic support, a user could manually combine them by copying the appropriate _TXSIGS_ lines between serializations, though it is not the recommended method for combining TxDPs.
Line 103:		Line 103:
	== Reference Implementation ==		== Reference Implementation ==

	This proposal was implemented and tested in the older versions of ''Armory'' Bitcoin software for use in offline-wallet transaction signing (as a 1-of-1 transaction). Implementation can be found in https://github.com/etotheipi/BitcoinArmory/blob/v0.91-beta/armoryengine/Transaction.py under the class PyTxDistProposal. However, as of ~~verion~~ 0.92 released in July 2014, Armory no longer uses this proposal for offline wallet transaction signing and has moved on to a new format.		This proposal was implemented and tested in the older versions of ''Armory'' Bitcoin software for use in offline-wallet transaction signing (as a 1-of-1 transaction). Implementation can be found in https://github.com/etotheipi/BitcoinArmory/blob/v0.91-beta/armoryengine/Transaction.py under the class PyTxDistProposal. However, as of version 0.92 released in July 2014, Armory no longer uses this proposal for offline wallet transaction signing and has moved on to a new format.

934: Update BIP text with latest version from https://github.com/bitcoin/bips/blob/b5723035e23896d0/bip-0010.mediawiki

2019-09-24T17:59:09Z

Update BIP text with latest version from https://github.com/bitcoin/bips/blob/b5723035e23896d0/bip-0010.mediawiki

@@ Line 1: / Line 1: @@
 {{bip}}
 <pre>
    BIP: 10
    Title: Multi-Sig Transaction Distribution
-   Author: Alan Reiner
+   Author: Alan Reiner <etotheipi@gmail.com>
    Status: Withdrawn
    Type: Informational
-   Created: 28-10-2011
+   Created: 2011-10-28
 </pre>
-{{BipMoved|bip-0010.mediawiki}}
+The following is an example TxDP from Armory, produced while running on the test network.  Its DPID is 3fX59xPj:
-[[Category:BIP|D]]
+This proposal was implemented and tested in the older versions of ''Armory'' Bitcoin software for use in offline-wallet transaction signing (as a 1-of-1 transaction). Implementation can be found in https://github.com/etotheipi/BitcoinArmory/blob/v0.91-beta/armoryengine/Transaction.py under the class PyTxDistProposal. However, as of verion 0.92 released in July 2014, Armory no longer uses this proposal for offline wallet transaction signing and has moved on to a new format.

934: Removing redundant parameter.

2015-12-29T13:44:13Z

Removing redundant parameter.

← Older revision		Revision as of 13:44, 29 December 2015
Line 10:		Line 10:
	</pre>		</pre>

	{{BipMoved\|bip-0010.mediawiki~~\|BIP 0010~~}}		{{BipMoved\|bip-0010.mediawiki}}

	[[Category:BIP\|D]]		[[Category:BIP\|D]]

TheRealSteve: updated status

2015-06-13T15:01:00Z

updated status

← Older revision		Revision as of 15:01, 13 June 2015
Line 5:		Line 5:
	Title: Multi-Sig Transaction Distribution		Title: Multi-Sig Transaction Distribution
	Author: Alan Reiner		Author: Alan Reiner
	Status: ~~Draft~~		Status: Withdrawn
	Type: Informational		Type: Informational
	Created: 28-10-2011		Created: 28-10-2011

Wumpus: Move to github

2013-12-06T07:34:07Z

Move to github

@@ Line 10: / Line 10: @@
 </pre>
-A multi-signature transaction is one where a certain number of Bitcoins are "encumbered" with more than one recipient address.  The subsequent transaction that spends these coins will require each party involved (or some subset, depending on the script), to see the proposed transaction and sign it with their private key.  This necessarily requires collaboration between all parties -- to propose a distribution of encumbered funds, collect signatures from all necessary participants, and then broadcast the completed transaction.
+{{BipMoved|bip-0010.mediawiki|BIP 0010}}
 [[Category:BIP|D]]

Nanotube: Removed protection from "BIP 0010"

2013-01-18T14:57:19Z

Removed protection from "BIP 0010"

← Older revision	Revision as of 14:57, 18 January 2013
(No difference)

Genjix at 17:11, 16 April 2012

2012-04-16T17:11:49Z

← Older revision		Revision as of 17:11, 16 April 2012
Line 1:		Line 1:
			{{bip}}

	<pre>		<pre>
	BIP: 10		BIP: 10

Genjix: Protected "BIP 0010": submit bips to genjix ([edit=sysop] (indefinite) [move=sysop] (indefinite))

2012-01-31T21:38:04Z

Protected "BIP 0010": submit bips to genjix ([edit=sysop] (indefinite) [move=sysop] (indefinite))

← Older revision	Revision as of 21:38, 31 January 2012
(No difference)

Etotheipi at 01:25, 31 January 2012

2012-01-31T01:25:58Z

← Older revision		Revision as of 01:25, 31 January 2012
Line 33:		Line 33:
	Anyone adopting BIP 0010 for multi-sig transactions will use the following format (without indentation):		Anyone adopting BIP 0010 for multi-sig transactions will use the following format (without indentation):

	'-----BEGIN-TRANSACTION-TXDPID-------'		'-----BEGIN-TRANSACTION-TXDPID-------'
	("_TXDIST_") (magicBytes) (base58Txid) (varIntTxSize)		("_TXDIST_") (magicBytes) (base58Txid) (varIntTxSize)
	(serializedTxListInHex_Line1)		(serializedTxListInHex_Line1)
	(serializedTxListInHex_Line2)		(serializedTxListInHex_Line2)
	(serializedTxListInHex_Line3)		(serializedTxListInHex_Line3)
	...		...
	("_TXINPUT_") (00) (InputValue)		("_TXINPUT_") (00) (InputValue)
	("_SIG_") (AddrBase58) (SigBytes) (SigHexPart0)		("_SIG_") (AddrBase58) (SigBytes) (SigHexPart0)
	(SigHexRemainingLines)		(SigHexRemainingLines)
	("_SIG_") (AddrBase58) (SigBytes) (SigHexPart0)		("_SIG_") (AddrBase58) (SigBytes) (SigHexPart0)
	(SigHexRemainingLines)		(SigHexRemainingLines)
	("_TXINPUT_") (01) (InputValue)		("_TXINPUT_") (01) (InputValue)
	("_SIG_") (AddrBase58) (SigBytes) (SigHexPart0)		("_SIG_") (AddrBase58) (SigBytes) (SigHexPart0)
	(SigHexRemainingLines)		(SigHexRemainingLines)
	("_TXINPUT_") (02) (InputValue)		("_TXINPUT_") (02) (InputValue)
	'-------END-TRANSACTION-TXDPID-------'		'-------END-TRANSACTION-TXDPID-------'


	The following is an example TxDP from Armory, produced while running on the test network. Its DPID is 3fX59xPj:		The following is an example TxDP from Armory, produced while running on the test network. Its DPID is 3fX59xPj:

Etotheipi at 01:23, 31 January 2012

2012-01-31T01:23:25Z

Show changes