From aj at erisian.com.au  Tue Nov 24 05:45:43 2015
From: aj at erisian.com.au (Anthony Towns)
Date: Tue, 24 Nov 2015 15:45:43 +1000
Subject: [Lightning-dev] Better privacy with SNARKs
In-Reply-To: <87y4dojcqc.fsf@rustcorp.com.au>
References: <20151120074415.GA24674@navy> <87y4dojcqc.fsf@rustcorp.com.au>
Message-ID: <9123B138-FC5E-489D-8159-3945176B84CE@erisian.com.au>

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.