MIME-Version: 1.0
References: <CABuOfujV1gAaSOKBB7S0_JKuwp+3iNhY5kN59F3LLndPENUA_Q@mail.gmail.com>
In-Reply-To: <CABuOfujV1gAaSOKBB7S0_JKuwp+3iNhY5kN59F3LLndPENUA_Q@mail.gmail.com>
From: Ben Thompson <thompson.benedictjames@gmail.com>
Date: Mon, 30 Oct 2017 12:49:18 +0000
Message-ID: <CAOxie=En8EqfuEtaPxH_v-2SYfUunudb4Zu0MQ-ZfEiPMxa6AQ@mail.gmail.com>
To: shiva sitamraju <shiva@blockonomics.co>, 
	Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary="f403045c8204b176e1055cc31169"
Subject: Re: [bitcoin-dev] Visually Differentiable - Bitcoin Addresses
Precedence: list

--f403045c8204b176e1055cc31169
Content-Type: text/plain; charset="UTF-8"

Checking the first few bytes of a Bitcoin Address should not be considered
sufficient for ensuring that it is correct as it takes less than a second
to generate a 3 character vanity address that matches the first 3
characters of an address.

On Mon, 30 Oct 2017, 11:44 shiva sitamraju via bitcoin-dev, <
bitcoin-dev@lists.linuxfoundation.org> wrote:

> 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
>

--f403045c8204b176e1055cc31169
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Checking the first few bytes of a Bitcoin Address should n=
ot be considered sufficient for ensuring that it is correct as it takes les=
s than a second to generate a 3 character vanity address that matches the f=
irst 3 characters of an address.</div><span>
</span><br><div class=3D"gmail_quote"><div dir=3D"ltr">On Mon, 30 Oct 2017,=
 11:44 shiva sitamraju via bitcoin-dev, &lt;<a href=3D"mailto:bitcoin-dev@l=
ists.linuxfoundation.org" target=3D"_blank">bitcoin-dev@lists.linuxfoundati=
on.org</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"m=
argin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"l=
tr"><div><div><div>Hi,<br><br></div>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.<br><br><br></div>With Bech32 address,=
 its seems like in this department we are taking as step in the backward di=
rection. 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 by=
tes only (since addresses themselves are very long and will overflow in a m=
obile text box).<br><br></div>Is there anyway to make the Bech32 addresses =
format more visually distinct (atleast the first few bytes) ? <br></div>
_______________________________________________<br>
bitcoin-dev mailing list<br>
<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=3D"_blank">=
bitcoin-dev@lists.linuxfoundation.org</a><br>
<a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" =
rel=3D"noreferrer" target=3D"_blank">https://lists.linuxfoundation.org/mail=
man/listinfo/bitcoin-dev</a><br>
</blockquote></div>

--f403045c8204b176e1055cc31169--