public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed

From: ts <ts@cronosurf•com>
To: bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] Human readable checksum (verification code) to avoid errors on BTC public addresses
Date: Sat, 28 Aug 2021 16:17:35 -0500	[thread overview]
Message-ID: <6f69f132-211f-9d42-8023-c3b0264af439@cronosurf.com> (raw)
In-Reply-To: <f31bc6b0-f9b3-be4c-190c-fc292821b24b@cronosurf.com>

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?

Thanks,
TS



ts wrote on 8/15/21 11:23 PM:
> 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 (or communicate it via a different channel). 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

next prev parent reply	other threads:[~2021-08-28 21:17 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-16  4:23 ts
2021-08-16 10:34 ` ZmnSCPxj
2021-08-19 17:02   ` ts
2021-08-19 17:37     ` Christopher Allen
2021-08-21  4:52       ` ts
2021-08-19 21:05     ` Karl
2021-08-21  4:52       ` ts
2021-08-29 14:42     ` Pieter Wuille
2021-08-31  2:17       ` ts
2021-08-28 21:17 ` ts [this message]
2021-08-29 14:24   ` Pieter Wuille
2021-08-31  2:16     ` ts
2021-08-31  8:47       ` Marek Palatinus
2021-09-03  5:08         ` ts

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=6f69f132-211f-9d42-8023-c3b0264af439@cronosurf.com \
    --to=ts@cronosurf$(echo .)com \
    --cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox