š
Original date posted:2021-08-16
š Original message:Entering a BTC address for a transaction can pose a risk of error (human or technical). While
there is a checksum integrated in BTC addresses already, this is used only at a technical
level and does not avoid entering a valid but otherwise wrong address. Moreover, it does not
improve the overall user experience.
In case this hasn't been discussed before, I propose to implement a 3 or 4 digit code (lets
call it 4DC for this text), generated as checksum from the address. This 4DC should be shown
in all wallets next to the receiving address. When entering a new address to send BTC, the
sending wallet should also show the 4DC next to the entered address. This way, the sending
person can easily verify that the resulting 4DC matches the one from the receiving address.
This would mean that a receiver would not only send his public address to the sender, but also
the 4DC. A minor disadvantage since a) it is not mandatory and b) it is very easy to do.
However, it would greatly reduce the probability of performing transactions to a wrong address.
Technically, this is very easy to implement. The only effort needed is agreeing on a checksum
standard to generate the code. Once the standard is established, all wallet and exchange
developers can start implementing this.
Agreeing on a good name for this code would be helpful for a fast adoption (human readable
checksum, verification code or 4DC are just examples).
Obviously, this solution could be used for all other coins/networks. But ideally, each of them
should have its own checksum algorithm, in order to further avoid sending funds to the wrong
network. Especially when the address standard is the same like it is the case with BTC and BCH.
Hopefully, Bitcoin can implement this first and serve as example-to-follow to other
coins/networks.
Cheers,
TS
ts [ARCHIVE] /
npub16gā¦8hzyg
2023-06-07 22:58:06
in reply to nevent1qā¦hcm2
Author Public Key
npub16g0u0er3urgenux4fa7gt2h8avvfa33r3657jcwne4naszvyq4qsv8hzygPublished at
2023-06-07 22:58:06Event JSON
{
"id": "c272453d24f8bd4207d0787db7180ed1f285789b52d6cf3302d07a9385fc4c93",
"pubkey": "d21fc7e471e0d199f0d54f7c85aae7eb189ec6238ea9e961d3cd67d809840541",
"created_at": 1686178686,
"kind": 1,
"tags": [
[
"e",
"a33b3f0d53c98f3fc059fbd1e00cf1f7838bc50bfea2f6b6c05733132d02affb",
"",
"reply"
],
[
"p",
"a23dbf6c6cc83e14cc3df4e56cc71845f611908084cfe620e83e40c06ccdd3d0"
]
],
"content": "š
Original date posted:2021-08-16\nš Original message:Entering a BTC address for a transaction can pose a risk of error (human or technical). While \nthere is a checksum integrated in BTC addresses already, this is used only at a technical \nlevel and does not avoid entering a valid but otherwise wrong address. Moreover, it does not \nimprove the overall user experience.\n\nIn case this hasn't been discussed before, I propose to implement a 3 or 4 digit code (lets \ncall it 4DC for this text), generated as checksum from the address. This 4DC should be shown \nin all wallets next to the receiving address. When entering a new address to send BTC, the \nsending wallet should also show the 4DC next to the entered address. This way, the sending \nperson can easily verify that the resulting 4DC matches the one from the receiving address.\n\nThis would mean that a receiver would not only send his public address to the sender, but also \nthe 4DC. A minor disadvantage since a) it is not mandatory and b) it is very easy to do. \nHowever, it would greatly reduce the probability of performing transactions to a wrong address.\n\nTechnically, this is very easy to implement. The only effort needed is agreeing on a checksum \nstandard to generate the code. Once the standard is established, all wallet and exchange \ndevelopers can start implementing this.\n\nAgreeing on a good name for this code would be helpful for a fast adoption (human readable \nchecksum, verification code or 4DC are just examples).\n\nObviously, this solution could be used for all other coins/networks. But ideally, each of them \nshould have its own checksum algorithm, in order to further avoid sending funds to the wrong \nnetwork. Especially when the address standard is the same like it is the case with BTC and BCH.\n\nHopefully, Bitcoin can implement this first and serve as example-to-follow to other \ncoins/networks.\n\nCheers,\nTS",
"sig": "6198250c161b75e884be6fe41591601296e7ff5db7356aa3c9da088940370689af848c74a973feb4feeffabb3268fecfe6ec56a20d7565fccdde6bb3f7931493"
}