Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id A688C927 for ; Mon, 30 Oct 2017 08:57:03 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from blockonomics.co (blockonomics.co [52.10.115.182]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 682FD14B for ; Mon, 30 Oct 2017 08:57:03 +0000 (UTC) Received: from mail-ua0-f169.google.com (mail-ua0-f169.google.com [209.85.217.169]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by blockonomics.co (Postfix) with ESMTPSA id 8B4D11E55B8 for ; Mon, 30 Oct 2017 08:57:02 +0000 (UTC) Received: by mail-ua0-f169.google.com with SMTP id 47so8934218uas.8 for ; Mon, 30 Oct 2017 01:57:02 -0700 (PDT) X-Gm-Message-State: AMCzsaXcGPNouyvlee4e+Q0/qNBY8Y+mca9vl9+PPVXi/bO1DIgRpNsS AjGbDWOkEi7b2zqq4cJX49Z0rQX/OO8MHNcwjg== X-Google-Smtp-Source: ABhQp+SFxqc+NiTy8d9lLWeavxFEq7ZVSXEpMyMJTtxenjqHyUVmw55uFdr7+EH15ETju+7ESUwMa84+0HwLuzGxgws= X-Received: by 10.176.80.183 with SMTP id c52mr7352351uaa.162.1509353821293; Mon, 30 Oct 2017 01:57:01 -0700 (PDT) MIME-Version: 1.0 Received: by 10.176.7.212 with HTTP; Mon, 30 Oct 2017 01:56:40 -0700 (PDT) From: shiva sitamraju Date: Mon, 30 Oct 2017 14:26:40 +0530 X-Gmail-Original-Message-ID: Message-ID: To: bitcoin-dev@lists.linuxfoundation.org Content-Type: multipart/alternative; boundary="94eb2c18fd225bd301055cbfd28c" X-Spam-Status: No, score=0.0 required=5.0 tests=HTML_MESSAGE,RP_MATCHES_RCVD autolearn=disabled version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.linux-foundation.org X-Mailman-Approved-At: Mon, 30 Oct 2017 11:44:19 +0000 Subject: [bitcoin-dev] Visually Differentiable - Bitcoin Addresses X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Bitcoin Protocol Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Oct 2017 08:57:03 -0000 --94eb2c18fd225bd301055cbfd28c Content-Type: text/plain; charset="UTF-8" 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) ? --94eb2c18fd225bd301055cbfd28c Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Hi,

When I copy and paste bitc= oin 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 a= ddress, or I incorrectly pasted the wrong address.

With Be= ch32 address, its seems like in this department we are taking as step in th= e backward direction. With the traditional address, I could compare first f= ew bytes like 1Ko or 1L3. With bech32, bc1. is all I can see and compare wh= ich 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 ov= erflow in a mobile text box).

Is there anyway to make the Bech= 32 addresses format more visually distinct (atleast the first few bytes) ? =

--94eb2c18fd225bd301055cbfd28c--