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
141
142
143
144
145
146
147
148
149
150
151
152
|
Return-Path: <jtimon@jtimon.cc>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 6818D900
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 10 May 2018 09:33:42 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-io0-f182.google.com (mail-io0-f182.google.com
[209.85.223.182])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id DC5A6683
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 10 May 2018 09:33:41 +0000 (UTC)
Received: by mail-io0-f182.google.com with SMTP id f21-v6so2243386iob.13
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 10 May 2018 02:33:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=jtimon-cc.20150623.gappssmtp.com; s=20150623;
h=mime-version:references:from:date:message-id:subject:to;
bh=cFaD4NIezeKflDe29aRywxr0hz3enu2it5twtDSZV+8=;
b=1a22CPjjB5ObtzjUWA6a8l10ZSnee4mUutxp4o9Ny4gt9EALTqatMT0saaBTI/stTY
RBtKsTMtsoCCDLeDkaMAWm67C03iUdr+f12G+eSXQCDmdRD1HlXDgEDzKk/W8ThqWe55
rw4wkxOkIkScdeizy9qORVcKZdTWhpiFIqwbTQEfICNRjV75xr3qdMLLPQzBOoOHGDcm
XSNi0mblJ81lKOF46qyN2W0g9172+t67rzCRmZRdfMPM2kPicJX01fPfkbRVB0yKBN23
cPeH55S1z//UH3REwWGVedIIRCEkBwe/frtya2hIUmsqK2+3t1AvAXDlxTFGQyCbnzWl
aeZg==
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:from:date:message-id
:subject:to;
bh=cFaD4NIezeKflDe29aRywxr0hz3enu2it5twtDSZV+8=;
b=ZJm7AJb727MereC9m/B5t2gUWUwjkaNVDv/F1MSAurUXNc62/DGkD5V88rLiBO77cA
r7845o3ed6HByxlpGaYilETFbr1oLbqzckntwTGlnShKhOyndyuJN9bkN+j8e+MTN4Lz
FntNdgBCbMARqny6NePE0LjVwYs+sBu31+AMt1XVFJDqHk75phV+IWNGjmvZDLllfVss
u/uij6nC0KZ7kMGWoTxwBjpI241dsg1iU5hZ0DOhhMdRtyy4lI11StqcDYXhzB5RkBkE
J7QsM4BiPTf+d7fh/6nBeyAtfKUYB7lCkXUZZM/KsQnr5+AMQke6rG9MfyhlRxaRlErC
/GqA==
X-Gm-Message-State: ALKqPwfuVW5Y1rEV4Sq2OAovgp8P+iLPF/vFIk+k6spjtlOyH6x96Cio
aajOc00sniohhg8yYrMyeysZIRh5p0M83/zRpfNQVA==
X-Google-Smtp-Source: AB8JxZoAmNGeKkU8RvGsND1Vb0jr98yBASpM4G8A3a0Tyr2yySb2VeIiAGrSB9wPKdrm+YEbpfXY8tpCS+o7vbfkfKE=
X-Received: by 2002:a6b:88e3:: with SMTP id s96-v6mr643927ioi.45.1525944821249;
Thu, 10 May 2018 02:33:41 -0700 (PDT)
MIME-Version: 1.0
References: <87po25lmzs.fsf@rustcorp.com.au>
<CABm2gDoJEKQXPipWY5y6MUgQRu1W_ogBHL7ibjt8dD_=n2=ptg@mail.gmail.com>
From: =?UTF-8?B?Sm9yZ2UgVGltw7Nu?= <jtimon@jtimon.cc>
Date: Thu, 10 May 2018 09:33:30 +0000
Message-ID: <CABm2gDppMYYPs65XJOq8YLpaxX4-mADibqq+fvgSDDRUpdk5yQ@mail.gmail.com>
To: Rusty Russell <rusty@rustcorp.com.au>,
Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary="000000000000048a81056bd6b7d0"
X-Spam-Status: No, score=-0.9 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID, FROM_EXCESS_BASE64, 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: Thu, 10 May 2018 09:33:42 -0000
--000000000000048a81056bd6b7d0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
But in prnciple I don't oppose to making it stardard, just want to
understand what's the point.
On Thu, 10 May 2018, 02:16 Jorge Tim=C3=B3n, <jtimon@jtimon.cc> wrote:
> I fail to see what's the practical difference between sending to op_true
> and giving the coins are fees directly. Perhaps it is ao obvious to you
> that you forget to mention it?
> If you did I honestlt missed it.
>
> On Wed, 9 May 2018, 01:58 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
>>
>
--000000000000048a81056bd6b7d0
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div dir=3D"auto">But in prnciple I don't oppose to making it stardard,=
just want to understand what's the point.</div><br><div class=3D"gmail=
_quote"><div dir=3D"ltr">On Thu, 10 May 2018, 02:16 Jorge Tim=C3=B3n, <j=
timon@jtimon.cc> wrote:<br></div><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=
=3D"auto">I fail to see what's the practical difference between sending=
to op_true and giving the coins are fees directly. Perhaps it is ao obviou=
s to you that you forget to mention it?=C2=A0<div dir=3D"auto">If you did I=
honestlt missed it.</div></div><br><div class=3D"gmail_quote"><div dir=3D"=
ltr">On Wed, 9 May 2018, 01:58 Rusty Russell via bitcoin-dev, <<a href=
=3D"mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev@lists.linuxfo=
undation.org</a>> wrote:<br></div><blockquote class=3D"gmail_quote" styl=
e=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-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></blockquote></div>
--000000000000048a81056bd6b7d0--
|
