Russell O'Connor [ARCHIVE] on Nostr: 📅 Original date posted:2019-03-12 📝 Original message:On Tue, Mar 12, 2019 at ...
📅 Original date posted:2019-03-12
📝 Original message:On Tue, Mar 12, 2019 at 6:39 PM Jacob Eliosoff <jacob.eliosoff at gmail.com>
wrote:
> Also, if future disabling isn't the point of making a tx type like
> OP_CODESEPARATOR non-standard - what is? If we're committed to indefinite
> support of these oddball features, what do we gain by making them hard to
> use/mine?
>
The purpose of making OP_CODESEPARATOR non-standard was to partly mitigate
the risk of the vulnerability that OP_CODESEPARATOR induces while we
consider how to patch it.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20190312/3a355816/attachment.html>
📝 Original message:On Tue, Mar 12, 2019 at 6:39 PM Jacob Eliosoff <jacob.eliosoff at gmail.com>
wrote:
> Also, if future disabling isn't the point of making a tx type like
> OP_CODESEPARATOR non-standard - what is? If we're committed to indefinite
> support of these oddball features, what do we gain by making them hard to
> use/mine?
>
The purpose of making OP_CODESEPARATOR non-standard was to partly mitigate
the risk of the vulnerability that OP_CODESEPARATOR induces while we
consider how to patch it.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20190312/3a355816/attachment.html>