📅 Original date posted:2021-01-15 📝 Original message:Dear Pieter, I read the ...

nakagat [ARCHIVE] /

npub1jx0…8pdk

2023-06-07 18:28:07

in reply to nevent1q…7wvn

📅 Original date posted:2021-01-15
📝 Original message:Dear Pieter,

I read the BIP draft of Bech32m and implemented it in Go.

Let me ask you one question.
Does Checksum have to be fixed?
The 'bech32_verify_checksum' function has hrp and data as parameters,
so how about committing Checksum with these two values?

For example, calculate Checksum from hrp and data using hash, chacha20, etc.

Thank you.
Takatoshi Nakagawa

2021年1月5日(火) 9:14 Pieter Wuille via bitcoin-dev
<bitcoin-dev at lists.linuxfoundation.org>:
>
> Hello all,
>
> here is a BIP draft for changing the checksum in native segwit addresses for v1 and higher, following the discussion in https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2020-December/018293.html
>
> Overall, the idea is:
> * Define a new encoding which is a tweaked variant of Bech32, called Bech32m. It refers to the Bech32 section of BIP173, which remains in effect.
> * Define a new segwit address encoding which replaces the corresponding section in BIP173. It prescribes using Bech32 for v0 witness addresses, and Bech32m for other versions.
>
> Comments, suggestions, ideas?
>
> Cheers,
>
> --
> Pieter
>
>
>
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev at lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev

Author Public Key

npub1jx0luel8punvucx7seamuunqh7x4tfm88pjutdv8qyw57v35dfrsj78pdk

Show more details

Published at

2023-06-07 18:28:07

Kind type

1 Short Text Note

Event JSON

{ "id": "8e444f4ab1b26bc51aa34680bffa032ad1eda07e2bb0ba129906d2683b18f571", "pubkey": "919ffe67e70f26ce60de867bbe7260bf8d55a7673865c5b587011d4f32346a47", "created_at": 1686162487, "kind": 1, "tags": [ [ "e", "7894b615fe731b617f07a8b91bd4476f4ccbbbf6d4889d965a791780695a3952", "", "root" ], [ "e", "1139465176e68c6b95aeb2bdc1cc02b5265b68da3ccb8f728474bf54ae04b808", "", "reply" ], [ "p", "13bd8c1c5e3b3508a07c92598647160b11ab0deef4c452098e223e443c1ca425" ] ], "content": "📅 Original date posted:2021-01-15\n📝 Original message:Dear Pieter,\n\nI read the BIP draft of Bech32m and implemented it in Go.\n\nLet me ask you one question.\nDoes Checksum have to be fixed?\nThe 'bech32_verify_checksum' function has hrp and data as parameters,\nso how about committing Checksum with these two values?\n\nFor example, calculate Checksum from hrp and data using hash, chacha20, etc.\n\nThank you.\nTakatoshi Nakagawa\n\n2021年1月5日(火) 9:14 Pieter Wuille via bitcoin-dev\n\u003cbitcoin-dev at lists.linuxfoundation.org\u003e:\n\u003e\n\u003e Hello all,\n\u003e\n\u003e here is a BIP draft for changing the checksum in native segwit addresses for v1 and higher, following the discussion in https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2020-December/018293.html\n\u003e\n\u003e Overall, the idea is:\n\u003e * Define a new encoding which is a tweaked variant of Bech32, called Bech32m. It refers to the Bech32 section of BIP173, which remains in effect.\n\u003e * Define a new segwit address encoding which replaces the corresponding section in BIP173. It prescribes using Bech32 for v0 witness addresses, and Bech32m for other versions.\n\u003e\n\u003e Comments, suggestions, ideas?\n\u003e\n\u003e Cheers,\n\u003e\n\u003e --\n\u003e Pieter\n\u003e\n\u003e\n\u003e\n\u003e\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": "5212ff762e3a3519c8d462d1428b409f02f7aacafd07599a93a921c96105af21963dc5a8325fa709f37d5c724eddb3e876a435a5ac9551cd08582aab27848437" }