From: Tom Zander <tomz@freedommail.ch>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Date: Mon, 17 Jul 2017 15:40:29 +0200
Message-ID: <1695234.eLYGsKu2sb@strawberry>
In-Reply-To: <CAHGSxGs8Dko1UeZbRLN0VEDfcV9t6fONv3_N48hV36wTzLwu1w@mail.gmail.com>
References: <CAHGSxGs8Dko1UeZbRLN0VEDfcV9t6fONv3_N48hV36wTzLwu1w@mail.gmail.com>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="UTF-8"
Subject: Re: [bitcoin-dev] A BIP proposal for conveniently referring to
	confirmed transactions
Precedence: list

On Friday, 14 July 2017 20:43:37 CEST Clark Moody via bitcoin-dev wrote:
> I can understand the desire to keep all reference strings to the nice
> 14-character version by keeping the data payload to 40 bits

I=E2=80=99m not so clear on this, to be honest.

What is the point of having a user-readable tx-reference?

In the actual blockchain you will still be using txid, and if you want to=20
change that then a less readable but more compact format is useful because=
=20
we want to optimize for space, not for human comprehention.

Another usecase I can come up with is you wanting to spend a specific outpu=
t,=20
or you reporting a specific tx as proof to a merchant (or tax office).

=46or any such usecases you sill need to actually provide a proof of holdin=
g=20
the private keys and using a human-readable format just doesn=E2=80=99t see=
m to make=20
much sense because a cryptographic proof of ownership is not going to be=20
readable however hard you try.

Apologies for missing the point,
can you list one or two usecases that you can see this being used for?
=2D-=20
Tom Zander
Blog: https://zander.github.io
Vlog: https://vimeo.com/channels/tomscryptochannel