From: Christian Decker <decker.christian@gmail•com>
To: ZmnSCPxj <ZmnSCPxj@protonmail•com>
Cc: "bitcoin-dev@lists•linuxfoundation.org"
<bitcoin-dev@lists•linuxfoundation.org>,
"lightning-dev@lists•linuxfoundation.org"
<lightning-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] [Lightning-dev] eltoo: A Simplified update Mechanism for Lightning and Off-Chain Contracts
Date: Tue, 01 May 2018 13:38:12 +0200 [thread overview]
Message-ID: <87sh7bhahn.fsf@gmail.com> (raw)
In-Reply-To: <9OOOx7l1TdSQBlgt0MuRvtKzuxa_Z3g0kF315Legl5L-UOvvNZFL_tgAuWhe015Q-ZtOdYfI9iGJkAqhfb42RqazYq0JvTCzXaEr1XkD_iY=@protonmail.com>
ZmnSCPxj <ZmnSCPxj@protonmail•com> writes:
> Good morning Christian,
>
> This is very interesting indeed!
>
> I have started skimming through the paper.
>
> I am uncertain if the below text is correct?
>
>> Throughout this paper we will use the terms *input script* to refer to `witnessProgram` and `scriptPubKey`, and *output script* to refer to the `witness` or `scriptSig`.
>
> Figure 2 contains to what looks to me like a `witnessProgram`, `scriptPubKey`, or `redeemScript` but refers to it as an "output script":
>
>> OP_IF
>> 10 OP_CSV
>> 2 As Bs 2 OP_CHECKMULTISIGVERIFY
>> OP_ELSE
>> 2 Au Bu 2 OP_CHECKMULTISIGVERIFY
>> OP_ENDIF
>>
>> Figure 2: The output script used by the on-chain update transactions.
>
> Regards,
> ZmnSCPxj
Darn last minute changes! Yes, you are right, I seem to have flipped the
two definitions. I'll fix that up and push a new version.
next prev parent reply other threads:[~2018-05-01 12:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-30 15:41 [bitcoin-dev] " Christian Decker
2018-04-30 23:00 ` Jim Posen
2018-05-01 5:01 ` ZmnSCPxj
2018-05-01 11:36 ` Christian Decker
2018-05-01 15:50 ` Jim Posen
2018-05-01 16:29 ` Christian Decker
2018-05-01 17:07 ` Jim Posen
2018-05-01 17:31 ` Christian Decker
2018-05-02 1:15 ` Jim Posen
2018-05-07 23:26 ` Olaoluwa Osuntokun
2018-05-10 13:57 ` Christian Decker
2018-05-01 5:07 ` [bitcoin-dev] [Lightning-dev] " ZmnSCPxj
2018-05-01 11:38 ` Christian Decker [this message]
[not found] ` <20180619115618.ppycfvdh76rdagfo@email>
[not found] ` <87tvpy96lz.fsf@gmail.com>
[not found] ` <20180619180251.j4l3zvxfmwi5mwlb@email>
[not found] ` <20180620153150.4mdash2sj7r2aiwo@email>
2018-06-22 0:32 ` Rusty Russell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sh7bhahn.fsf@gmail.com \
--to=decker.christian@gmail$(echo .)com \
--cc=ZmnSCPxj@protonmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=lightning-dev@lists$(echo .)linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox