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-ref
ginal Message --------
Subject: Re: [bitcoin-dev] A BIP proposal for conveniently referring to
confirmed transactions
Local Time: July 15, 2017 1:43 AM
UTC Time: July 14, 2017 6:43 PM
From: bitcoin-dev@lists.linuxfoundation.org
To: bitcoin-dev@lists.linuxfoundation.org
(copying from GitHub per
(copying from GitHub per jonasschnelli's request)
I can understand the desire to keep all reference strings to the nice
14-character version by keeping the data payload to 40 bits, but it
seems to place artificial limitations on the format (year 2048 & 8191
transactions). I also understand that th
Hello List,
I would like to propose a BIP that specifies a way of referring to transactions
that have been successfully inserted into the blockchain.
The format makes use of the excellent Bech32 encoding, and is designed to be
short and useful for human use. A C reference implementation is incl
