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
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
|
Return-Path: <laolu32@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 389EB982
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 9 May 2018 00:25:12 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-wm0-f42.google.com (mail-wm0-f42.google.com [74.125.82.42])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 8842A14F
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 9 May 2018 00:25:11 +0000 (UTC)
Received: by mail-wm0-f42.google.com with SMTP id f6so21551234wmc.4
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 08 May 2018 17:25:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
h=mime-version:references:in-reply-to:from:date:message-id:subject:to;
bh=N8l7ML3NC+fI55Z26H3XgfOMD10dKGsShS0Xk8VaVJ8=;
b=tl4fdNPAM/CIe08k/Z+7689l31Xw7mQs0qv5/JbX2usDtCpmsUwm8WqrnVrzLz2/iT
H+VaqSZt4E0oNrg7u2bJzVTvzdit952FBafVRod1oJKyG60vZSW55bXl2tuK1K0XXSXg
6swrOC4iyDOMzXfs2ndY3+iGrdutg4QxaJCTtfRYv8+y5FeKIIGxaBEhKZ75KuGh1UJ3
VHeb3FzHol9cUAR3qtOZP72kozroawLZ1cTAJeilFmdk6FMrDzVn02ylFXNtAKVxzI7p
YFMYJupm253580hroIrLXR/EwHJ3IIo4Z0H+oUuO9skjg8+enc3LHiBcfmQTiAK6jrVg
dzJg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20161025;
h=x-gm-message-state:mime-version:references:in-reply-to:from:date
:message-id:subject:to;
bh=N8l7ML3NC+fI55Z26H3XgfOMD10dKGsShS0Xk8VaVJ8=;
b=foNbnVB0EHrLzMGIiUYlRNQhPkqe1m0vSIM/AAvsh7IEchKfwJBZDobYkU9LwGfqOW
ZQ5hqGa0bZO5/QybFbLqddQr8TbiO4N9s73+AjmEeqvnvqITAsjjtO182AulhkaLP/rd
wEZQ/GI909GW0dqeWU9Rnp9WiZK1554hdySsKUVU4Q7y+aHDjZEk0JiNLHvrQ+syvmoV
/ycSwBOx6OfIpmbbM/Je7G5KIvQoWV/dxkpL43moQrYvJMIpIr/1t29RggUCCh2V6GHq
F+dQuxhFlyHAWTyvYa932C1+pskuCriTZfSYG2Hp+8ng5HGunvHuCxtqXXoCLTMf9IxL
qdPw==
X-Gm-Message-State: ALQs6tBlvJj1pKDEQlMoeKttuMmF8xa+xDcXzRi/YKd8gGMjpPIUPH85
cfBX7PVTfLwZafVoigoKVHS+ehQ7XS9OMaE7XTEj/g==
X-Google-Smtp-Source: AB8JxZox87+W4PzWnQwr3ed9+w67Qmf6OZgDce2GEiAJnpKjMlxN/cDLIcDbw16aOCyi6Fcz4UpsvOnCXbztkeN0ilU=
X-Received: by 2002:a50:d311:: with SMTP id
g17-v6mr23165898edh.160.1525825510066;
Tue, 08 May 2018 17:25:10 -0700 (PDT)
MIME-Version: 1.0
References: <87po25lmzs.fsf@rustcorp.com.au>
In-Reply-To: <87po25lmzs.fsf@rustcorp.com.au>
From: Olaoluwa Osuntokun <laolu32@gmail.com>
Date: Wed, 09 May 2018 00:24:59 +0000
Message-ID: <CAO3Pvs9e5_YR9A_nqxcHAO5KgSvoyNq9q3P5UKBHbfK+kfvkKA@mail.gmail.com>
To: Rusty Russell <rusty@rustcorp.com.au>,
Arnoud Kouwenhoven - Pukaki Corp via bitcoin-dev
<bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary="000000000000844de7056bbaef20"
X-Spam-Status: No, score=-1.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID,DKIM_VALID_AU,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,
HTML_MESSAGE,RCVD_IN_DNSWL_NONE autolearn=no version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
Subject: Re: [bitcoin-dev] Making OP_TRUE standard?
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, 09 May 2018 00:25:12 -0000
--000000000000844de7056bbaef20
Content-Type: text/plain; charset="UTF-8"
What are the downsides of just using p2wsh? This route can be rolled out
immediately, while policy changes are pretty "fuzzy" and would require a
near uniform rollout in order to ensure wide propagation of the commitment
transactions.
On Tue, May 8, 2018, 4:58 PM Rusty Russell via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:
> Hi all,
>
> The largest problem we are having today with the lightning
> protocol is trying to predict future fees. Eltoo solves this elegantly,
> but meanwhile we would like to include a 546 satoshi OP_TRUE output in
> commitment transactions so that we use minimal fees and then use CPFP
> (which can't be done at the moment due to CSV delays on outputs).
>
> Unfortunately, we'd have to P2SH it at the moment as a raw 'OP_TRUE' is
> non-standard. Are there any reasons not to suggest such a policy
> change?
>
> Thanks!
> Rusty.
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
--000000000000844de7056bbaef20
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div dir=3D"auto"><div>What are the downsides of just using p2wsh? This rou=
te can be rolled out immediately, while policy changes are pretty "fuz=
zy" and would require a near uniform rollout in order to ensure wide p=
ropagation of the commitment transactions.=C2=A0<br><br><div class=3D"gmail=
_quote"><div dir=3D"ltr">On Tue, May 8, 2018, 4:58 PM Rusty Russell via bit=
coin-dev <<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org">bitco=
in-dev@lists.linuxfoundation.org</a>> wrote:<br></div><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex">Hi all,<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 The largest problem we are having today with th=
e lightning<br>
protocol is trying to predict future fees.=C2=A0 Eltoo solves this elegantl=
y,<br>
but meanwhile we would like to include a 546 satoshi OP_TRUE output in<br>
commitment transactions so that we use minimal fees and then use CPFP<br>
(which can't be done at the moment due to CSV delays on outputs).<br>
<br>
Unfortunately, we'd have to P2SH it at the moment as a raw 'OP_TRUE=
' is<br>
non-standard.=C2=A0 Are there any reasons not to suggest such a policy<br>
change?<br>
<br>
Thanks!<br>
Rusty.<br>
_______________________________________________<br>
bitcoin-dev mailing list<br>
<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=3D"_blank" =
rel=3D"noreferrer">bitcoin-dev@lists.linuxfoundation.org</a><br>
<a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" =
rel=3D"noreferrer noreferrer" target=3D"_blank">https://lists.linuxfoundati=
on.org/mailman/listinfo/bitcoin-dev</a><br>
</blockquote></div></div></div>
--000000000000844de7056bbaef20--
|
