From: Ricardo Filipe <ricardojdfilipe@gmail•com>
To: shiva sitamraju <shiva@blockonomics•co>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Visually Differentiable - Bitcoin Addresses
Date: Mon, 30 Oct 2017 12:14:42 +0000 [thread overview]
Message-ID: <CALC81CMgpzdeiD=T3yQazn5eAT7Nym4-t1bwGh1TD7rfuDT7EA@mail.gmail.com> (raw)
In-Reply-To: <CABuOfujV1gAaSOKBB7S0_JKuwp+3iNhY5kN59F3LLndPENUA_Q@mail.gmail.com>
start double checking the last few bytes instead?
2017-10-30 8:56 GMT+00:00 shiva sitamraju via bitcoin-dev
<bitcoin-dev@lists•linuxfoundation.org>:
> Hi,
>
> When I copy and paste bitcoin address, I double check the first few bytes,
> to make sure I copied the correct one. This is to make sure some rogue
> software is not changing the address, or I incorrectly pasted the wrong
> address.
>
>
> With Bech32 address, its seems like in this department we are taking as step
> in the backward direction. With the traditional address, I could compare
> first few bytes like 1Ko or 1L3. With bech32, bc1. is all I can see and
> compare which is likely to be same anyway. Note that most users will only
> compare the first few bytes only (since addresses themselves are very long
> and will overflow in a mobile text box).
>
> Is there anyway to make the Bech32 addresses format more visually distinct
> (atleast the first few bytes) ?
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists•linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
next prev parent reply other threads:[~2017-10-30 12:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-30 8:56 shiva sitamraju
2017-10-30 12:14 ` Ricardo Filipe [this message]
2017-10-30 14:23 ` Ben Thompson
2017-10-30 12:49 ` Ben Thompson
2017-10-30 13:13 ` shiva sitamraju
2017-10-30 14:26 ` Pieter Wuille
2017-10-30 14:39 ` Moral Agent
2017-10-30 16:15 ` Danny Thorpe
2017-10-30 16:48 ` Moral Agent
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='CALC81CMgpzdeiD=T3yQazn5eAT7Nym4-t1bwGh1TD7rfuDT7EA@mail.gmail.com' \
--to=ricardojdfilipe@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=shiva@blockonomics$(echo .)co \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox