summaryrefslogtreecommitdiff
path: root/ed/c856c7ced65ea409fdde191825aafe6b8bcd1e
blob: f2192e900bde9ec9799d24fff55928525a8e798d (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
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
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
Return-Path: <loneroassociation@gmail.com>
Received: from smtp1.osuosl.org (smtp1.osuosl.org [IPv6:2605:bc80:3010::138])
 by lists.linuxfoundation.org (Postfix) with ESMTP id 445E4C0001
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Sun, 14 Mar 2021 05:46:08 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by smtp1.osuosl.org (Postfix) with ESMTP id 1C78183DF6
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Sun, 14 Mar 2021 05:46:08 +0000 (UTC)
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: -2.088
X-Spam-Level: 
X-Spam-Status: No, score=-2.088 tagged_above=-999 required=5
 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
 DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001,
 HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001,
 SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01]
 autolearn=ham autolearn_force=no
Authentication-Results: smtp1.osuosl.org (amavisd-new);
 dkim=pass (2048-bit key) header.d=gmail.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 rgCBT9luwZZy
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Sun, 14 Mar 2021 05:46:06 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.8.0
Received: from mail-yb1-xb2a.google.com (mail-yb1-xb2a.google.com
 [IPv6:2607:f8b0:4864:20::b2a])
 by smtp1.osuosl.org (Postfix) with ESMTPS id B009083DE4
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Sun, 14 Mar 2021 05:46:06 +0000 (UTC)
Received: by mail-yb1-xb2a.google.com with SMTP id c131so29824874ybf.7
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Sat, 13 Mar 2021 21:46:06 -0800 (PST)
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=XhzzQQpIoLhNw5ibKKiJuqVVI3qoTtt9rnPXmbIPSWo=;
 b=Qe4W65wO9XrZLlEuqIGbTdg8nFYRA8V7JabW2IGyK/L07FnBe1AkdNOG1EuQwI7pQQ
 R6N8QRUjS29F8/hX0Ai+iv9IYP8ddhI4/KdQZQzP3FuuKLAsPr3n2V/sD1M9Z633ha3f
 zEKZnVfoAfg+k4ezgEt4XF1K3uM/owaf2PKsXqANB7pgh1a8d6AJsk+2D0KioZf/JT5o
 7g9mF1Klaw/cieeMvrBvJLLfc/7nCP70e+NE76yD5cqLd2eqT0tGjEDbMP4/e89ERu7B
 Y9nUjLmTSkx3FmAXo0TsWRX4D1R3OUfS2l62Yomy6+wsGqHuGzLOWU06mZW8d5D4ofKx
 AVCA==
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=XhzzQQpIoLhNw5ibKKiJuqVVI3qoTtt9rnPXmbIPSWo=;
 b=ZaXYjQx1CSc4kCYK7omwj4HoIHMZnI8z7gMpwacB0g/7bCq/ajpPmdB+Y904+BJtri
 jwykXVRIA0AiHM9xE1Rp73Gue/704E8Ki23djRK6sRgDyYn36xDApSK38xsdkLmRsOWl
 UX7xjvvw7Ji/jKu8BnH2tf2b4EQND4W9mfN21ypa2gSugQFlBBtCEmxC6FSbfVbG4f1v
 NP/tQg6qd5VcoYksYyOUaTC3jvU1+dx3gBvC+fmQQ2BimPkT2i4n4Wc2OGi2IGs014O1
 8IdnqSt9EoYgAQB9xyGC3m7tZ5k6n7v2y1GCopaME4Y1OtKFN71GED7JmvIzIyrDi8XK
 2EYg==
X-Gm-Message-State: AOAM532HKFW8sMQSZ4Xha/C7gbMjmLu70RsjWqfgWe+e+3ov2bETT8Z5
 5166MDCyb/6hwpnlzawOIhrOwYqbUyEgj0p5sQusGM6YXE4=
X-Google-Smtp-Source: ABdhPJxJmdev1w9sTJkJUjbXAwcQDRla0KsKaEghyI+lWNcHs3oybHYRgzuDtA8nYGwmUQK3ydIEzJAc1zY+cxPc8Uk=
X-Received: by 2002:a25:a246:: with SMTP id b64mr28790224ybi.236.1615700765379; 
 Sat, 13 Mar 2021 21:46:05 -0800 (PST)
MIME-Version: 1.0
References: <CA+YkXXzOre2nhaC9gPWe0Qa30+434_vC+Q0WsVz=kxKk4HjvEg@mail.gmail.com>
 <296-604d1600-db-42a1fb80@93437088>
In-Reply-To: <296-604d1600-db-42a1fb80@93437088>
From: Lonero Foundation <loneroassociation@gmail.com>
Date: Sun, 14 Mar 2021 00:45:53 -0500
Message-ID: <CA+YkXXwTEvq=Rk=iSgyrSYr-Q0G=Ov3jdMk8saUnA8q5p-aKuw@mail.gmail.com>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary="0000000000002f0f4605bd78a620"
X-Mailman-Approved-At: Sun, 14 Mar 2021 13:40:47 +0000
Subject: Re: [bitcoin-dev] BIP Proposal: Consensus (hard fork) PoST
 Datastore for Energy Efficient Mining
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: Sun, 14 Mar 2021 05:46:08 -0000

--0000000000002f0f4605bd78a620
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

I have added quite a bit more details. I haven't made any UML diagrams just
yet. I did add a basic non-technical infographic though, and more then
likely making a technical UML for the cryptographic mechanisms will be on
my to-do list. I have also updated the terminology and added a bit more
content.

Best regards, Andrew

On Sat, Mar 13, 2021, 2:44 PM email@yancy.lol <email@yancy.lol> wrote:

> My mistake for thinking your text was generated text, and my humor was no=
t
> meant to be directed at you, so apologies if you took it personally.
>
>
> PS: The AI overlord is no joke
>
> Cheers,
> -Yancy
>
> On Saturday, March 13, 2021 18:11 CET, Lonero Foundation <
> loneroassociation@gmail.com> wrote:
>
>
> Hi, no worries. I made the changes now in the GitHub repository and pull
> request. I'm hoping for a BIP # soon. Thanks for the feedback, and I gues=
s
> the sense of humor.
>
> Best regards, Andrew
>
> On Sat, Mar 13, 2021, 10:45 AM yancy <email@yancy.lol> wrote:
>
>> Ok thanks.  Using the correct terminology helps people understand what
>> you're talking about and take you seriously.
>>
>> Cheers,
>> -Yancy
>>
>>
>> Mar 13, 2021 4:02:18 PM Lonero Foundation <loneroassociation@gmail.com>:
>>
>> Hi, I know the differences between the cryptographic hashing algorithm
>> and key validation. I know hashing is for SHA, but was referring to asym=
metric
>> cryptography in regards to the key validation. I should have used a
>> different term though instead of, "In regards to cryptographic hashing,"=
, I
>> should have stated in regards to cryptographic key validation. There are=
 a
