From: Luke Dashjr <luke@dashjr.org>
To: bitcoin-dev@lists.linuxfoundation.org
Date: Thu, 4 Jan 2018 14:23:05 +0000
User-Agent: KMail/1.13.7 (Linux/4.12.12-gentoo; KDE/4.14.37; x86_64; ; )
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Message-Id: <201801041423.05959.luke@dashjr.org>
Subject: [bitcoin-dev] =?iso-8859-1?q?Bech32_and_P2SH=B2?=
Precedence: list

I know I'm super-late to bring this up, but was there a reason Bech32 omitt=
ed=20
the previously-discussed P2SH=B2 improvements? Since deployment isn't too=20
widespread yet, maybe it'd be worth a quick revision to add this?

=46or those unfamiliar with the concept, the idea is to have the address in=
clude=20
the *single* SHA256 hash of the public key or script, rather than=20
RIPEMD160(SHA256(pubkey)) or SHA256(SHA256(script)). The sender would then=
=20
perform the second hash to produce the output. Doing this would in the futu=
re=20
enable relaying the "middle-hash" as a way to prove the final hash is in fa=
ct=20
a hash itself, thereby proving it is not embedded data spam.

Bech32 seems like a huge missed opportunity to add this, since everyone wil=
l=20
probably be upgrading to it at some point.

Luke