summaryrefslogtreecommitdiff
path: root/1a/6fdc6d8c8feb2bb4124414e31efe4408e7c071
blob: 27fee59d3bb2beded180a09ac03108982fb11724 (plain)
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
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
Return-Path: <jtimon@jtimon.cc>
Received: from smtp1.osuosl.org (smtp1.osuosl.org [IPv6:2605:bc80:3010::138])
 by lists.linuxfoundation.org (Postfix) with ESMTP id D8A4FC002D
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Sat,  4 Jun 2022 18:42:11 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by smtp1.osuosl.org (Postfix) with ESMTP id D05C284404
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Sat,  4 Jun 2022 18:42:11 +0000 (UTC)
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level: 
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5
 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
 HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001,
 SPF_NONE=0.001] autolearn=ham autolearn_force=no
Authentication-Results: smtp1.osuosl.org (amavisd-new);
 dkim=pass (2048-bit key) header.d=jtimon-cc.20210112.gappssmtp.com
Received: from smtp1.osuosl.org ([127.0.0.1])
 by localhost (smtp1.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id fZlyEPb1uNTD
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Sat,  4 Jun 2022 18:42:10 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.8.0
Received: from mail-yb1-xb33.google.com (mail-yb1-xb33.google.com
 [IPv6:2607:f8b0:4864:20::b33])
 by smtp1.osuosl.org (Postfix) with ESMTPS id 8F6ED843ED
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Sat,  4 Jun 2022 18:42:10 +0000 (UTC)
Received: by mail-yb1-xb33.google.com with SMTP id u3so9354186ybi.4
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Sat, 04 Jun 2022 11:42:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=jtimon-cc.20210112.gappssmtp.com; s=20210112;
 h=mime-version:references:in-reply-to:from:date:message-id:subject:to;
 bh=ITvkZdTdWn1S9RB7b/8PnY8OTQpcNKk0wuLRUIGYfpc=;
 b=aeeJ1afPO76MDt212TquZdRY9LOy4NL75TLb0BqU0VplxNDKN9QzyhJMToVFdGK0Ic
 YqYRLQSWnWSLtWJ1oqxlEx8lHXNSkmwM+OfaQerps5kemcDIIZO/x0EGPCYJieeF4S0o
 P6ytWuRiiMoXIGoxH+4/to83k9EwxBnI0rHa1EbGbtSe5FA3w+7ClyoLwaTnqpbMLfA3
 JshJASAEZkO4l0omof9BSBjWDf5ssBU/Jo6knt5vlg1JywIw1aS6qJJodQGYcC9itvqw
 UUUVgjf5XXQvyMjustRSSrjmnVF9XwQ6gPUbzasX4kXRYA8kXs5rQEDjOauhxoN+G/Y4
 bmNw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20210112;
 h=x-gm-message-state:mime-version:references:in-reply-to:from:date
 :message-id:subject:to;
 bh=ITvkZdTdWn1S9RB7b/8PnY8OTQpcNKk0wuLRUIGYfpc=;
 b=3ivwYBLSHxNaPWCysZlWmj7IAphFwPbsvkxCRMDv8JdbDQaLUgLfkoAMlWoaGGKZ9w
 4bLfGM8hPwCw56M44buYS/IvZi84froH5XVaBJ7PZyAvslmDqYBV1HF+DeeK3Hl+aRb9
 dcCDnH/4uq0g6Jz+rFqRP+7cgdNFAI9gPcaFV2uuH0P2/sdGfcXA0mmUGr07KQe7li3D
 UCTuOUotRm6jz8peMIrSsghQvqnoRHoy/zZxqAEacDOpPxUejv+VDjQ45Urgm9poejP6
 LCTwtqHQNgDTJUFAriMbnnCOsjnkDU1agWAHxWiE+B4lm10Pwwdr7QUEru86vCL4SK3L
 ezSw==
X-Gm-Message-State: AOAM532hprYOhggxbi27JSBKOGQZ2cRQjjm7c8o6MAfqBjkjjgpF+mYN
 BOjY6In/Xf874SMIS6fLCGtqn93oqI/qHcoaMwgOrQ==
X-Google-Smtp-Source: ABdhPJxYHYTpwd0UtCpGatMiRrH5gCq9DO6+zEQGNymhyoRXuRMI3xEFE6a/uUiv9rNVErvzmQrf8vXPvR7U7ZtpCsU=
X-Received: by 2002:a25:d311:0:b0:65c:b04d:5f8b with SMTP id
 e17-20020a25d311000000b0065cb04d5f8bmr16371229ybf.26.1654368129395; Sat, 04
 Jun 2022 11:42:09 -0700 (PDT)
MIME-Version: 1.0
References: <QOWIpROGDv5HHP2GsDiSOsTJ9TVZhFeSP3C03_e2Z3XtOKC_4N5GJtxbdlxuhErvhLZXo1Rn_7SWAQ9XRPwHFuYyArZryTVENefDZuGTAYA=@protonmail.com>
In-Reply-To: <QOWIpROGDv5HHP2GsDiSOsTJ9TVZhFeSP3C03_e2Z3XtOKC_4N5GJtxbdlxuhErvhLZXo1Rn_7SWAQ9XRPwHFuYyArZryTVENefDZuGTAYA=@protonmail.com>
From: =?UTF-8?B?Sm9yZ2UgVGltw7Nu?= <jtimon@jtimon.cc>
Date: Sat, 4 Jun 2022 19:43:35 +0100
Message-ID: <CABm2gDoyFUhcryx9wSx2NOWt126img+51UehtkW7Nfg2Sf97aQ@mail.gmail.com>
To: alicexbt <alicexbt@protonmail.com>, 
 Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary="000000000000ae425505e0a3981d"
X-Mailman-Approved-At: Sat, 04 Jun 2022 22:13:55 +0000
Subject: Re: [bitcoin-dev] Bitcoin covenants are inevitable
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.15
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: Sat, 04 Jun 2022 18:42:12 -0000

--000000000000ae425505e0a3981d
Content-Type: text/plain; charset="UTF-8"

"Some people say CTV is contentious, but they're spreading misinformation"?
Really? Seriously?
Come on, guys, we can do better than nina jankovich and the "fact checkers".

Please, rise the bar.

On Fri, Jun 3, 2022, 19:44 alicexbt via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:

> Note: This email is an opinion and not an attack on bitcoin
>
> Covenants on bitcoin will eventually be implemented with a soft fork. CTV
> is the easiest and best possible way OP_TX looks good as well. Apart from
> the technical merits, covenants will improve a few other things:
>
> - Developers can build interesting projects with real demand in market.
> - Students learn Sapio and not just solidity.
> - Better tooling could be available for application developers.
> - Maybe we see bitcoin developer hackathons in different countries.
> - Demand for block space might increase, it wont be just exchanges and
> coinjoin.
> - Funding of bitcoin developers and projects might improve. Wont need to
> convince a few people for grants.
>
> **Why covenants are not contentious?**
>
> Some people may write paragraphs about CTV being contentious, spread
> misinformation and do all types of drama, politics etc. on social media but
> there are zero technical NACKs for CTV. We have discussed other covenant
> proposals in detail on mailing list and IRC meetings with an open minded
> approach.
>
> All the developers that participated in the discussion are either okay
> with CTV or OP_TX or covenants in general.
>
> **How and when should covenants be implemented in Bitcoin?**
>
> I don't think we should wait for years anticipating a proposal that
> everyone will agree on or argue for years to pretend changes are hard in
> Bitcoin. We should improve the review process for soft fork BIPs and share
> honest opinions with agreement, disagreement on technical merits.
>
> I prefer BIP 8 or improved BIP 8 for soft fork but I won't mind anything
> else being used if that improves Bitcoin. Covenants implemented in Bitcoin
> before the next cycle would provide opportunity for developers to build
> interesting things during the bear market. Ossification supporters also
> believe there is some window that will close soon, maybe doing changes
> considering each case individually will be a better approach. CTV is not a
> rushed soft fork, less people followed the research and it was not
> mentioned on social media repeatedly by the respected developers like other
> soft forks.
>
> /dev/fd0
>
>
> Sent with Proton Mail secure email.
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>

--000000000000ae425505e0a3981d
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto"><div>&quot;Some people say CTV is contentious, but they&#=
39;re spreading misinformation&quot;? Really? Seriously?</div><div dir=3D"a=
uto">Come on, guys, we can do better than nina jankovich and the &quot;fact=
 checkers&quot;.</div><div dir=3D"auto"><br></div><div dir=3D"auto">Please,=
 rise the bar.</div><div dir=3D"auto"><br><div class=3D"gmail_quote" dir=3D=
"auto"><div dir=3D"ltr" class=3D"gmail_attr">On Fri, Jun 3, 2022, 19:44 ali=
cexbt via bitcoin-dev &lt;<a href=3D"mailto:bitcoin-dev@lists.linuxfoundati=
on.org">bitcoin-dev@lists.linuxfoundation.org</a>&gt; wrote:<br></div><bloc=
kquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #cc=
c solid;padding-left:1ex">Note: This email is an opinion and not an attack =
on bitcoin<br>
<br>
Covenants on bitcoin will eventually be implemented with a soft fork. CTV i=
s the easiest and best possible way OP_TX looks good as well. Apart from th=
e technical merits, covenants will improve a few other things:<br>
<br>
- Developers can build interesting projects with real demand in market.<br>
- Students learn Sapio and not just solidity.<br>
- Better tooling could be available for application developers.<br>
- Maybe we see bitcoin developer hackathons in different countries.<br>
- Demand for block space might increase, it wont be just exchanges and coin=
join.<br>
- Funding of bitcoin developers and projects might improve. Wont need to co=
nvince a few people for grants.<br>
<br>
**Why covenants are not contentious?**<br>
<br>
Some people may write paragraphs about CTV being contentious, spread misinf=
ormation and do all types of drama, politics etc. on social media but there=
 are zero technical NACKs for CTV. We have discussed other covenant proposa=
ls in detail on mailing list and IRC meetings with an open minded approach.=
<br>
<br>
All the developers that participated in the discussion are either okay with=
 CTV or OP_TX or covenants in general.<br>
<br>
**How and when should covenants be implemented in Bitcoin?**<br>
<br>
I don&#39;t think we should wait for years anticipating a proposal that eve=
ryone will agree on or argue for years to pretend changes are hard in Bitco=
in. We should improve the review process for soft fork BIPs and share hones=
t opinions with agreement, disagreement on technical merits.<br>
<br>
I prefer BIP 8 or improved BIP 8 for soft fork but I won&#39;t mind anythin=
g else being used if that improves Bitcoin. Covenants implemented in Bitcoi=
n before the next cycle would provide opportunity for developers to build i=
nteresting things during the bear market. Ossification supporters also beli=
eve there is some window that will close soon, maybe doing changes consider=
ing each case individually will be a better approach. CTV is not a rushed s=
oft fork, less people followed the research and it was not mentioned on soc=
ial media repeatedly by the respected developers like other soft forks.<br>
<br>
/dev/fd0<br>
<br>
<br>
Sent with Proton Mail secure email.<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>

--000000000000ae425505e0a3981d--