public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Pieter Wuille <pieter.wuille@gmail.com>
To: shiva sitamraju <shiva@blockonomics.co>,
	 Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Visually Differentiable - Bitcoin Addresses
Date: Mon, 30 Oct 2017 07:26:29 -0700	[thread overview]
Message-ID: <CAPg+sBiZGwQup0QRWVnBoHyR5Fx5tB6CtYgX7P=MM1-etm57Ww@mail.gmail.com> (raw)
In-Reply-To: <CABuOfui=G_iSaKdeVZ=M_udg-DoqAVxCrHOZaHuSJze4+N7CLw@mail.gmail.com>

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

On Oct 30, 2017 15:21, "shiva sitamraju via bitcoin-dev" <
bitcoin-dev@lists.linuxfoundation.org> wrote:

For example bc1qeklep85ntjz4605drds6aww9u0qr46qzrv5xswd35uhjuj8ahfcqgf6hak
in 461e8a4aa0a0e75c06602c505bd7aa06e7116ba5cd98fd6e046e8cbeb00379d6 is 62
bytes !


...

While I get the error/checksum capabilities Bech32 brings, any user would
prefer a 20 byte address with a checksum  over an address that would wrap
several lines !!


That's an unfair comparison. You're pasting a P2WSH address which contains
a 256-bit hash.

A P2WPKH address (which only contains a 160-bit hash, just like P2PKH and
P2SH) in Bech32 is only 42 characters, not 62.

Cheers,

-- 
Pieter

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

  reply	other threads:[~2017-10-30 14:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-30  8:56 [bitcoin-dev] Visually Differentiable - Bitcoin Addresses shiva sitamraju
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 [this message]
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='CAPg+sBiZGwQup0QRWVnBoHyR5Fx5tB6CtYgX7P=MM1-etm57Ww@mail.gmail.com' \
    --to=pieter.wuille@gmail.com \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=shiva@blockonomics.co \
    /path/to/YOUR_REPLY

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

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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