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
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
|
Return-Path: <damian@willtech.com.au>
Received: from smtp3.osuosl.org (smtp3.osuosl.org [IPv6:2605:bc80:3010::136])
by lists.linuxfoundation.org (Postfix) with ESMTP id BC860C000E
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 5 Nov 2021 11:01:11 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by smtp3.osuosl.org (Postfix) with ESMTP id 9A12260609
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 5 Nov 2021 11:01:11 +0000 (UTC)
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: -1.035
X-Spam-Level:
X-Spam-Status: No, score=-1.035 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1,
RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001,
SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665]
autolearn=no autolearn_force=no
Authentication-Results: smtp3.osuosl.org (amavisd-new); dkim=neutral
reason="invalid (public key: not available)" header.d=willtech.com.au
Received: from smtp3.osuosl.org ([127.0.0.1])
by localhost (smtp3.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id j65-qEdOts8u
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 5 Nov 2021 11:01:09 +0000 (UTC)
X-Greylist: delayed 00:09:05 by SQLgrey-1.8.0
Received: from brown.birch.relay.mailchannels.net
(brown.birch.relay.mailchannels.net [23.83.209.23])
by smtp3.osuosl.org (Postfix) with ESMTPS id 4247F605DC
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 5 Nov 2021 11:01:08 +0000 (UTC)
X-Sender-Id: hostpapa|x-authuser|damian@willtech.com.au
Received: from relay.mailchannels.net (localhost [127.0.0.1])
by relay.mailchannels.net (Postfix) with ESMTP id 0D478401DC9;
Fri, 5 Nov 2021 10:52:04 +0000 (UTC)
Received: from s110.servername.online
(100-96-133-198.trex.outbound.svc.cluster.local [100.96.133.198])
(Authenticated sender: hostpapa)
by relay.mailchannels.net (Postfix) with ESMTPA id E079B401DAE;
Fri, 5 Nov 2021 10:52:02 +0000 (UTC)
X-Sender-Id: hostpapa|x-authuser|damian@willtech.com.au
Received: from s110.servername.online (s110.servername.online [204.44.192.22])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384)
by 100.96.133.198 (trex/6.4.3); Fri, 05 Nov 2021 10:52:03 +0000
X-MC-Relay: Junk
X-MailChannels-SenderId: hostpapa|x-authuser|damian@willtech.com.au
X-MailChannels-Auth-Id: hostpapa
X-Trouble-Shade: 3e1c7a5a760147c6_1636109523799_2604697603
X-MC-Loop-Signature: 1636109523798:9964195
X-MC-Ingress-Time: 1636109523798
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed;
d=willtech.com.au; s=default; h=Content-Transfer-Encoding:Content-Type:
Message-ID:References:In-Reply-To:Subject:Cc:To:From:Date:MIME-Version:Sender
:Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From:
Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:
List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive;
bh=hg3ocI6nx68VtjK6Nf8m/ke3Btw+7UhYdAKKhTH5C0w=; b=uKMoy70nh+xMHm7luzRPyfa+45
Cm0VxKdKRYF05rA9w2mHoXIVoDCuzbwQIb8NT9BlPv4NHCa4IFIlSh6IxN+wPm43wkjsrbuv9XM5y
B0vXBDzvAbXRWzOx462G1xRehrl3lefN6cRYMYf9CZ+vmiEliZ/FX2FsYWVtR24y1Jojejif892zv
vrg9RhUuePSrF5EtYIX6LVLMVLWJa+V2D9sshK0Nt+6eDjjgXia/gkdtv4A8OVmmnbkhgARa7qGLQ
grWlJsPnCRJneHfj51h4kFkeRUryIpOri6kzBdno1nEvLLE7VMYC5Woi8tBptYiKcYgZloBp8vAjV
jKlSJ9GQ==;
Received: from localhost ([127.0.0.1]:49156 helo=s110.servername.online)
by s110.servername.online with esmtpa (Exim 4.94.2)
(envelope-from <damian@willtech.com.au>)
id 1miwpG-002ksN-S9; Fri, 05 Nov 2021 03:52:02 -0700
MIME-Version: 1.0
Date: Fri, 05 Nov 2021 03:52:00 -0700
From: damian@willtech.com.au
To: Prayank <prayank@tutanota.de>, Bitcoin Protocol Discussion
<bitcoin-dev@lists.linuxfoundation.org>
In-Reply-To: <MnjA6g0--3-2@tutanota.de>
References: <MmT9umZ--3-2@tutanota.de>
<20211020192054.GA117785@jauntyelephant.191.37.198.vultr.com>
<CAHiDt8A30DZtvsPnDDdtyVpho-NKKQhbP_4g8d0MGATawWvg_w@mail.gmail.com>
<MnjA6g0--3-2@tutanota.de>
User-Agent: Roundcube Webmail/1.4.11
Message-ID: <d86119700edb2eeaf9672375935bb74f@willtech.com.au>
X-Sender: damian@willtech.com.au
Content-Type: text/plain; charset=US-ASCII;
format=flowed
Content-Transfer-Encoding: 7bit
X-AuthUser: damian@willtech.com.au
X-Mailman-Approved-At: Fri, 05 Nov 2021 12:14:40 +0000
Subject: Re: [bitcoin-dev] bitcoin.org missing bitcoin core version 22.0
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: Fri, 05 Nov 2021 11:01:11 -0000
Good Afternoon,
Talk about the present and the future is misguided if it concludes that
the decentralisation of a project itself is responsible even if the
operation of the project is to produce a specification, and a software
capable of performing transactions in a decentralised manner. There is
no advantage or disadvantage to the project to have several choices of
the software implementation unless buffoons are misguided and wish to
attack fungibility or consensus, which the operation of consensus must
defend, in which case use [Bitcoin Core at version
21](https://github.com/bitcoin/bitcoin/tree/0.21) and [create a
fork](https://docs.github.com/en/get-started/quickstart/fork-a-repo) and
start developing. As you can see [Bitcoin Core version 20 has been
modified](https://github.com/bitcoin/bitcoin/branches) and no longer
passes checks similarly with version 18 which makes it more difficult to
compile make build. A person't own contributions are theirs, to delegate
is responsible, to try and create a seven headed lion to keep under
command like one would a gryphon is an infirmity.
Creating a properly delegated organisation, being a foundation for the
purpose of the maintenance of the consensus of Bitcoin a fungible
decentralised currency and the Bitcoin Core software is the sort of
thing I would easily consider but it is far more centralised to be an
operable concern. In short, as at the beginning, Bitcoin needs a few
heroes that can understand the whitepaper and write software and if the
work is too much one organisational foundation that does is correctly
stewardship. To decentralise one's own work only requires that there are
several offices available for those you employ to delegate to, but still
there requires for your project a headship.
Once the currency is fungible as you should now consider, just today
there was a public announcement that the Commonwealth Bank Of Australia
is going to allow buying and selling Bitcoin as one of its services, the
primary requirements are to defend the existing consensus as the right
of trade in every UTXO has value because of that consensus, and
particularly because of the ease of that trade.
I do not expect anybody is eligible to be dictated to in the Bitcoin
project, but people, be sensible, everybody has worked hard and the
project is becoming a success. Opportunities to further develop the
software of the coin and the protocol do not form part of the current
value, hardly. Several groaning seven headed lion's are
counterproductive if all they do is search for opportunities for change.
Change is the diametrically opposed of consensus and is consensus that
brings fungibility. You can already make any manner of instrument for
smart contract with your solicitor's office. What is necessary is the
operation of the Bitcoin protocol. The alternative to the deliberately
chosen consensus is a democracy, and you cannot build any software with
democracy, and people do not know what is good for them or they could
govern themselves. A few lessons in history assures government is
necessary to enshrine law and insist as the delegates of democracy for
its operation, to ensure a civilised and decent civility can exist.
Please, if you have concerned for Bitcoin, revoke your positions until
you fight for consensus.
KING JAMES HRMH
Great British Empire
Regards,
The Australian
LORD HIS EXCELLENCY JAMES HRMH (& HMRH)
of Hougun Manor & Glencoe & British Empire
MR. Damian A. James Williamson
Wills
et al.
Willtech
www.willtech.com.au
www.go-overt.com
duigco.org DUIGCO API
and other projects
m. 0487135719
f. +61261470192
This email does not constitute a general advice. Please disregard this
email if misdelivered.
On 2021-11-05 01:17, Prayank via bitcoin-dev wrote:
> Hi Kate,
>
>> He is taking the most sensible way forward, decreasing bus factor.
>
> Agree. Work being shared with other maintainers is an improvement.
>
>> Read: https://laanwj.github.io/2021/01/21/decentralize.html
>
> Interesting blog post. First paragraph talks about strange
> expectations, not sure what other people expected however I expected
> present maintainers will always have respect for the Founder of
> Bitcoin, keep important docs in repository, website etc. forever and
> respond with appropriate things if any rich scammers try to remove
> anything important. Anyway that chapter is over and this PR will
> always remain in history for others to see and make their own opinions
> about it: https://github.com/bitcoin-core/bitcoincore.org/pull/740
>
> What followed it (whitepaper being shared on different websites) was
> true decentralization and we need something similar in other aspects
> of full node implementations. Few things that can improve
> decentralization:
>
> 1.More people using alternative full node implementations. Right now
> 98% of nodes use Bitcoin Core.
>
> 2.More people like Luke Dashjr and Amir Taaki who do not simp for
> anyone. Being a contributor or maintainer in Bitcoin full node
> implementation is different from other open source projects. It was
> never going to be easy and it will get difficult with time,
>
> 3.More people from different countries getting involved in important
> roles.
>
> 4.Few anons.
>
> 5.Individuals and organizations who fund different Bitcoin projects
> should consider contributing in alternative. full node implementations
> as well. Maybe start with Bitcoin Knots.
>
> I am sure lot of people will find this controversial or disagree with
> it however this is my opinion and things that I think can improve
> Bitcoin. Will quote something from my recent medium post about a dev
> meetup and Knots:
>
> Accepting the problems, looking for solutions and trying to improve
> things is the best approach we as engineers can follow to do better
> things in Bitcoin. Irrational optimism is as toxic as irrational
> pessimism.
>
> https://prayankgahlot.medium.com/op-halloween21-and-bitcoin-knots-b8a4da4fa0bd
>
> Only ~1337 blocks left for Taproot to activate. So cheers to another
> soft fork being a success and Bitcoin improving regularly. Thanks to
> everyone who contributed including reviewers. Hoping most of the
> people will start using latest version of Bitcoin Core or other full
> node implementations soon.
>
> .
>
> --
>
> Prayank
>
> A3B1 E430 2298 178F
>
> Oct 21, 2021, 01:48 by mercedes.catherine.salazar@gmail.com:
>
>> Hi Owen,
>>
>> On Wed, Oct 20, 2021 at 9:25 PM Owen Gunden via bitcoin-dev
>> <bitcoin-dev@lists.linuxfoundation.org> wrote:
>>
>>> On Wed, Oct 20, 2021 at 04:47:17PM +0200, Prayank wrote:
>>>
>>>>> It seems confusing to have two sites that seemingly both
>>> represent
>>>
>>>>> bitcoin core.
>>>
>>>>
>>>
>>>> There is only one website which represents Bitcoin Core full
>>> node
>>>
>>>> implementation. You can download Bitcoin Core from
>>>
>>>> https://bitcoincore.org
>>>
>>> I also notice that, as of 22.0, Wladimir is no longer signing the
>>>
>>> releases, and I have no trust in my gpg network of the people who
>>> seem
>>>
>>> to have replaced him.
>>
>> He is taking the most sensible way forward, decreasing bus factor.
>>
>> Read: https://laanwj.github.io/2021/01/21/decentralize.html
>>
>>> Given the level of security at stake here, my eyebrows are raised
>>> at
>>>
>>> this combination of items changing (new website + new gpg signers
>>> at the
>>>
>>> same time).
>>
>> Don't worry and build your own release;
>>
>> but if you do, always verify the tree hash.
>>
>> Trust signed annotated tags.
>>
>> Cheers!
>>
>>> _______________________________________________
>>>
>>> bitcoin-dev mailing list
>>>
>>> bitcoin-dev@lists.linuxfoundation.org
>>>
>>> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
|