Indeed, the PR in question does *not* change the semantics of
OP_CODESEPARATOR within SegWit redeemScripts, where it is still allowed
(and Nicolas Dorier pointed out that he was using it in TumbleBit), so
there are still ways to use it, but only in places, like SegWit, where
the potential
It is relevant to note that BIP 117 makes an insecure form of CODESEPARATOR
delegation possible, which could be made secure if some sort of
CHECKSIGFROMSTACK opcode is added at a later point in time. It is not IMHO a
very elegant way to achieve delegation, however, so I hope that one way or
Hi Jeff
There where previous discussions about similar approaches [1] [2].
I’m not sure if compression should be built into the protocol.
My humble understanding of it, is, that it should be built into different
layers.
If bandwidth is a concern, then on the fly gzip compression like apaches
Hi Jeff!
On Mon, Nov 27, 2017 at 3:11 AM, Jeff Johnson via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:
> Raw block
> 998,198 bytes
>
> Gzip
> 521,212 bytes (52% ratio)
> (needs 2MB to decompress).
>
I don't know how you got that raw block, but it seems a bit odd.
If you look
