diff options
Diffstat (limited to 'bip-0142.mediawiki')
| -rw-r--r-- | bip-0142.mediawiki | 180 |
1 files changed, 87 insertions, 93 deletions
diff --git a/bip-0142.mediawiki b/bip-0142.mediawiki index 7efeca7..7d7b1d2 100644 --- a/bip-0142.mediawiki +++ b/bip-0142.mediawiki @@ -1,6 +1,6 @@ <pre> BIP: 142 - Title: Address Formats for Witness Program + Title: Address Format for Segregated Witness Author: Johnson Lau <jl2012@xbt.hk> Status: Draft Type: Standards Track @@ -9,149 +9,143 @@ == Abstract == -This BIP describes 2 new types of Bitcoin address to support native Segregated Witness (segwit) transactions. The first type resembles the original P2PKH base-58 address. The second type is a z-base-32 representation of a witness program with Damm algorithm checksum, which supports arbitrarily complex transactions, and is forward compatible to new version witness programs in the future. +This BIP describes new types of Bitcoin address to support native segregated witness transactions with 20-byte and 32-byte program. == Motivation == -To define standard payment addresses for native segwit transactions to promote early adoption of the more efficient transaction method. +To define standard payment address for native segregated witness (segwit) transactions to promote early adoption of the more efficient transaction method. == Specification == -=== P2PKH segwit address === +The new Bitcoin address format defined is for the Pay-to-Witness-Public-Key-Hash (P2WPKH) and Pay-to-Witness-Script-Hash (P2WSH) transaction described in segregated witness soft fork (BIP141). The scriptPubKey is an OP_0 followed by a push of 20-byte-hash (P2WPKH) or 32-byte hash (P2WSH). -The first new Bitcoin address format defined is specific to pay-to-public-key-hash segwit transaction. The scriptPubKey is a single push of version-0 witness program in this form, - <0x0076A914{20-byte-hash-value}88AC> -The new address is encoded exactly in the same way as the original pay-to-public-key-hash address: - base58-encode: [1-byte version][20-byte-hash-value][4-byte checksum] -Version byte is 0x19 for a main-network address, 0x41 for a testnet address. The following 20-byte is the public key hash. And the 4-byte checksum is the first four bytes of the double SHA256 hash of the version and public key hash. +The new address is encoded in a simlar way as existing address formats: + + base58-encode: + [1-byte address version] + [1-byte witness program version] + [0x00] + [20/32-byte-hash] + [4-byte checksum] + +For P2WPKH address, the address version is 6 (0x06) for a main-network address or 3 (0x03) for a testnet address. -All addresses generated with this scheme will a constant length of 34 characters, with a "B" prefix for main-network and "T" prefix for testnet. +For P2WSH address, the address version is 10 (0x0A) for a main-network address or 40 (0x28) for a testnet address. -=== General segwit address === +The witness program version is an 1-byte value between 0 (0x00) and 16 (0x10). Only version 0 is defined in BIP141. Versions 1 to 16 are reserved for future extensions. -The second new bitcoin address format defined is applicable to witness program of version 0 to 15 with a length of 2 to 32 bytes. +Following the witness program version is a 0x00 padding to make sure that each witness program version will have an unique prefix. -The z-base-32 character set is used: -{|class="wikitable" style="width:40ex; text-align: center; margin: 0 auto 0 auto;" -!width="12%"|Value -!width="12%"|Symbol -!width="12%"|Value -!width="12%"|Symbol -!width="12%"|Value -!width="12%"|Symbol -!width="12%"|Value -!width="12%"|Symbol +Following the padding is the program hash, 20 byte for a P2WPKH address and 32 byte for a P2WSH address. + +The 4-byte checksum is the first four bytes of the double SHA256 hash of the serialization of the previous items. + +All addresses generated with this scheme will have a constant length, with 36 digits for 20-byte and 53 digits for 32-byte. Different witness program version will have an unique prefix shown in the following table: + +{|class="wikitable" style="text-align: center;" +|- +!rowspan=3 style=""|Witness program version +!colspan=4 style=""|Hash size +|- +!colspan=2 style=""|20-byte (36 digits) +!colspan=2 style=""|32-byte (53 digits) +|- +!Mainnet +!Testnet +!Mainnet +!Testnet +|- +|0||p2||QW||7Xh||T7n +|- +|1||p4||QY||7Xq||T7w +|- +|2||p6||Qa||7Xz||T85 +|- +|3||p7||Qc||7Y9||T8E +|- +|4||pA||Qe||7YH||T8N +|- +|5||pB||Qf||7YS||T8X +|- +|6||pD||Qh||7Ya||T8g +|- +|7||pF||Qj||7Yj||T8p +|- +|8||pG||Qm||7Yt||T8y |- -| 0 || y || 8 || e || 16 || o || 24 || a +|9||pJ||Qn||7Z2||T97 |- -| 1 || b || 9 || j || 17 || t || 25 || 2 +|10||pL||Qp||7ZB||T9G |- -| 2 || n || 10 || k || 18 || 1 || 26 || 4 +|11||pN||Qr||7ZK||T9Q |- -| 3 || d || 11 || m || 19 || u || 27 || 5 +|12||pQ||Qt||7ZU||T9Z |- -| 4 || r || 12 || c || 20 || w || 28 || h +|13||pS||Qv||7Zc||T9i |- -| 5 || f || 13 || p || 21 || i || 29 || 7 +|14||pT||Qw||7Zm||T9r |- -| 6 || g || 14 || q || 22 || s || 30 || 6 +|15||pV||Qy||7Zv||TA1 +|- +|16||pX||R1||7a4||TA9 |- -| 7 || 8 || 15 || x || 23 || z || 31 || 9 |} -It is case-insensitive and includes all alphanumeric characters excluding 0, 2, l, v. The order of alphabet is chosen so that less ambiguous alphabet characters will appear more frequently than others. - -An address is a 270-bit string in z-base-32 with the following components: - - 5 address version bits - 5 length bits - 4 witness program version bits - 256 witness program bits - -The address version bits is 00001<sub>b</sub> for the main-network and 11001<sub>b</sub> for the testnet. - -Value of the length bits is the length of the witness program in byte minus 1. - -Witness program version bits indicates version of the witness program (v0 to v15). - -The witness program is padded with leading 0<sub>b</sub> to 256 bits. - -The 270-bit string is transformed to z-base-32 with 54 digits. - -The 54-digit raw address is then divided into 9 equal segments. For each segment, a checksum is calculated with Damm algorithm and appended to the end of the segment. This makes the length increases to 63 digits. - -A second round of checksum is calculated by taking the digits in the same position of the 9 segments, and appended to the end of the address. This is the final address with 69 digits. - == Rationale == -The segregated witness soft fork (BIP x) defines 2 ways of encoding "witness program", a data push of 2 to 32 bytes: +The BIP141 defines 2 ways of encoding "witness program", a data push of 2 to 32 bytes: * A native witness program output is a scriptPubKey with a push of version byte followed by a push of witness program, and nothing else; -* A witness program in P2SH is a P2SH redeemScript with a push of version byte followed by a push of witness program, while the scriptPubKey looks like a normal P2SH output. +* Segwit-in-P2SH is a BIP16 P2SH redeemScript with a push of version byte followed by a push of witness program, while the scriptPubKey looks like a normal P2SH output. -As the P2SH address has been defined in 2012, using witness program in P2SH allows most existing wallets to pay a segwit-compatible wallet without any upgrade. However, this method requires more block space and is less collision-resistance than a native witness program, and is only a short-term solution to make the transition smoother. Eventually, all users are expected to use the more efficient native witness program as the primary payment method. +As the BIP13 P2SH address has been defined in 2012, using segwit-in-P2SH allows most existing wallets to pay a segwit-compatible wallet without any upgrade. However, this method requires more block space and is only a short-term solution to make the transition smoother. Eventually, all users are expected to use the more efficient native witness program as the primary payment method. The drawbacks of Bitcoin addresses have been extensively discussed in BIP13. Since then, better payment methods have been proposed or deployed, for example: *BIP47 Reusable Payment Codes for Hierarchical Deterministic Wallets *BIP63 Stealth Addresses *BIP70 Payment protocol -However, none of these are as widely adopted as the suboptimal base-58 scriptPubKey template addresses, which is still a standard for the whole eco-system, from wallets, block explorers, merchants, exchanges, to end users. As P2PKH transactions are still dominating the blockchain, the author believes that the proposed P2PKH segwit addresses is the easiest way for wallets and services to adopt native witness program, which is particularly important in the context of scaling the capacity of the blockchain. +However, none of these are as widely adopted as the suboptimal base-58 scriptPubKey template addresses, which is still a standard for the whole eco-system, from wallets, block explorers, merchants, exchanges, to end users. It is believed that the proposed P2WPKH and P2WSH address format is the easiest way for wallets and services to adopt native witness program, which is particularly important in the context of scaling the capacity of the blockchain. -The P2PKH segwit addresses only allow simple payment to a single public key. For arbitrarily complex segwit transactions, the general segwit address is used. The use of z-base-32 eliminates case-sensitiveness and simplifies transformation to and from hexadecimals. The Damm algorithm checksum allows detection of all single-digit errors and all adjacent transposition errors. With the excellent upgradability of witness program, this proposal is also forward compatible to new version witness programs that is not longer than 32 bytes. +While P2WPKH address is specific for simple payment to a single public key, P2WSH address allows arbitrarily complex segwit transactions, resemble to the BIP13 P2SH address. == Compatibility == -This proposal is not backward compatible, but it fails gracefully -- if an older implementation is given one of these new Bitcoin addresses, it will report the address as invalid and will refuse to create a transaction. +This proposal is not backward compatible. However, an older implementation will report the new address type as invalid and will refuse to create a transaction. -This proposal is forward compatible to any new witness program format with version 2 to 15 and length of 2 to 32 bytes. +This proposal is forward compatible to the future versions of witness program of 20 and 32 bytes. == Example == -=== P2PKH segwit address === - The following public key, + 0450863AD64A87AE8A2FE83C1AF1A8403CB53F53E486D8511DAD8A04887E5B23522CD470243453A299FA9E77237716103ABC11A1DF38855ED6F2EE187E9C582BA6 + when encoded as a P2PKH template, would become: + DUP HASH160 <010966776006953D5567439E5E39F86A0D273BEE> EQUALVERIFY CHECKSIG + And the corresponding version 1 Bitcoin address is + 16UwLL9Risc3QfPqBUvKofHmBQ7wMtjvM -When the same script is encoded as a version 0 witness program, the scriptPubKey becomes: - OP_0 <0x76A914010966776006953D5567439E5E39F86A0D273BEE88AC> -Using 0x19 as the address version, the equivalent witness program address is: - B4YZZ3nMBETWVF9ZSfotSwTxVnqhdkTi7r - -=== General segwit address === - -With the same 25 bytes version 0 witness program in the last example: - OP_0 <0x76A914010966776006953D5567439E5E39F86A0D273BEE88AC> -The address version bits is 00001<sub>b</sub> - 00001<sub>b</sub> -The lengths bits is 11000<sub>b</sub> (24 = 25 - 1) - 00001-11000<sub>b</sub> -The witness program version bits is 0000 - 00001-11000-0000<sub>b</sub> -Appended by the zero-padded witness program - 00001-11000-0000-0-00000-00000-00000-00000-00000-00000-00000-00000-00000-00000-00000-00000-11101...01100 -The 270-bit string is transformed to z-base-32 with 54 digits and split into 9 equal segments: - bayyyy -yyyyyy -yyq4wt -eyejc3 -5sybwi -8iksqo -h6mah9 -o4oprh -767nfc -Calculate the Damm checksum for each segment: - For example: Damm(bayyyy) = 7 - bayyyy7-yyyyyyy-yyq4wte-eyejc3q-5sybwic-8iksqoo-h6mah9w-o4oprhm-767nfc4 -Calculate the Damm checksum for digits in the same position of different segments: - For example: Damm(byye58ho7) = j - bayyyy7-yyyyyyy-yyq4wte-eyejc3q-5sybwic-8iksqoo-h6mah9w-o4oprhm-767nfc4-jwk86o - -== Implementation == - -From arbitrary witness program to general segwit address: https://gist.github.com/jl2012/760b0f952715b8b6c608 + +When the same public key is encoded as P2WPKH, the scriptPubKey becomes: + + OP_0 <010966776006953D5567439E5E39F86A0D273BEE> + +Using 0x06 as witness version, followed 0x00 as witness version, and a 0x00 padding, the equivalent P2WPKH address is: + + p2xtZoXeX5X8BP8JfFhQK2nD3emtjch7UeFm + +== Reference implementation == == References == * [[bip-0013.mediawiki|BIP 13: Address Format for pay-to-script-hash]] -* [[bip-0016.mediawiki|BIP 16: Pay to Script Hash (aka "/P2SH/")]] -* [[bip-xxxx.mediawiki|BIP x: Segregated Witness]] https://github.com/bitcoin/bips/pull/265 +* [[bip-0016.mediawiki|BIP 16: Pay to Script Hash]] +* [[bip-0070.mediawiki|BIP 70: Payment Protocal]] +* [[bip-0141.mediawiki|BIP 141: Segregated Witness]] == Copyright == This work is placed in the public domain. |