📅 Original date posted:2018-01-05
📝 Original message: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.mediawiki
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² 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
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev at lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
Luke Dashjr [ARCHIVE] /
npub1tf…rfq0n
2023-06-07 18:09:14
in reply to nevent1q…jfwz
Author Public Key
npub1tfk373zg9dnmtvxnpnq7s2dkdgj37rwfj3yrwld7830qltmv8qps8rfq0nSeen on
wss://relay.nostr.bandPublished at
2023-06-07 18:09:14Event JSON
{
"id": "c5aaacf0b8590d89b57a07e377dc75a91ba4fa41cbfe99bab63abd9ceb3871c4",
"pubkey": "5a6d1f44482b67b5b0d30cc1e829b66a251f0dc99448377dbe3c5e0faf6c3803",
"created_at": 1686161354,
"kind": 1,
"tags": [
[
"e",
"45c82b414730d6087d141656cdec1e9fa3d3c7df8a0406cc87e780bba7d95c10",
"",
"root"
],
[
"e",
"0e0422fd0d87814018198a6462f167d3022b07c22c1e80158635cb728cbb8fa9",
"",
"reply"
],
[
"p",
"5a6d1f44482b67b5b0d30cc1e829b66a251f0dc99448377dbe3c5e0faf6c3803"
]
],
"content": "📅 Original date posted:2018-01-05\n📝 Original message:I've posted an initial draft of a possible Bech32 revision/replacement here:\n\nhttps://github.com/luke-jr/bips/blob/new_bech32_p2sh2/bip-bech32-p2sh2.mediawiki\n\nOn Thursday 04 January 2018 2:23:05 PM Luke Dashjr via bitcoin-dev wrote:\n\u003e I know I'm super-late to bring this up, but was there a reason Bech32\n\u003e omitted the previously-discussed P2SH² improvements? Since deployment\n\u003e isn't too widespread yet, maybe it'd be worth a quick revision to add\n\u003e this?\n\u003e \n\u003e For those unfamiliar with the concept, the idea is to have the address\n\u003e include the *single* SHA256 hash of the public key or script, rather than\n\u003e RIPEMD160(SHA256(pubkey)) or SHA256(SHA256(script)). The sender would then\n\u003e perform the second hash to produce the output. Doing this would in the\n\u003e future enable relaying the \"middle-hash\" as a way to prove the final hash\n\u003e is in fact a hash itself, thereby proving it is not embedded data spam.\n\u003e \n\u003e Bech32 seems like a huge missed opportunity to add this, since everyone\n\u003e will probably be upgrading to it at some point.\n\u003e \n\u003e Luke\n\u003e _______________________________________________\n\u003e bitcoin-dev mailing list\n\u003e bitcoin-dev at lists.linuxfoundation.org\n\u003e https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev",
"sig": "377d2d206b312a579a0796a8b7cd8c6ecdc94434529f2ad67ab6710233cb7aa16e52b22b57f34b67824a6d9b7dd48f975b5290c2b3b430fbdd8009552f1771c6"
}