diff options
| -rw-r--r-- | README.mediawiki | 2 | ||||
| -rw-r--r-- | bip-0010.mediawiki | 5 | ||||
| -rw-r--r-- | bip-0032.mediawiki | 2 | ||||
| -rw-r--r-- | bip-0062.mediawiki | 4 |
4 files changed, 7 insertions, 6 deletions
diff --git a/README.mediawiki b/README.mediawiki index 8ad9e17..54a7229 100644 --- a/README.mediawiki +++ b/README.mediawiki @@ -23,7 +23,7 @@ Those proposing changes should consider that ultimately consent may rest with th | Multi-Sig Transaction Distribution | Alan Reiner | Informational -| Draft +| Withdrawn |- style="background-color: #cfffcf" | [[bip-0011.mediawiki|11]] | M-of-N Standard Transactions diff --git a/bip-0010.mediawiki b/bip-0010.mediawiki index b3d750b..4307f3e 100644 --- a/bip-0010.mediawiki +++ b/bip-0010.mediawiki @@ -2,7 +2,7 @@ BIP: 10 Title: Multi-Sig Transaction Distribution Author: Alan Reiner - Status: Draft + Status: Withdrawn Type: Informational Created: 2011-10-28 </pre> @@ -96,5 +96,4 @@ A party receiving this TxDP can simply add their signature to the appropriate _T == Reference Implementation == -This proposal has been implemented and tested in the ''Armory'' Bitcoin software for use in offline-wallet transaction signing (as a 1-of-1 transaction), and will eventually use it for multi-signature transcations. The source code for this implementation be found in the [https://github.com/etotheipi/BitcoinArmory/blob/qtdev/armoryengine.py Armory Github project]. Specifically, the [https://github.com/etotheipi/BitcoinArmory/blob/qtdev/armoryengine.py#L4704 PyTxDistProposal class] implements all features of BIP 0010. It contains reference code for both -[https://github.com/etotheipi/BitcoinArmory/blob/qtdev/armoryengine.py#L5095 serializing a TxDP] and [https://github.com/etotheipi/BitcoinArmory/blob/qtdev/armoryengine.py#L5143 unserializing a TxDP]. +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. diff --git a/bip-0032.mediawiki b/bip-0032.mediawiki index e8dcd12..8a953f8 100644 --- a/bip-0032.mediawiki +++ b/bip-0032.mediawiki @@ -2,7 +2,7 @@ RECENT CHANGES: * (16 Apr 2013) Added private derivation for i ≥ 0x80000000 (less risk of parent private key leakage) * (30 Apr 2013) Switched from multiplication by I<sub>L</sub> to addition of I<sub>L</sub> (faster, easier implementation) * (25 May 2013) Added test vectors -* (15 Jan 2014) Rename keys with index ≥ 0x8000000 to hardened keys, and add explicit conversion functions. +* (15 Jan 2014) Rename keys with index ≥ 0x80000000 to hardened keys, and add explicit conversion functions. <pre> BIP: 32 diff --git a/bip-0062.mediawiki b/bip-0062.mediawiki index 9d5bfe5..4e5653b 100644 --- a/bip-0062.mediawiki +++ b/bip-0062.mediawiki @@ -63,7 +63,9 @@ Below is a summary of the effects on signatures, their encoding and data pushes. The value S in signatures must be between 0x1 and 0x7FFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF 5D576E73 57A4501D DFE92F46 681B20A0 (inclusive). If S is too high, simply replace it by S' = 0xFFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFE BAAEDCE6 AF48A03B BFD25E8C D0364141 - S. -The constraints on the value R is unchanged w.r.t. ECDSA, and can be between 0x1 and 0xFFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFE BAAEDCE6 AF48A03B BFD25E8C D0364140 (inclusive). +Signatures produced by the OpenSSL library are not guaranteed to be consistent with this constraint. Version 0.9.3 of the reference client provides [https://github.com/bitcoin/bitcoin/blob/0.9.3/src/key.cpp#L202-L227 an example] for detection and correction. + +The constraints on the value R are unchanged w.r.t. ECDSA, and values can be between 0x1 and 0xFFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFE BAAEDCE6 AF48A03B BFD25E8C D0364140 (inclusive). ====DER encoding==== For reference, here is how to encode signatures correctly in DER format. |