public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: shiva sitamraju <shiva@blockonomics•co>
To: bitcoin-dev@lists•linuxfoundation.org
Subject: [bitcoin-dev] Visually Differentiable - Bitcoin Addresses
Date: Mon, 30 Oct 2017 14:26:40 +0530	[thread overview]
Message-ID: <CABuOfujV1gAaSOKBB7S0_JKuwp+3iNhY5kN59F3LLndPENUA_Q@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 754 bytes --]

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

[-- Attachment #2: Type: text/html, Size: 835 bytes --]

             reply	other threads:[~2017-10-30  8:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-30  8:56 shiva sitamraju [this message]
2017-10-30 12:14 ` Ricardo Filipe
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=CABuOfujV1gAaSOKBB7S0_JKuwp+3iNhY5kN59F3LLndPENUA_Q@mail.gmail.com \
    --to=shiva@blockonomics$(echo .)co \
    --cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
    /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