>> few other dubious clarifications or minor edits I should make in order t=
o
>> not draw confusion. I will do a repo update today. Honest mistake, but
>> enough with the sarcasm.
>>
>> Best regards, Andrew
>>
>> On Sat, Mar 13, 2021, 3:13 AM email@yancy.lol <email@yancy.lol> wrote:
>>
>>> My email was not intended as an insult.  Your proposal seemed a bit lik=
e
>>> gibberish and made some obvious mistakes as pointed out before (such as
>>> conflating secp256k1 with sha256), and so I was genuinely curious if yo=
u
>>> were a bot spamming the list.
>>>
>>>
>>> Maybe a more interesting topic is, can GPT3 be used to generate a BIP?
>>> How long before our AI overlord produces improvements to Bitcoin?  At w=
hat
>>> point will the AI have more than 51% of commit frequency?  Will we have
>>> lost the war to our new centralized overlord?
>>>
>>> Cheers,
>>> -Yancy
>>>
>>>
>>> On Saturday, March 13, 2021 00:31 CET, Lonero Foundation <
>>> loneroassociation@gmail.com> wrote:
>>>
>>>
>>> Also, I already stated I was referring to signature validation
>>> cryptography in that aspect:
>>> https://wizardforcel.gitbooks.io/practical-cryptography-for-developers-=
book/content/digital-signatures/ecdsa-sign-verify-examples.html
>>> My BIP has a primary purpose in regards to what I want to develop proof=
s
>>> for and the different cryptographic elements I want to develop proofs f=
or.
>>> That said to those who disagree with the premise, I do prefer
>>> constructive feedback over insults or making fun of one another. After =
all
>>> this is an improvement proposal with a specific purpose aiming to devel=
op a
>>> specific thing, not a guy who is just wanting to copy and paste a
>>> repository and call it a day.
>>>
>>> Best regards, Andrew
>>>
>>> On Fri, Mar 12, 2021 at 6:21 PM Lonero Foundation <
>>> loneroassociation@gmail.com> wrote:
>>>
>>>> Hi, I also want to emphasize that my main point isn't just to create a
>>>> BTC hardfork or become another Bitcoin Cash, Gold, or SV. The main poi=
nt in
>>>> regards to this BIP actually expands POW rather than replaces or creat=
es an
>>>> alternative. Many of the problems faced in regards to security in the
>>>> future as well as sustainability is something I believe lots of the ch=
anges
>>>> I am proposing can fix. In regards to technological implementation, on=
ce
>>>> this is assigned draft status I am more than willing to create preprin=
ts
>>>> explaining the cryptography, hashing algorithm improvements, and conse=
nsus
>>>> that I am working on. This is a highly technologically complex idea th=
at I
>>>> am willing to "call my bluff on" and expand upon. As for it being a dr=
aft,
>>>> I think this is a good starting point at least for draft status prior =
to
>>>> working on technological implementation.
>>>>
>>>> Best regards, Andrew
>>>>
>>>> On Fri, Mar 12, 2021 at 5:37 PM email@yancy.lol <email@yancy.lol>
>>>> wrote:
>>>>
>>>>> I think Andrew himself is an algo.  The crypto training set must not
>>>>> be very good.
>>>>>
>>>>> Cheers,
>>>>> -Yancy
>>>>>
>>>>> On Friday, March 12, 2021 17:54 CET, Lonero Foundation via bitcoin-de=
v
>>>>> <bitcoin-dev@lists.linuxfoundation.org> wrote:
>>>>>
>>>>>
>>>>> =E2=80=A6
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>>
>>
>>
>
>
>

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

<div dir=3D"auto">I have added quite a bit more details. I haven&#39;t made=
 any UML diagrams just yet. I did add a basic non-technical infographic tho=
ugh, and more then likely making a technical UML for the cryptographic mech=
anisms will be on my to-do list. I have also updated the terminology and ad=
ded a bit more content.<div dir=3D"auto"><br></div><div dir=3D"auto">Best r=
egards, Andrew</div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" c=
lass=3D"gmail_attr">On Sat, Mar 13, 2021, 2:44 PM email@yancy.lol &lt;email=
@yancy.lol&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"m=
argin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><p dir=3D"ltr=
" style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt" id=3D"m_65532=
4507113837888docs-internal-guid-be47d78b-7fff-e62f-3a7d-3f65dada23ee"><span=
 style=3D"font-size:11pt;font-family:Arial;background-color:transparent;fon=
t-weight:400;font-style:normal;font-variant:normal;text-decoration:none;ver=
tical-align:baseline;white-space:pre-wrap">My mistake for thinking your tex=
t was generated text, and my humor was not meant to be directed at you, so =
apologies if you took it personally.</span></p>=C2=A0<p dir=3D"ltr" style=
=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style=3D"font-=
size:11pt;font-family:Arial;background-color:transparent;font-weight:400;fo=
nt-style:normal;font-variant:normal;text-decoration:none;vertical-align:bas=
eline;white-space:pre-wrap">PS: The AI overlord is no joke</span></p><br>Ch=
eers,<br>-Yancy<br><br>On Saturday, March 13, 2021 18:11 CET, Lonero Founda=
tion &lt;<a href=3D"mailto:loneroassociation@gmail.com" target=3D"_blank" r=
el=3D"noreferrer">loneroassociation@gmail.com</a>&gt; wrote:<br>=C2=A0<bloc=
kquote type=3D"cite" cite=3D"http://CA+YkXXzOre2nhaC9gPWe0Qa30+434_vC+Q0WsV=
z=3DkxKk4HjvEg@mail.gmail.com"><div dir=3D"auto">Hi, no worries. I made the=
 changes now in the GitHub repository and pull request. I&#39;m hoping for =
a BIP # soon. Thanks for the feedback, and I guess the sense of humor.<div =
dir=3D"auto">=C2=A0</div><div dir=3D"auto">Best regards, Andrew</div></div>=
=C2=A0<div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On S=
at, Mar 13, 2021, 10:45 AM yancy &lt;email@yancy.lol&gt; wrote:</div><block=
quote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc=
 solid;padding-left:1ex"><div><span style=3D"font-family:sans-serif">Ok tha=
nks.=C2=A0 Using the correct terminology helps people understand what you&#=
39;re talking about and take you seriously.</span><br><br><span style=3D"fo=
nt-family:sans-serif">Cheers,</span><br><span style=3D"font-family:sans-ser=
if">-Yancy</span><div>=C2=A0<p>Mar 13, 2021 4:02:18 PM Lonero Foundation &l=
t;<a rel=3D"noreferrer noreferrer" href=3D"mailto:loneroassociation@gmail.c=
om" target=3D"_blank">loneroassociation@gmail.com</a>&gt;:</p><blockquote><=
div dir=3D"auto">Hi, I know the differences between the cryptographic hashi=
ng algorithm and key validation. I know hashing is for SHA, but was referri=
ng to=C2=A0<span>asymmetric cryptography in regards to the key validation. =
I should have used a different term though instead of, &quot;In regards to =
cryptographic hashing,&quot;, I should have stated in regards to cryptograp=
hic key validation. There are a few other dubious clarifications or minor e=
dits I should make in order to not draw confusion. I will do a repo update =
today. Honest mistake, but enough with the sarcasm.</span><div dir=3D"auto"=
>=C2=A0</div><div dir=3D"auto">Best regards, Andrew</div></div>=C2=A0<div c=
lass=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Sat, Mar 13, =
2021, 3:13 AM email@yancy.lol &lt;email@yancy.lol&gt; wrote:</div><blockquo=
te class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc so=
lid;padding-left:1ex"><p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0=
pt;margin-bottom:0pt" id=3D"m_655324507113837888m_-24665084329890104m_-7605=
373105595509035m_8158420199876589271m_-1581779554600417290m_-17411290091809=
98294m_3490105251412115872m_-7757793637796267019m_-5697419812760722977docs-=
internal-guid-4056a8b1-7fff-9296-3427-4d2e04c785c7"><span style=3D"backgrou=
nd-color:transparent;font-variant:normal;white-space:pre-wrap;font-weight:4=
00;text-decoration:none;vertical-align:baseline;font-size:11pt;font-family:=
Arial;font-style:normal">My email was not intended as an insult.=C2=A0 Your=
 proposal seemed a bit like gibberish and made some obvious mistakes as poi=
nted out before (such as conflating secp256k1 with sha256), and so I was ge=
nuinely curious if you were a bot spamming the list.</span></p>=C2=A0<p dir=
=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span =
style=3D"background-color:transparent;font-variant:normal;white-space:pre-w=
rap;font-weight:400;text-decoration:none;vertical-align:baseline;font-size:=
11pt;font-family:Arial;font-style:normal">Maybe a more interesting topic is=
, can GPT3 be used to generate a BIP?=C2=A0 How long before our AI overlord=
 produces improvements to Bitcoin?=C2=A0 At what point will the AI have mor=
e than 51% of commit frequency?=C2=A0 Will we have lost the war to our new =
centralized overlord?</span></p><br>Cheers,<br>-Yancy<br><br><br>On Saturda=
y, March 13, 2021 00:31 CET, Lonero Foundation &lt;<a rel=3D"noreferrer nor=
eferrer noreferrer noreferrer noreferrer noreferrer noreferrer noreferrer n=
oreferrer" href=3D"mailto:loneroassociation@gmail.com" target=3D"_blank">lo=
neroassociation@gmail.com</a>&gt; wrote:<br>=C2=A0<blockquote type=3D"cite"=
 cite=3D"http://CA+YkXXw5uh4yfvqDiBBEXcq188PEGku-NFFAq7uNuAFTG3ooTQ@mail.gm=
ail.com"><div dir=3D"ltr"><div>Also, I already stated I was referring to si=
gnature validation cryptography in that aspect: <a rel=3D"noreferrer norefe=
rrer noreferrer noreferrer noreferrer noreferrer noreferrer noreferrer nore=
ferrer" href=3D"https://wizardforcel.gitbooks.io/practical-cryptography-for=
-developers-book/content/digital-signatures/ecdsa-sign-verify-examples.html=
" target=3D"_blank">https://wizardforcel.gitbooks.io/practical-cryptography=
-for-developers-book/content/digital-signatures/ecdsa-sign-verify-examples.=
html</a></div><div>My BIP has a primary purpose in regards to what I want t=
o develop proofs for and the different cryptographic elements I want to dev=
elop proofs for.</div><div>That said to those who disagree with the premise=
, I do prefer constructive feedback over insults or making fun of one anoth=
er. After all this is an improvement proposal with a specific purpose aimin=
g to develop a specific thing, not a guy who is just wanting to copy and pa=
ste a repository and call it a day.</div><div>=C2=A0</div><div>Best regards=
, Andrew</div></div>=C2=A0<div class=3D"gmail_quote"><div dir=3D"ltr" class=
=3D"gmail_attr">On Fri, Mar 12, 2021 at 6:21 PM Lonero Foundation &lt;<a re=
l=3D"noreferrer noreferrer noreferrer noreferrer noreferrer noreferrer nore=
ferrer noreferrer noreferrer" href=3D"mailto:loneroassociation@gmail.com" t=
arget=3D"_blank">loneroassociation@gmail.com</a>&gt; wrote:</div><blockquot=
e class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px s=
olid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div>Hi, I also wa=
nt to emphasize that my main point isn&#39;t just to create a BTC hardfork =
or become another Bitcoin Cash, Gold, or SV. The main point in regards to t=
his BIP actually expands POW rather than replaces or creates an alternative=
. Many of the problems faced in regards to security in the future as well a=
s sustainability is something I believe lots of the changes I am proposing =
can fix. In regards to technological implementation, once this is assigned =
draft status I am more than willing to create preprints explaining the cryp=
tography, hashing algorithm improvements, and consensus that I am working o=
n. This is a highly technologically complex idea that I am willing to &quot=
;call my bluff on&quot; and expand upon. As for it being a draft, I think t=
his is a good starting point at least for draft status prior to working on =
technological implementation.</div><div>=C2=A0</div><div>Best regards, Andr=
ew</div></div>=C2=A0<div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gm=
ail_attr">On Fri, Mar 12, 2021 at 5:37 PM email@yancy.lol &lt;email@yancy.l=
ol&gt; wrote:</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0p=
x 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">I thin=
k Andrew himself is an algo.=C2=A0 The crypto training set must not be very=
 good.<br><br>Cheers,<br>-Yancy<br><br>On Friday, March 12, 2021 17:54 CET,=
 Lonero Foundation via bitcoin-dev &lt;<a rel=3D"noreferrer noreferrer nore=
ferrer noreferrer noreferrer noreferrer noreferrer noreferrer noreferrer" h=
ref=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=3D"_blank">bitc=
oin-dev@lists.linuxfoundation.org</a>&gt; wrote:<br>=C2=A0<blockquote type=
=3D"cite" cite=3D"http://CA+YkXXz9aHfZtt-it_8w4ovF=3D-QaZ4_9vwDS0Kz36qhHwVD=
C5Q@mail.gmail.com">=E2=80=A6</blockquote><br><br><br>=C2=A0</blockquote></=
div></blockquote></div></blockquote><br><br><br>=C2=A0</blockquote></div></=
blockquote></div></div></blockquote></div></blockquote><br><br><br>=C2=A0
</blockquote></div>

--0000000000002f0f4605bd78a620--