diff options
| author | Luke Dashjr <luke@dashjr.org> | 2018-01-06 00:26:51 +0000 |
|---|---|---|
| committer | bitcoindev <bitcoindev@gnusha.org> | 2018-01-06 00:27:09 +0000 |
| commit | 135ecfc1a5f4869729bb53278ec20a69e69ea9ce (patch) | |
| tree | 648c1f06f0dd7902472b9bbe49262d416720ed3a /16 | |
| parent | 86071d86bb8473f358c105f688dcb5fdb9eff9c2 (diff) | |
| download | pi-bitcoindev-135ecfc1a5f4869729bb53278ec20a69e69ea9ce.tar.gz pi-bitcoindev-135ecfc1a5f4869729bb53278ec20a69e69ea9ce.zip | |
Re: [bitcoin-dev] Bech32 and P2SH²
Diffstat (limited to '16')
| -rw-r--r-- | 16/5bcdfb0e583408f7aefe9491303d3b197ce6ef | 76 |
1 files changed, 76 insertions, 0 deletions
diff --git a/16/5bcdfb0e583408f7aefe9491303d3b197ce6ef b/16/5bcdfb0e583408f7aefe9491303d3b197ce6ef new file mode 100644 index 000000000..ceadb3152 --- /dev/null +++ b/16/5bcdfb0e583408f7aefe9491303d3b197ce6ef @@ -0,0 +1,76 @@ +Return-Path: <luke@dashjr.org> +Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org + [172.17.192.35]) + by mail.linuxfoundation.org (Postfix) with ESMTPS id 13017CAA + for <bitcoin-dev@lists.linuxfoundation.org>; + Sat, 6 Jan 2018 00:27:09 +0000 (UTC) +X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 +Received: from zinan.dashjr.org (zinan.dashjr.org [192.3.11.21]) + by smtp1.linuxfoundation.org (Postfix) with ESMTP id A1EBFD3 + for <bitcoin-dev@lists.linuxfoundation.org>; + Sat, 6 Jan 2018 00:27:08 +0000 (UTC) +Received: from ishibashi.localnet (unknown [IPv6:2001:470:5:265::71]) + (Authenticated sender: luke-jr) + by zinan.dashjr.org (Postfix) with ESMTPSA id DCC4B38A0C61 + for <bitcoin-dev@lists.linuxfoundation.org>; + Sat, 6 Jan 2018 00:26:52 +0000 (UTC) +X-Hashcash: 1:25:180106:bitcoin-dev@lists.linuxfoundation.org::bLImq8rwD46lg8Bb:a23Rw +From: Luke Dashjr <luke@dashjr.org> +To: bitcoin-dev@lists.linuxfoundation.org +Date: Sat, 6 Jan 2018 00:26:51 +0000 +User-Agent: KMail/1.13.7 (Linux/4.12.12-gentoo; KDE/4.14.37; x86_64; ; ) +References: <201801041423.05959.luke@dashjr.org> +In-Reply-To: <201801041423.05959.luke@dashjr.org> +X-PGP-Key-Fingerprint: E463 A93F 5F31 17EE DE6C 7316 BD02 9424 21F4 889F +X-PGP-Key-ID: BD02942421F4889F +X-PGP-Keyserver: hkp://pgp.mit.edu +MIME-Version: 1.0 +Content-Type: Text/Plain; + charset="iso-8859-1" +Content-Transfer-Encoding: quoted-printable +Message-Id: <201801060026.51676.luke@dashjr.org> +X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW, + T_RP_MATCHES_RCVD autolearn=ham version=3.3.1 +X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on + smtp1.linux-foundation.org +Subject: Re: [bitcoin-dev] =?iso-8859-1?q?Bech32_and_P2SH=B2?= +X-BeenThere: bitcoin-dev@lists.linuxfoundation.org +X-Mailman-Version: 2.1.12 +Precedence: list +List-Id: Bitcoin Protocol Discussion <bitcoin-dev.lists.linuxfoundation.org> +List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>, + <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe> +List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/> +List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org> +List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help> +List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>, + <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe> +X-List-Received-Date: Sat, 06 Jan 2018 00:27:09 -0000 + +I've posted an initial draft of a possible Bech32 revision/replacement here: + +https://github.com/luke-jr/bips/blob/new_bech32_p2sh2/bip-bech32-p2sh2.medi= +awiki + +On Thursday 04 January 2018 2:23:05 PM Luke Dashjr via bitcoin-dev wrote: +> I know I'm super-late to bring this up, but was there a reason Bech32 +> omitted the previously-discussed P2SH=B2 improvements? Since deployment +> isn't too widespread yet, maybe it'd be worth a quick revision to add +> this? +>=20 +> For those unfamiliar with the concept, the idea is to have the address +> include the *single* SHA256 hash of the public key or script, rather than +> RIPEMD160(SHA256(pubkey)) or SHA256(SHA256(script)). The sender would then +> perform the second hash to produce the output. Doing this would in the +> future enable relaying the "middle-hash" as a way to prove the final hash +> is in fact a hash itself, thereby proving it is not embedded data spam. +>=20 +> Bech32 seems like a huge missed opportunity to add this, since everyone +> will probably be upgrading to it at some point. +>=20 +> Luke +> _______________________________________________ +> bitcoin-dev mailing list +> bitcoin-dev@lists.linuxfoundation.org +> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev + |