From: Luke Dashjr <luke@dashjr•org>
To: bitcoin-dev@lists•linuxfoundation.org
Subject: [bitcoin-dev] Bech32 and P2SH²
Date: Thu, 4 Jan 2018 14:23:05 +0000 [thread overview]
Message-ID: <201801041423.05959.luke@dashjr.org> (raw)
I know I'm super-late to bring this up, but was there a reason Bech32 omitted
the previously-discussed P2SH² improvements? Since deployment isn't too
widespread yet, maybe it'd be worth a quick revision to add this?
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.
Bech32 seems like a huge missed opportunity to add this, since everyone will
probably be upgrading to it at some point.
Luke
next reply other threads:[~2018-01-04 14:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-04 14:23 Luke Dashjr [this message]
2018-01-06 0:26 ` Luke Dashjr
2018-01-06 0:44 ` Gregory Maxwell
2018-01-06 10:05 ` Adam Ritter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201801041423.05959.luke@dashjr.org \
--to=luke@dashjr$(echo .)org \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox