📅 Original date posted:2021-08-29
📝 Original message:On Saturday, August 28th, 2021 at 5:17 PM, ts via bitcoin-dev <bitcoin-dev at lists.linuxfoundation.org> wrote:
> Following up on my original proposal, I would like to get some more feedback of the community
>
> to see if this could be realized at some point. Also, any recommendations as to who to contact
>
> to get things rolling?
I honestly don't understand the point of what you're suggesting.
* If you're concerned about random typos, this is something already automatically protected against through the checksum (both base58check or bech32/bech32m).
* If you're concerned about accidentally entering the wrong - but honestly created - address, comparing any few characters of the address is just as good as any other. It doesn't even require the presence of a checksum. Looking at the last N characters, or the middle N, or anything except the first few, will do, and is just as good as an "external" checksum added at the end. For randomly-generated addresses (as honest ones are), each of those has exactly as much entropy.
* If you're concerned about maliciously constructed addresses, which are designed to look similar in specific places, an attacker can just as easily make the external checksum collide (and having one might even worsen this, as now the attacker can focus on exactly that, rather than needing to focus on every other character).
Things would be different if you'd suggest a checksum in another medium than text (e.g. a visual/drawing/colorcoding one). But I don't see any added value for an additional text-based checksum when addresses are already text themselves. This is even disregarding the difficulty of getting the ecosystem to adopt such changes.
Cheers,
--
Pieter
Pieter Wuille [ARCHIVE] /
npub1tj…jtl6r
2023-06-07 22:58:11
in reply to nevent1q…zlul
Author Public Key
npub1tjephawh7fdf6358jufuh5eyxwauzrjqa7qn50pglee4tayc2ntqcjtl6rPublished at
2023-06-07 22:58:11Event JSON
{
"id": "3be53d3ba2b79d948a45b637bcc012e5dbef38db966dabb00b55abc09caabf77",
"pubkey": "5cb21bf5d7f25a9d46879713cbd32433bbc10e40ef813a3c28fe7355f49854d6",
"created_at": 1686178691,
"kind": 1,
"tags": [
[
"e",
"a33b3f0d53c98f3fc059fbd1e00cf1f7838bc50bfea2f6b6c05733132d02affb",
"",
"root"
],
[
"e",
"dc1c2e49617129971747aa39f8fcb63ea04bf1e15b1506894fec9694de17dd21",
"",
"reply"
],
[
"p",
"d21fc7e471e0d199f0d54f7c85aae7eb189ec6238ea9e961d3cd67d809840541"
]
],
"content": "📅 Original date posted:2021-08-29\n📝 Original message:On Saturday, August 28th, 2021 at 5:17 PM, ts via bitcoin-dev \u003cbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\n\u003e Following up on my original proposal, I would like to get some more feedback of the community\n\u003e\n\u003e to see if this could be realized at some point. Also, any recommendations as to who to contact\n\u003e\n\u003e to get things rolling?\n\nI honestly don't understand the point of what you're suggesting.\n\n* If you're concerned about random typos, this is something already automatically protected against through the checksum (both base58check or bech32/bech32m).\n\n* If you're concerned about accidentally entering the wrong - but honestly created - address, comparing any few characters of the address is just as good as any other. It doesn't even require the presence of a checksum. Looking at the last N characters, or the middle N, or anything except the first few, will do, and is just as good as an \"external\" checksum added at the end. For randomly-generated addresses (as honest ones are), each of those has exactly as much entropy.\n\n* If you're concerned about maliciously constructed addresses, which are designed to look similar in specific places, an attacker can just as easily make the external checksum collide (and having one might even worsen this, as now the attacker can focus on exactly that, rather than needing to focus on every other character).\n\nThings would be different if you'd suggest a checksum in another medium than text (e.g. a visual/drawing/colorcoding one). But I don't see any added value for an additional text-based checksum when addresses are already text themselves. This is even disregarding the difficulty of getting the ecosystem to adopt such changes.\n\nCheers,\n\n--\nPieter",
"sig": "20e28ae8415f20ed66ac6584c6f167dc7daf649a0a9fe7eae85656fea84407c24c04ec66a47ba42a25d89822a63967dc3fa8be82ebf33a0c0d21afefb5f2d748"
}