Tier Nolan [ARCHIVE] on Nostr: 📅 Original date posted:2016-02-11 📝 Original message:On Thu, Feb 11, 2016 at ...
📅 Original date posted:2016-02-11
📝 Original message:On Thu, Feb 11, 2016 at 10:20 PM, Thomas Kerin <thomas.kerin at gmail.com>
wrote:
> I wonder if this is possible as a soft fork without using segwit?
Increasing the sigop count for a NOP would be a hard fork, but such a
change would be fine with a new segwit version. It might require specific
support in the altcoin, which might be troublesome..
It is a soft fork since it makes things that were previous allowed
disallowed. If it decreased the sigop count, then you could create a block
that had to many sigops due to the old rules.
With this rule, it increases the count. If the sigop count is valid under
the new rules, it is also valid under the old rules.
There is no need for specific support on the altcoin. It allows the
Bitcoin network act as trusted 3rd party so that you can do channels safely
on the altcoin, even though the altcoin still suffers from malleability and
doesn't have OP_CHECKLOCKTIMEVERIFY.
With regards to seg-witness, Ideally, the opcode would work in both old and
new scripts by re-purposing OP_NOP3.
<https://www.avast.com/sig-email>; This email has been sent from a
virus-free computer protected by Avast.
www.avast.com <https://www.avast.com/sig-email>;
<#DDB4FAA8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20160211/05dd04fa/attachment.html>;
📝 Original message:On Thu, Feb 11, 2016 at 10:20 PM, Thomas Kerin <thomas.kerin at gmail.com>
wrote:
> I wonder if this is possible as a soft fork without using segwit?
Increasing the sigop count for a NOP would be a hard fork, but such a
change would be fine with a new segwit version. It might require specific
support in the altcoin, which might be troublesome..
It is a soft fork since it makes things that were previous allowed
disallowed. If it decreased the sigop count, then you could create a block
that had to many sigops due to the old rules.
With this rule, it increases the count. If the sigop count is valid under
the new rules, it is also valid under the old rules.
There is no need for specific support on the altcoin. It allows the
Bitcoin network act as trusted 3rd party so that you can do channels safely
on the altcoin, even though the altcoin still suffers from malleability and
doesn't have OP_CHECKLOCKTIMEVERIFY.
With regards to seg-witness, Ideally, the opcode would work in both old and
new scripts by re-purposing OP_NOP3.
<https://www.avast.com/sig-email>; This email has been sent from a
virus-free computer protected by Avast.
www.avast.com <https://www.avast.com/sig-email>;
<#DDB4FAA8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20160211/05dd04fa/attachment.html>;