>From your draft:
"It could also more easily, ignoring the difficulties of a hard-fork
period, be rolled out as a hard fork to avoid hokey-pokey.[1]
[...]
[1] Because someone asked... The Txid Hokey Pokey: you put the tail
end in, you put the tail end out, you put the tail end in and you hash
it
On Thursday, July 23, 2015 8:12:19 PM Jeremy Rubin via bitcoin-dev wrote:
> Please see the following draft BIP which should decrease the amount of
> bytes needed per transaction. This is very much a draft BIP, as the design
> space for this type of improvement is large.
>
> This BIP can be rolled
Please see the following draft BIP which should decrease the amount of
bytes needed per transaction. This is very much a draft BIP, as the design
space for this type of improvement is large.
This BIP can be rolled out by a soft fork.
Improvements are around 12% for standard "one in two out" txn,
