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
|
Return-Path: <buck.perley@protonmail.com>
Received: from smtp2.osuosl.org (smtp2.osuosl.org [140.211.166.133])
by lists.linuxfoundation.org (Postfix) with ESMTP id C5EF7C002D
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 12 Sep 2022 00:05:34 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by smtp2.osuosl.org (Postfix) with ESMTP id 8D5C540370
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 12 Sep 2022 00:05:34 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp2.osuosl.org 8D5C540370
Authentication-Results: smtp2.osuosl.org;
dkim=pass (2048-bit key) header.d=protonmail.com header.i=@protonmail.com
header.a=rsa-sha256 header.s=protonmail3 header.b=n1hjple7
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: 0.598
X-Spam-Level:
X-Spam-Status: No, score=0.598 tagged_above=-999 required=5
tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001,
RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001]
autolearn=ham autolearn_force=no
Received: from smtp2.osuosl.org ([127.0.0.1])
by localhost (smtp2.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id 7UfJ1NBPh11b
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 12 Sep 2022 00:05:33 +0000 (UTC)
X-Greylist: domain auto-whitelisted by SQLgrey-1.8.0
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp2.osuosl.org 8324E401E1
Received: from mail-4316.protonmail.ch (mail-4316.protonmail.ch [185.70.43.16])
by smtp2.osuosl.org (Postfix) with ESMTPS id 8324E401E1
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 12 Sep 2022 00:05:33 +0000 (UTC)
Date: Mon, 12 Sep 2022 00:05:18 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com;
s=protonmail3; t=1662941130; x=1663200330;
bh=CeuukLO9MhYWkqwmdDpPp773fZnUHGiSyRjFRjSPsoI=;
h=Date:To:From:Reply-To:Subject:Message-ID:Feedback-ID:From:To:Cc:
Date:Subject:Reply-To:Feedback-ID:Message-ID;
b=n1hjple7FflCJMTbEh2IPj7ZBFn4/VYpyGzvLMPji1AorseqAP7bPDMcPOd+DNpyB
iKwG99iqfkXqT71T0HOiui9BIOc0PL2q2797sL7riW7XRpVAv6wnQO9gswLCSFd0KO
NRI8tn/SY5HStL7uB7mAEEymebvsa/f4M45y9fNN+sy/evlYvXnclQbVVkP+A2fEDa
KJT0GV4jejxRzzDegpUxL8ok6phb2McFqrITHZcvnrCHJKMyi1pllgB03J4H8HoFEK
IsGV0d1reh/Lnn7VWSNUl4OvTZ2Kx8fv6iNCcPFoO7z7vdaWVv6uRMRKZWHvoQ7rB1
2CVOlwqWox0kg==
To: "bitcoin-dev@lists.linuxfoundation.org"
<bitcoin-dev@lists.linuxfoundation.org>
From: Buck O Perley <buck.perley@protonmail.com>
Reply-To: Buck O Perley <buck.perley@protonmail.com>
Message-ID: <BQjnkZZajHKYBOUFAin8toHgNHhG346VUR4GQx6bSi2ftOuNTK1c1d4LWN4Zmr0tUg2w3xgtIZJSphBORYgWw4PPXq5pGFoZJk2Lx6AokuQ=@protonmail.com>
Feedback-ID: 17248654:user:proton
MIME-Version: 1.0
Content-Type: multipart/mixed;
boundary="b1_ziDoRxlml5NEv5UfIeu1D8kpmyCrvNfD17UAsQSNk"
X-Mailman-Approved-At: Mon, 12 Sep 2022 02:47:06 +0000
Subject: Re: [bitcoin-dev] On a new community process to specify covenants
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: Mon, 12 Sep 2022 00:05:34 -0000
This is a multi-part message in MIME format.
--b1_ziDoRxlml5NEv5UfIeu1D8kpmyCrvNfD17UAsQSNk
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Hi Antoine,
First just wanted to thank you for taking the initiative to=20
put this together. I think that as the community and=20
ecosystem continue to grow, it's going to be an important=20
part of the process to have groups like this develop. Hopefully
they allow us to resist the "Tyranny of Structurelessness" without=20
resorting to formalized governance processes and systems.=20
> Defining a communication channel is still an open question: IRC, Slack,
Discord, Discourse, ...
I would vote against Slack. IRC is probably the best but maybe too
high a barrier to entry? Publishing logs at least would counter
concerns of it being exclusive. Maybe discord as an alternative.=20
> About the starting point for regular meetings, I think the good timing is
somewhere in November, after the upcoming cycle of Bitcoin conferences,
+1=20
> softfork activation discussions will be considered as
off-topic and discouraged. This is first and foremost a long-term R&D
effort.
I understand the reason for this but I do have some concerns that
it's not as off-topic as most of us would like. It shouldn't
be a priority but how any of these primitives end up getting activated
is part of the proposal itself in my opinion.=20
I think it also became clear in some of the discussions over the past=20
~year that maybe there were more concerns than people realized about
even the taproot activation process, whether the method used or if it=20
was done too quickly. An example of where there might be=20
some intersection with the WG as proposed is the question of how much=20
research, security audits, etc. are "enough" before it should be=20
considered for activation?=20
Maybe as a way to keep these topics separate, it would make sense=20
for activation to have its own WG. As norms develop around this one,=20
they could inform creating a separate space focused on forwarding=20
research and discussion around how to introduce upgrades to bitcoin.=20
In general it would be nice to have multiple of these groups
happening at once, and finding a way that they can operate separate
from centralized companies. To my mind, there's no good reason why
a supposedly decentralized protocol should have to be focusing on only
one set of protocol advancements at a time. The linear way that
discussions post-Taproot activation took shape ("What do you think the
next bitcoin softfork should be?") is a sign of weakness in my opinion.=20
Definitely a big red flag that we should be concerned with.=20
Couple other comments from the proposal/repo:
* it seems like there might be some opportunities to work with=20
bipbounty.org which grew out of the organic bounty donations that
were made towards finding CTV vulnerabilities. For example,=20
if the group develops specific, achievable research goals (building
out use cases, researching vulnerabilities or limitations, etc.),=20
bipbounty.org could help support these efforts in a more decentralized
way by diversifying funding.=20
* Any thoughts on starting to commit to an in-person meetup to happen=20
~6 months - 1 year after the start of the regular online meetings?=20
That should be plenty of time for people to plan and formalize=20
a location and it seems like other IRL dev meetups have been=20
very productive in terms of knowledge sharing and setting priorities.=20
An in-person meetup would give a nice goal to work towards and a way
to measure progress.=20
--b1_ziDoRxlml5NEv5UfIeu1D8kpmyCrvNfD17UAsQSNk
Content-Type: application/pgp-keys; name="publickey - buck.perley@protonmail.com - 0xC64EEB00.asc"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="publickey - buck.perley@protonmail.com - 0xC64EEB00.asc"
LS0tLS1CRUdJTiBQR1AgUFVCTElDIEtFWSBCTE9DSy0tLS0tCgp4ak1FWGVaM3l4WUpLd1lCQkFI
YVJ3OEJBUWRBN0ZxeTZ3UVNxanJrS2FqTURxaHJ1djFTaG81RE9EeXUKZXZIdXEyTE02L0ROTjJK
MVkyc3VjR1Z5YkdWNVFIQnliM1J2Ym0xaGFXd3VZMjl0SUR4aWRXTnJMbkJsCmNteGxlVUJ3Y205
MGIyNXRZV2xzTG1OdmJUN0Nkd1FRRmdvQUh3VUNYZVozeXdZTENRY0lBd0lFRlFnSwpBZ01XQWdF
Q0dRRUNHd01DSGdFQUNna1FEUG9sb1RTeTlCZkIvZ0VBaE1aUDByQTJYK05nS3dnRlZuaW4KeURS
Z2sxaVd5TXZuWW1ZNmJPeTlJbE1CQUl2Q0tnUDZycFc1SlZneDRmM2l4U0Rya0xUaHBvaDhsMURF
Ck1pWmVWam9EempnRVhlWjN5eElLS3dZQkJBR1hWUUVGQVFFSFFKbFVHTVhWbGs1czlHaEhDVzlU
Z0x2WQo4cnZKTjdYbHhMV2kvVmlzUGoxUkF3RUlCOEpoQkJnV0NBQUpCUUpkNW5mTEFoc01BQW9K
RUF6NkphRTAKc3ZRWEFOUUEvUktvSmQ5VzVJWVQ4YTFlSy9SeEFPQWswZzRUZGxiRTVHczZ4aHhl
L29CaUFRRG9OWEFoCllOTm1ZdE1namtDTUE1VWp5U2dOV2hoeWs1Vlh6UG0yZVZXb0FRPT0KPWZU
SjQKLS0tLS1FTkQgUEdQIFBVQkxJQyBLRVkgQkxPQ0stLS0tLQo=
--b1_ziDoRxlml5NEv5UfIeu1D8kpmyCrvNfD17UAsQSNk--
|
