From: Tom Zander <tomz@freedommail•ch>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] A BIP proposal for conveniently referring to confirmed transactions
Date: Mon, 17 Jul 2017 15:40:29 +0200 [thread overview]
Message-ID: <1695234.eLYGsKu2sb@strawberry> (raw)
In-Reply-To: <CAHGSxGs8Dko1UeZbRLN0VEDfcV9t6fONv3_N48hV36wTzLwu1w@mail.gmail.com>
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’m 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
change that then a less readable but more compact format is useful because
we want to optimize for space, not for human comprehention.
Another usecase I can come up with is you wanting to spend a specific output,
or you reporting a specific tx as proof to a merchant (or tax office).
For any such usecases you sill need to actually provide a proof of holding
the private keys and using a human-readable format just doesn’t seem to make
much sense because a cryptographic proof of ownership is not going to be
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?
--
Tom Zander
Blog: https://zander.github.io
Vlog: https://vimeo.com/channels/tomscryptochannel
next prev parent reply other threads:[~2017-07-17 13:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-14 18:43 Clark Moody
2017-07-15 5:00 ` Велеслав
2017-07-17 13:40 ` Tom Zander [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-05-23 15:30 Велеслав
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=1695234.eLYGsKu2sb@strawberry \
--to=tomz@freedommail$(echo .)ch \
--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