Anthony Towns [ARCHIVE] on Nostr: 📅 Original date posted:2015-11-24 📝 Original message: On 24 November 2015 ...
📅 Original date posted:2015-11-24
📝 Original message:
On 24 November 2015 1:30:19 pm AEST, Rusty Russell <rusty at rustcorp.com.au> wrote:
>Anthony Towns <aj at erisian.com.au> writes:
>> On Fri, Nov 20, 2015 at 12:05:46PM +1030, Rusty Russell wrote:
>>> With the segregated witness proposal, introducing new opcodes is
>easy,
>>> so maybe someone would find a reason to prefer open-coding it like
>this?
>>
>> I don't follow how segregated witness makes new opcodes any easier?
>
>I didn't either, and that's because it's slightly orthogonal.
>
>The proposal I heard is that the first byte of SW script is a version
>byte, and if you don't understand that version, the script succeeds.
Ah, I see - it doesn't make OP_CHECK*VERIFY any easier then, but adding ops that actually change the contents of the stack becomes a soft fork instead of a hard fork. Pretty neat. Don't think that's needed here though.
Cheers,
aj
--
Sent from my phone.
📝 Original message:
On 24 November 2015 1:30:19 pm AEST, Rusty Russell <rusty at rustcorp.com.au> wrote:
>Anthony Towns <aj at erisian.com.au> writes:
>> On Fri, Nov 20, 2015 at 12:05:46PM +1030, Rusty Russell wrote:
>>> With the segregated witness proposal, introducing new opcodes is
>easy,
>>> so maybe someone would find a reason to prefer open-coding it like
>this?
>>
>> I don't follow how segregated witness makes new opcodes any easier?
>
>I didn't either, and that's because it's slightly orthogonal.
>
>The proposal I heard is that the first byte of SW script is a version
>byte, and if you don't understand that version, the script succeeds.
Ah, I see - it doesn't make OP_CHECK*VERIFY any easier then, but adding ops that actually change the contents of the stack becomes a soft fork instead of a hard fork. Pretty neat. Don't think that's needed here though.
Cheers,
aj
--
Sent from my phone.