1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
|
Return-Path: <decker.christian@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 0E9EF8F5
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 19 Dec 2018 22:09:57 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-ed1-f41.google.com (mail-ed1-f41.google.com
[209.85.208.41])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 81D217C
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 19 Dec 2018 22:09:56 +0000 (UTC)
Received: by mail-ed1-f41.google.com with SMTP id h15so23044edb.4
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 19 Dec 2018 14:09:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
h=from:to:subject:in-reply-to:references:date:message-id:mime-version;
bh=93G6SmFnHeSaqZaHBIYOn9SCiW4Fi1OttV1gnZsl4D8=;
b=SahHrdcVix7wjks4ygCuVKKsRtEYLxASwAiX7fBO+EFiolU5ULh6l1Yi9GfXrUHMeu
jIMFYB3ZtWDxOgowe97Pg7T2GLnj0tjD9hfIszvVEQmyROmJC+pT9qg4kUzPjHxhm2w2
EvDNso532NIHP9gLJc0q/WyBTLzMDwKyqOXm9cldgMyNSt6wO5Mp1hx5jF8Mk/JIs6z7
rt2IsJzi2UflLdBHOnFXCxVJaaV16tyfvJlRVovBn2pyuQNd0Ze+QnRBC0kQO1zpYLse
wxoTGhyAc7J4WQ9tWXxC+HGuZSy2dm4lDSC1DKEELOnUbBZ9BvZsvAPdx4b8zzOyeUxC
fcEQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20161025;
h=x-gm-message-state:from:to:subject:in-reply-to:references:date
:message-id:mime-version;
bh=93G6SmFnHeSaqZaHBIYOn9SCiW4Fi1OttV1gnZsl4D8=;
b=YipaINDUQDwb0jk9XikCMj1QegrJenaxph94yJZIUfXmj7Tp4VWakYqoxzexUe73I5
ZLpMdH5BcrqZMtfQEoJXa/WppXcKTyd+jByyqyAQzvYE2sJiF4+TKtmE4AEnj2CN9PHj
wNET6YvMIZXz32QBSL9/GNN+J4V0CyU5Z8X/l2dRjSFZfCgIEO7QC2XdCWDcp0M7y2am
uAx6ktqwPVTj2QZzxJAFhM6Ya/lGqHX8nJS0zRuk4gACIkXxpODk7lLT3uvJAG9JIZR1
H1elqGxDI27hRHrO7SuaayadLVUADUArCuM5YqZNG+5/GOxenXThN+ZOjvCrn06rToHo
TOFA==
X-Gm-Message-State: AA+aEWbuw+gUk/ONrbaJwYORzHHc/pdHcb7BPB44lTs8b5e3O1joIPMr
q9Yc/xN59y7MYR45mnKD9LY=
X-Google-Smtp-Source: AFSGD/Udll2fFeq4hcxQcahe8+4Qy0mPZ9O6I+KXQL8ozXRfmvvGKePK3zZIWMr1HOsK8yw3jo1aBw==
X-Received: by 2002:a50:f098:: with SMTP id v24mr21306736edl.78.1545257395083;
Wed, 19 Dec 2018 14:09:55 -0800 (PST)
Received: from localhost ([2a02:aa16:1102:5480:b8c8:56f0:43e2:f1fe])
by smtp.gmail.com with ESMTPSA id
b46sm5722117edd.94.2018.12.19.14.09.53
(version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256);
Wed, 19 Dec 2018 14:09:53 -0800 (PST)
From: Christian Decker <decker.christian@gmail.com>
To: Ruben Somsen <rsomsen@gmail.com>,
Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>,
Johnson Lau <jl2012@xbt.hk>,
Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
In-Reply-To: <CAPv7TjYRVUGWCyFweootbMCJEkyFG4YOJ+M_N_N4j_t043bUfw@mail.gmail.com>
References: <9F8C0789-48E9-448A-A239-DB4AFB902A00@xbt.hk>
<CAPv7TjYRVUGWCyFweootbMCJEkyFG4YOJ+M_N_N4j_t043bUfw@mail.gmail.com>
Date: Wed, 19 Dec 2018 23:09:50 +0100
Message-ID: <87efadp3rl.fsf@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain
X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM,
RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
X-Mailman-Approved-At: Thu, 20 Dec 2018 21:58:07 +0000
Subject: Re: [bitcoin-dev] Safer NOINPUT with output tagging
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Protocol Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Dec 2018 22:09:57 -0000
Ruben Somsen via bitcoin-dev <bitcoin-dev@lists.linuxfoundation.org>
writes:
> Hi Johnson,
>
> The design considerations here seem similar to the ML discussion of
> whether Graftroot should be optional [1].
>
>>While this seems fully compatible with eltoo, is there any other proposals require NOINPUT, and is adversely affected by either way of tagging?
>
> As far as I can tell it should be compatible with Statechains [2],
> since it pretty much mirrors Eltoo in setup.
>
> My understanding is somewhat lacking, so perhaps I am missing the
> mark, but it is not completely clear to me how this affects
> fungibility if taproot gets added and the setup and trigger tx for
> Eltoo get combined into a single transaction. Would the NOINPUT
> spending condition be hidden inside the taproot commitment?
I'm not aware of a way to combine the setup and trigger transaction. The
trigger transaction was introduced in order to delay the start of the
timeouts until a later time, to avoid having an absolute lifetime limit
and having really huge timeout. If we were to combine the trigger
transaction with the setup transaction (which is broadcast during
channel creation), all of those timeouts would start counting down
immediately, and we could just skip the trigger transaction
altogether. It'd be more interesting to combine update and trigger
transactions in a sort of cut-through combination, but that doesn't seem
possible outside of Mimblewimble.
Cheers,
Christian
|
