From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id C242894B for ; Mon, 30 Oct 2017 12:49:30 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.7.6 Received: from mail-wm0-f41.google.com (mail-wm0-f41.google.com [74.125.82.41]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 209F020D for ; Mon, 30 Oct 2017 12:49:30 +0000 (UTC) Received: by mail-wm0-f41.google.com with SMTP id y80so8807722wmd.0 for ; Mon, 30 Oct 2017 05:49:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=huNajAOryO8fV2w4fOZAtiwyf6vKD2+OYkmY1kvZYCc=; b=ObjTW0fMOIlCBuSDQ4HywXItVaiBeN+7qXZC0NoQmdpsZmtAjuF+50DTTLMldEJFyB LfIuESmNQAYFvLQjAQBcUopWEH4W9jfNWbAh0Iy/1PH9H8wGADxGR6tvL7nUoJXFRtPc xij6kdLrna9vZx7mwyFYiL3iAcTwbTezQWdQhNGc0JK+bzZnkreaTGXdDashe0peDV8r 7K3V9Abur2VhXJwjNMe4U+uUKQ3WvdVn0xTCtKDeR7NhjRRfBenNOQpWztvFNhIO54TL 5SHfEYMXMyz/83cSnlN90VpoWK1XzjaO7I9OLG6dqc57lJQ8LLG7xmWl7qR619EVtfvN ZVVg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=huNajAOryO8fV2w4fOZAtiwyf6vKD2+OYkmY1kvZYCc=; b=BX8oLMUZuZetZobEZbqW7UcXOZLiN67lGz2MQKwbkM+Fnsqqgeg4cdOLv2c3BN98Vk rxZoKyiC/MI/aaPNthn/BJe9TmKtgzq1CmWg+z0bV299XOmekXYqAoBVz7OzGB4hZxwF dfk5OSUgGefRb+PM0jnpxxVhKnYl9Ssc3UqKPL2s+dTCdzS7yLRGjuQc36CaN4x4wJZT 97DDotp3liSKdeDWtPp+X0xKZIkUtwg5lIEMGJIqWbKB1ktCgU4/cle/1y33WrK9Hs/V w/c2+/uPyh/YfSAfc9jkqFJxK7vmLpa+wZj5AstB9xjwGmngKfuzg2GKOZhwbTEIaXst zjZQ== X-Gm-Message-State: AMCzsaXDcpVtALDmGAB2piIk64jvhHPLLxNOfC1JLBnN1OEy9XRyXAle MELVhSIlPIwWVRFmLui0/oI9ur3yGk/KUSpVahs= X-Google-Smtp-Source: ABhQp+TtX9DiWuObJgfatC2KBRJYJztyhDIASjewgyeeV4Hl4p3I4yWwX7oXhDOG4QtoCnZ0MktPZD+pM++aO4XQV2M= X-Received: by 10.80.178.132 with SMTP id p4mr8967758edd.113.1509367768771; Mon, 30 Oct 2017 05:49:28 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Ben Thompson Date: Mon, 30 Oct 2017 12:49:18 +0000 Message-ID: To: shiva sitamraju , Bitcoin Protocol Discussion Content-Type: multipart/alternative; boundary="f403045c8204b176e1055cc31169" X-Spam-Status: No, score=-0.1 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE 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 14:18:27 +0000 Subject: Re: [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 12:49:30 -0000 --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
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.

On Mon, 30 Oct 2017,= 11:44 shiva sitamraju via bitcoin-dev, <bitcoin-dev@lists.linuxfoundati= on.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 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).

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/mail= man/listinfo/bitcoin-dev
--f403045c8204b176e1055cc31169--