summaryrefslogtreecommitdiff
path: root/aa/a95beedf023f8a50474b4d0cf9d2641cc8afa0
blob: a2add6d305342d43cb4442c129336dbbebb907aa (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
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
Return-Path: <antoine.riard@gmail.com>
Received: from smtp1.osuosl.org (smtp1.osuosl.org [140.211.166.138])
 by lists.linuxfoundation.org (Postfix) with ESMTP id ACF83C002A
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Mon, 22 May 2023 01:27:55 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by smtp1.osuosl.org (Postfix) with ESMTP id 72E8682213
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Mon, 22 May 2023 01:27:55 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp1.osuosl.org 72E8682213
Authentication-Results: smtp1.osuosl.org;
 dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com
 header.a=rsa-sha256 header.s=20221208 header.b=F9SxzMvS
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: 1.612
X-Spam-Level: *
X-Spam-Status: No, score=1.612 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,
 FREEMAIL_REPLY=1, 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=no autolearn_force=no
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 66dvuvZ7FGsc
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Mon, 22 May 2023 01:27:54 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.8.0
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp1.osuosl.org EA6C682212
Received: from mail-io1-xd2e.google.com (mail-io1-xd2e.google.com
 [IPv6:2607:f8b0:4864:20::d2e])
 by smtp1.osuosl.org (Postfix) with ESMTPS id EA6C682212
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Mon, 22 May 2023 01:27:53 +0000 (UTC)
Received: by mail-io1-xd2e.google.com with SMTP id
 ca18e2360f4ac-76c4e1fe1d7so55778139f.3
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Sun, 21 May 2023 18:27:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=gmail.com; s=20221208; t=1684718873; x=1687310873;
 h=to:subject:message-id:date:from:in-reply-to:references:mime-version
 :from:to:cc:subject:date:message-id:reply-to;
 bh=ZJQtElzu+UD5ph8V4em11PgQpTFGHc0+htp6yYua+aY=;
 b=F9SxzMvSJ+XliUr2rYHhQEJdE5gx7omag6kC6iXqDp20knZwgY5c3N4ipS4iHyjat6
 8R8rdmC6TGtJFyaV+8kKFmJE1g5he0vNfa2UEXgyMfDKLvJahkqaItBQQJ2j59FM3uuq
 sA+BhRXbXWOlc83FKOKRzoGPAkB0tl7yodGrd3zY7h+RjJZa3E9XMyH7p5nrxxGjDxPc
 CiCOX1cwCE13ZcrIsvioOcE2YJ8WUEaiWWVtBEEvmm71qbxd4AWQd8QuJTbTXSRL1s0a
 ApnGmOlpzuD+y3qd6vR+LTf0Inc37y/LaRpCsocQ2bZ+YG7GON5FKuxqoHZYEAx7rtyC
 bnHw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20221208; t=1684718873; x=1687310873;
 h=to:subject:message-id:date:from:in-reply-to:references:mime-version
 :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to;
 bh=ZJQtElzu+UD5ph8V4em11PgQpTFGHc0+htp6yYua+aY=;
 b=lP+hd0BYlbT7E1I6FEBxr9vT6pEgHsBeqodaPNNsfQcexmzopfJ9+o/A0mBQQxTWIw
 ORtysr4pvhkwzjmdIsFsCyaVm9Q21ZuRg3loB4lDkZgmc3fCTR3KCBNwlSdwB/KkIEU3
 wC0/lSlq/CjpDgC7F2r2QkO7fvg9JCApbEtiqDbQA9o3q186quYAjMHgj7KUMyRLbCXd
 zfTBEXVTVQC6EykHvF5TsXcOG04dNhNuw8VcIze7oUqf/b3JLH6CbbfiYghDwCCEEVRb
 HHzbk3VZ4gJOvaEtca9OSZ4XVysRbBZQqwe6YQqtDEbFxU6+hAVql4mWJMg8T231xJFZ
 pjuw==
X-Gm-Message-State: AC+VfDzC6BtN6E/qqiPkSosM4OpgSfyN4ZKWdic9Gk2+lbzYJocb7Hb2
 FC2CubKIcom8FQL5OAEBeVwjIEYISa7OaGKHAL+8wJR7iLY=
X-Google-Smtp-Source: ACHHUZ4H6vH9ubpSEJ/wt6Wx+Vo949yrpEky26ku89j4U/oiAlvsmQMGT8hTyU9OHixZOqZClisSXf/ta9ZjyNtLhJI=
X-Received: by 2002:a6b:910:0:b0:76c:570f:ac84 with SMTP id
 t16-20020a6b0910000000b0076c570fac84mr5363628ioi.15.1684718872502; Sun, 21
 May 2023 18:27:52 -0700 (PDT)
MIME-Version: 1.0
References: <CAO1K=nmMBr9QJ8bCz+DZ=tfOdyA5phe3a7FhnBcbbUcM1M_YWQ@mail.gmail.com>
In-Reply-To: <CAO1K=nmMBr9QJ8bCz+DZ=tfOdyA5phe3a7FhnBcbbUcM1M_YWQ@mail.gmail.com>
From: Antoine Riard <antoine.riard@gmail.com>
Date: Mon, 22 May 2023 02:27:41 +0100
Message-ID: <CALZpt+FbcKNKYUvRzcVxGxtOtUP1u-oNo5rWW2ChOBD-HW5DmQ@mail.gmail.com>
To: F M <fmerli1@gmail.com>, 
 Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary="000000000000f1277505fc3e2da2"
X-Mailman-Approved-At: Mon, 22 May 2023 09:33:28 +0000
Subject: Re: [bitcoin-dev] A payout scheme for a non custodial mining pool
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, 22 May 2023 01:27:55 -0000

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

Hi Lorban,

The RFC is very clear and consistent on presenting payments pools in
the context of non-custodial mining pools, congrats to the authoring
team.

Few feedbacks, on the technical definition of a payment pool, the
common idea between all payment pools ideas presented so far
(Joinpool, Radixpool, Coinpool) is the pool tree (what you're calling
the payment tree) enabling a compact withdrawal from the pool, with
more or less conservation of the pooling after a withdrawal.

In 2., for the observation of the group of properties, there is one
more which matters a lot if you would like to have off-chain novation
of the pool tree, it's replay security, where a pool participant
cannot replay its withdrawal, partially or in whole, after withdrawing
all its balances.

In 2.1, "as, for an integer n, the n! rapidly grows in size, it
follows that the number of pre-signed transactions that has to be
computed rapidly becomes too large"."This problem seems to not have
been considered in [14]". The factorial complexity of the number of
states (transactions/balances) in function of the number pool
participants is mentioned in a footnote of the paper: "These
restrictions could be also achieved by pre-signing all possible
sequences of state transitions (producing, storing and exchanging all
these signatures), which scales poorly (factorial) with the number of
participants." and in the original mail post about Coinpool:
https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2020-June/017964.ht=
ml
:)

In 2.7, in the rational about using ANYPREVOUT, I think if you're
using the ANYPREVOUT variant, the spent output amount is committed by
the signature digest and I think this is introducing an
interdependency between the validity of the payment tree and the block
template of transactions, as in function of this latter the coinbase
reward fluctuates ? I believe ANYPREVOUTANYSCRIPT is better as there
is no such
commitment to the spent amount/scriptPubkey iirc.

About the attacks, effectively the lack of cooperation of pool
participants to enable cooperative withdrawal is a huge DoS factor, it
can be fought by fees to enter in the pool. Another deterrence is the
timelocking of the balance in case of non-cooperative closure. Past
force-closure of pools can be consumed as a proof of good-conduct by
future co-participants in a payment pool.

Best,
Antoine


Le mer. 3 mai 2023 =C3=A0 17:05, F M via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> a =C3=A9crit :

>
> https://docs.google.com/document/d/1qiOOSOT7epX658_nhjz-jj0DlnSRvytemOv_u=
_OtMcc/edit?usp=3Dsharing
>
>
> Dear community,
>
> In the last months there have been several discussions about the topic of
> covenants and payment pools
>
> [0]. It has been difficult to approach these topics as it seems that ther=
e
> is no agreement in a precise
>
> definition on what is a covenant or what is a payment pool. This is
> probably due to the great generality
>
> of these two concepts. Perhaps, a good approach to study them is to look
> at some different use-cases
>
> and see which are the properties that appear more often and enclose them
> in a clear definition. About
>
> payment pools, that may be considered themself as a covenant, we
> specialized further, studying a payment
>
> pool=E2=80=99s scheme that may be used for the miners of a mining pool in=
 order to
> share the ownership of the
>
> coinbase reward [1]. This would make the pool non-custodial.
>
> The main pools now are custodial, in the sense that they collect the
> rewards of mining, and use them
>
> subsequently to pay the miners. As there are few large pools that find
> almost all the blocks, custodial
>
> polls increase the level of centralization in a protocol born to be
> decentralized and consensus ruled.
>
> This is why we generally want non-custodial pools.
>
> The only non-custodial payment pool that appeared is P2Pool, active some
> years ago, that was also decentralized.
>
> In P2Pool, the miners were paid directly by an output of the coinbase
> transaction. This implies a very
>
> large coinbase, preventing the inclusion of more transactions in the
> block, and therefore collecting
>
> less fees and making the mining less profitable, compared to a custodial
> pool. This makes the P2Pool
>
> payout scheme inappropriate considering also that there is big effort in
> keeping blockchain light, with
>
> several off-chain protocols.
>
> Our scheme uses ANYPREVOUT signatures and it is based on the idea of
> payment trees. A payment tree is
>
> a tree of transactions that redistributes the funds to the payment pool
> participants, having their address
>
> to the leaves. The root contains the funds of the payment pool on n-of-n
> multisig. We allow payment trees
>
> for future payment pools, in which the input=E2=80=99s references of the
> transactions are left empty and the
>
> signatures are ANYPREVOUT.
>
> This makes it possible to safely create a payment pool, merge two payment
> pools and withdraw funds from
>
> a payment pool.
>
> Why do we use ANYPREVOUT? Most payment pool structures use precompiled
> transactions for allowing safe
>
> withdrawal. The signatures of these transactions clearly commits to the
> extranonce of the coinbase. So,
>
> if the payment pool is set for the co-ownership of the mining reward,
> there must be a set of precompiled
>
> transactions for every extranonce tried by every miner, that may not be
> feasible.
>
> The use of ANYPREVOUT allow the miners to collectively construct a paymen=
t
> tree that =E2=80=9Cwaits=E2=80=9D the rewards,
>
> in the case that some miners finds a block. This payment tree is unique
> for all miners.
>
> We assume the pool to be centralized, even though our payment pool scheme
> perhaps can be generalized
>
> to decentralized pools. We compared the average space occupied on the
> blockchain and compared with the
>
> one of P2Pool. The results seem to be promising in this aspect, and are
> even better if the Pool is KYC.
>
> Clearly, this is just a very brief summary of our work, that is enclosed
> and labeled as an RFC. So, every
>
> remark or comment may be very appreciated.
>
>
> Authors:
>
>    -
>
>    Lorban (HRF), https://github.com/lorbax/, lorenzo.bonax@gmail.com
>    -
>
>    Fi3, https://github.com/fi3/
>    -
>
>    Rachel Rybarczyk (Galaxy Digital), https://github.com/rrybarczyk
>
> PS
> Please note that although the linked document bears some resemblance to a
> research paper, it is presented as an RFC. We chose to publish it as an R=
FC
> because it is not intended to be a comprehensive work.
>
> [0]
> https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2022-July/020763.=
html
>
> [1]
> https://docs.google.com/document/d/1qiOOSOT7epX658_nhjz-jj0DlnSRvytemOv_u=
_OtMcc/edit?usp=3Dsharing
>
>
>
>
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>

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

<div dir=3D"ltr"><pre style=3D"color:rgb(0,0,0);word-wrap:break-word;white-=
space:pre-wrap"><font face=3D"arial, sans-serif">Hi Lorban,

The RFC is very clear and consistent on presenting payments pools in the co=
ntext of non-custodial mining pools, congrats to the authoring team.

Few feedbacks, on the technical definition of a payment pool, the common id=
ea between all payment pools ideas presented so far (Joinpool, Radixpool, C=
oinpool) is the pool tree (what you&#39;re calling the payment tree) enabli=
ng a compact withdrawal from the pool, with more or less conservation of th=
e pooling after a withdrawal.

In 2., for the observation of the group of properties, there is one more wh=
ich matters a lot if you would like to have off-chain novation of the pool =
tree, it&#39;s replay security, where a pool participant cannot replay its =
withdrawal, partially or in whole, after withdrawing all its balances.

In 2.1, &quot;as, for an integer n, the n! rapidly grows in size, it follow=
s that the number of pre-signed transactions that has to be computed rapidl=
y becomes too large&quot;.&quot;This problem seems to not have been conside=
red in [14]&quot;. The factorial complexity of the number of states (transa=
ctions/balances) in function of the number pool participants is mentioned i=
n a footnote of the paper: &quot;These restrictions could be also achieved =
by pre-signing all possible sequences of state transitions (producing, stor=
ing and exchanging all these signatures), which scales poorly (factorial) w=
ith the number of participants.&quot; and in the original mail post about C=
oinpool: <a href=3D"https://lists.linuxfoundation.org/pipermail/bitcoin-dev=
/2020-June/017964.html">https://lists.linuxfoundation.org/pipermail/bitcoin=
-dev/2020-June/017964.html</a> :)

In 2.7, in the rational about using ANYPREVOUT, I think if you&#39;re using=
 the ANYPREVOUT variant, the spent output amount is committed by the signat=
ure digest and I think this is introducing an interdependency between the v=
alidity of the payment tree and the block template of transactions, as in f=
unction of this latter the coinbase reward fluctuates ? I believe ANYPREVOU=
TANYSCRIPT is better as there is no such
commitment to the spent amount/scriptPubkey iirc.

About the attacks, effectively the lack of cooperation of pool participants=
 to enable cooperative withdrawal is a huge DoS factor, it can be fought by=
 fees to enter in the pool. Another deterrence is the timelocking of the ba=
lance in case of non-cooperative closure. Past force-closure of pools can b=
e consumed as a proof of good-conduct by future co-participants in a paymen=
t pool.

Best,
Antoine</font></pre></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" c=
lass=3D"gmail_attr">Le=C2=A0mer. 3 mai 2023 =C3=A0=C2=A017:05, F M via bitc=
oin-dev &lt;<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoi=
n-dev@lists.linuxfoundation.org</a>&gt; a =C3=A9crit=C2=A0:<br></div><block=
quote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-w=
idth:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding=
-left:1ex"><div dir=3D"ltr"><p dir=3D"ltr" style=3D"line-height:1.38;margin=
-top:0pt;margin-bottom:0pt" id=3D"m_2045163968729918722gmail-docs-internal-=
guid-6964bd70-7fff-0d0e-503e-ab84601abcff"><span style=3D"font-size:11pt;fo=
nt-family:Arial;color:rgb(0,0,0);background-color:transparent;font-weight:4=
00;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal=
;font-variant-east-asian:normal;text-decoration:none;vertical-align:baselin=
e;white-space:pre-wrap"><a href=3D"https://docs.google.com/document/d/1qiOO=
SOT7epX658_nhjz-jj0DlnSRvytemOv_u_OtMcc/edit?usp=3Dsharing" target=3D"_blan=
k">https://docs.google.com/document/d/1qiOOSOT7epX658_nhjz-jj0DlnSRvytemOv_=
u_OtMcc/edit?usp=3Dsharing</a><br></span></p><p dir=3D"ltr" style=3D"line-h=
eight:1.38;margin-top:0pt;margin-bottom:0pt"><span style=3D"font-size:11pt;=
font-family:Arial;color:rgb(0,0,0);background-color:transparent;font-weight=
:400;font-style:normal;font-variant-ligatures:normal;font-variant-caps:norm=
al;font-variant-east-asian:normal;text-decoration:none;vertical-align:basel=
ine;white-space:pre-wrap"><br></span></p><p dir=3D"ltr" style=3D"line-heigh=
t:1.38;margin-top:0pt;margin-bottom:0pt" id=3D"m_2045163968729918722gmail-d=
ocs-internal-guid-ed790be8-7fff-cd7b-cba3-d2110597bd15"><span style=3D"font=
-size:11pt;font-family:Arial;color:rgb(0,0,0);background-color:transparent;=
font-weight:400;font-style:normal;font-variant-ligatures:normal;font-varian=
t-caps:normal;font-variant-east-asian:normal;text-decoration:none;vertical-=
align:baseline;white-space:pre-wrap">Dear community,</span></p><p dir=3D"lt=
r" style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style=
=3D"font-size:11pt;font-family:Arial;color:rgb(0,0,0);background-color:tran=
sparent;font-weight:400;font-style:normal;font-variant-ligatures:normal;fon=
t-variant-caps:normal;font-variant-east-asian:normal;text-decoration:none;v=
ertical-align:baseline;white-space:pre-wrap">In the last months there have =
been several discussions about the topic of covenants and payment pools</sp=
an></p><p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-botto=
m:0pt"><span style=3D"font-size:11pt;font-family:Arial;color:rgb(0,0,0);bac=
kground-color:transparent;font-weight:400;font-style:normal;font-variant-li=
gatures:normal;font-variant-caps:normal;font-variant-east-asian:normal;text=
-decoration:none;vertical-align:baseline;white-space:pre-wrap">[0]. It has =
been difficult to approach these topics as it seems that there is no agreem=
ent in a precise</span></p><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;=
color:rgb(0,0,0);background-color:transparent;font-weight:400;font-style:no=
rmal;font-variant-ligatures:normal;font-variant-caps:normal;font-variant-ea=
st-asian:normal;text-decoration:none;vertical-align:baseline;white-space:pr=
e-wrap">definition on what is a covenant or what is a payment pool. This is=
 probably due to the great generality</span></p><p dir=3D"ltr" style=3D"lin=
e-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style=3D"font-size:11=
pt;font-family:Arial;color:rgb(0,0,0);background-color:transparent;font-wei=
ght:400;font-style:normal;font-variant-ligatures:normal;font-variant-caps:n=
ormal;font-variant-east-asian:normal;text-decoration:none;vertical-align:ba=
seline;white-space:pre-wrap">of these two concepts. Perhaps, a good approac=
h to study them is to look at some different use-cases</span></p><p dir=3D"=
ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span styl=
e=3D"font-size:11pt;font-family:Arial;color:rgb(0,0,0);background-color:tra=
nsparent;font-weight:400;font-style:normal;font-variant-ligatures:normal;fo=
nt-variant-caps:normal;font-variant-east-asian:normal;text-decoration:none;=
vertical-align:baseline;white-space:pre-wrap">and see which are the propert=
ies that appear more often and enclose them in a clear definition. About</s=
pan></p><p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bott=
om:0pt"><span style=3D"font-size:11pt;font-family:Arial;color:rgb(0,0,0);ba=
ckground-color:transparent;font-weight:400;font-style:normal;font-variant-l=
igatures:normal;font-variant-caps:normal;font-variant-east-asian:normal;tex=
t-decoration:none;vertical-align:baseline;white-space:pre-wrap">payment poo=
ls, that may be considered themself as a covenant, we specialized further, =
studying a payment</span></p><p dir=3D"ltr" style=3D"line-height:1.38;margi=
n-top:0pt;margin-bottom:0pt"><span style=3D"font-size:11pt;font-family:Aria=
l;color:rgb(0,0,0);background-color:transparent;font-weight:400;font-style:=
normal;font-variant-ligatures:normal;font-variant-caps:normal;font-variant-=
east-asian:normal;text-decoration:none;vertical-align:baseline;white-space:=
pre-wrap">pool=E2=80=99s scheme that may be used for the miners of a mining=
 pool in order to share the ownership of the</span></p><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;color:rgb(0,0,0);background-color:transparent;f=
ont-weight:400;font-style:normal;font-variant-ligatures:normal;font-variant=
-caps:normal;font-variant-east-asian:normal;text-decoration:none;vertical-a=
lign:baseline;white-space:pre-wrap">coinbase reward [1]. This would make th=
e pool non-custodial.</span></p><p dir=3D"ltr" style=3D"line-height:1.38;ma=
rgin-top:0pt;margin-bottom:0pt"><span style=3D"font-size:11pt;font-family:A=
rial;color:rgb(0,0,0);background-color:transparent;font-weight:400;font-sty=
le:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-varia=
nt-east-asian:normal;text-decoration:none;vertical-align:baseline;white-spa=
ce:pre-wrap">The main pools now are custodial, in the sense that they colle=
ct the rewards of mining, and use them</span></p><p dir=3D"ltr" style=3D"li=
ne-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style=3D"font-size:1=
1pt;font-family:Arial;color:rgb(0,0,0);background-color:transparent;font-we=
ight:400;font-style:normal;font-variant-ligatures:normal;font-variant-caps:=
normal;font-variant-east-asian:normal;text-decoration:none;vertical-align:b=
aseline;white-space:pre-wrap">subsequently to pay the miners. As there are =
few large pools that find almost all the blocks, custodial</span></p><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;color:rgb(0,0,0);background-color=
:transparent;font-weight:400;font-style:normal;font-variant-ligatures:norma=
l;font-variant-caps:normal;font-variant-east-asian:normal;text-decoration:n=
one;vertical-align:baseline;white-space:pre-wrap">polls increase the level =
of centralization in a protocol born to be decentralized and consensus rule=
d.</span></p><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;color:rgb(0,0,=
0);background-color:transparent;font-weight:400;font-style:normal;font-vari=
ant-ligatures:normal;font-variant-caps:normal;font-variant-east-asian:norma=
l;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">This i=
s why we generally want non-custodial pools.</span></p><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;color:rgb(0,0,0);background-color:transparent;f=
ont-weight:400;font-style:normal;font-variant-ligatures:normal;font-variant=
-caps:normal;font-variant-east-asian:normal;text-decoration:none;vertical-a=
lign:baseline;white-space:pre-wrap">The only non-custodial payment pool tha=
t appeared is P2Pool, active some years ago, that was also decentralized.</=
span></p><p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bot=
tom:0pt"><span style=3D"font-size:11pt;font-family:Arial;color:rgb(0,0,0);b=
ackground-color:transparent;font-weight:400;font-style:normal;font-variant-=
ligatures:normal;font-variant-caps:normal;font-variant-east-asian:normal;te=
xt-decoration:none;vertical-align:baseline;white-space:pre-wrap">In P2Pool,=
 the miners were paid directly by an output of the coinbase transaction. Th=
is implies a very</span></p><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=
;color:rgb(0,0,0);background-color:transparent;font-weight:400;font-style:n=
ormal;font-variant-ligatures:normal;font-variant-caps:normal;font-variant-e=
ast-asian:normal;text-decoration:none;vertical-align:baseline;white-space:p=
re-wrap">large coinbase, preventing the inclusion of more transactions in t=
he block, and therefore collecting</span></p><p dir=3D"ltr" style=3D"line-h=
eight:1.38;margin-top:0pt;margin-bottom:0pt"><span style=3D"font-size:11pt;=
font-family:Arial;color:rgb(0,0,0);background-color:transparent;font-weight=
:400;font-style:normal;font-variant-ligatures:normal;font-variant-caps:norm=
al;font-variant-east-asian:normal;text-decoration:none;vertical-align:basel=
ine;white-space:pre-wrap">less fees and making the mining less profitable, =
compared to a custodial pool. This makes the P2Pool</span></p><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;color:rgb(0,0,0);background-color:tran=
sparent;font-weight:400;font-style:normal;font-variant-ligatures:normal;fon=
t-variant-caps:normal;font-variant-east-asian:normal;text-decoration:none;v=
ertical-align:baseline;white-space:pre-wrap">payout scheme inappropriate co=
nsidering also that there is big effort in keeping blockchain light, with</=
span></p><p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bot=
tom:0pt"><span style=3D"font-size:11pt;font-family:Arial;color:rgb(0,0,0);b=
ackground-color:transparent;font-weight:400;font-style:normal;font-variant-=
ligatures:normal;font-variant-caps:normal;font-variant-east-asian:normal;te=
xt-decoration:none;vertical-align:baseline;white-space:pre-wrap">several of=
f-chain protocols.</span></p><p dir=3D"ltr" style=3D"line-height:1.38;margi=
n-top:0pt;margin-bottom:0pt"><span style=3D"font-size:11pt;font-family:Aria=
l;color:rgb(0,0,0);background-color:transparent;font-weight:400;font-style:=
normal;font-variant-ligatures:normal;font-variant-caps:normal;font-variant-=
east-asian:normal;text-decoration:none;vertical-align:baseline;white-space:=
pre-wrap">Our scheme uses ANYPREVOUT signatures and it is based on the idea=
 of payment trees. A payment tree is</span></p><p dir=3D"ltr" style=3D"line=
-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style=3D"font-size:11p=
t;font-family:Arial;color:rgb(0,0,0);background-color:transparent;font-weig=
ht:400;font-style:normal;font-variant-ligatures:normal;font-variant-caps:no=
rmal;font-variant-east-asian:normal;text-decoration:none;vertical-align:bas=
eline;white-space:pre-wrap">a tree of transactions that redistributes the f=
unds to the payment pool participants, having their address</span></p><p di=
r=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span=
 style=3D"font-size:11pt;font-family:Arial;color:rgb(0,0,0);background-colo=
r:transparent;font-weight:400;font-style:normal;font-variant-ligatures:norm=
al;font-variant-caps:normal;font-variant-east-asian:normal;text-decoration:=
none;vertical-align:baseline;white-space:pre-wrap">to the leaves. The root =
contains the funds of the payment pool on n-of-n multisig. We allow payment=
 trees</span></p><p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;ma=
rgin-bottom:0pt"><span style=3D"font-size:11pt;font-family:Arial;color:rgb(=
0,0,0);background-color:transparent;font-weight:400;font-style:normal;font-=
variant-ligatures:normal;font-variant-caps:normal;font-variant-east-asian:n=
ormal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">fo=
r future payment pools, in which the input=E2=80=99s references of the tran=
sactions are left empty and the</span></p><p dir=3D"ltr" style=3D"line-heig=
ht:1.38;margin-top:0pt;margin-bottom:0pt"><span style=3D"font-size:11pt;fon=
t-family:Arial;color:rgb(0,0,0);background-color:transparent;font-weight:40=
0;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;=
font-variant-east-asian:normal;text-decoration:none;vertical-align:baseline=
;white-space:pre-wrap">signatures are ANYPREVOUT.</span></p><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;color:rgb(0,0,0);background-color:transpar=
ent;font-weight:400;font-style:normal;font-variant-ligatures:normal;font-va=
riant-caps:normal;font-variant-east-asian:normal;text-decoration:none;verti=
cal-align:baseline;white-space:pre-wrap">This makes it possible to safely c=
reate a payment pool, merge two payment pools and withdraw funds from</span=
></p><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;color:rgb(0,0,0);backg=
round-color:transparent;font-weight:400;font-style:normal;font-variant-liga=
tures:normal;font-variant-caps:normal;font-variant-east-asian:normal;text-d=
ecoration:none;vertical-align:baseline;white-space:pre-wrap">a payment pool=
.</span></p><br><p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;mar=
gin-bottom:0pt"><span style=3D"font-size:11pt;font-family:Arial;color:rgb(0=
,0,0);background-color:transparent;font-weight:400;font-style:normal;font-v=
ariant-ligatures:normal;font-variant-caps:normal;font-variant-east-asian:no=
rmal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">Why=
 do we use ANYPREVOUT? Most payment pool structures use precompiled transac=
tions for allowing safe</span></p><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;color:rgb(0,0,0);background-color:transparent;font-weight:400;font-s=
tyle:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-var=
iant-east-asian:normal;text-decoration:none;vertical-align:baseline;white-s=
pace:pre-wrap">withdrawal. The signatures of these transactions clearly com=
mits to the extranonce of the coinbase. So,</span></p><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;color:rgb(0,0,0);background-color:transparent;f=
ont-weight:400;font-style:normal;font-variant-ligatures:normal;font-variant=
-caps:normal;font-variant-east-asian:normal;text-decoration:none;vertical-a=
lign:baseline;white-space:pre-wrap">if the payment pool is set for the co-o=
wnership of the mining reward, there must be a set of precompiled</span></p=
><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;color:rgb(0,0,0);backgroun=
d-color:transparent;font-weight:400;font-style:normal;font-variant-ligature=
s:normal;font-variant-caps:normal;font-variant-east-asian:normal;text-decor=
ation:none;vertical-align:baseline;white-space:pre-wrap">transactions for e=
very extranonce tried by every miner, that may not be feasible.</span></p><=
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;color:rgb(0,0,0);background-=
color:transparent;font-weight:400;font-style:normal;font-variant-ligatures:=
normal;font-variant-caps:normal;font-variant-east-asian:normal;text-decorat=
ion:none;vertical-align:baseline;white-space:pre-wrap">The use of ANYPREVOU=
T allow the miners to collectively construct a payment tree that =E2=80=9Cw=
aits=E2=80=9D the rewards,</span></p><p dir=3D"ltr" style=3D"line-height:1.=
38;margin-top:0pt;margin-bottom:0pt"><span style=3D"font-size:11pt;font-fam=
ily:Arial;color:rgb(0,0,0);background-color:transparent;font-weight:400;fon=
t-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-=
variant-east-asian:normal;text-decoration:none;vertical-align:baseline;whit=
e-space:pre-wrap">in the case that some miners finds a block. This payment =
tree is unique for all miners.</span></p><br><p dir=3D"ltr" style=3D"line-h=
eight:1.38;margin-top:0pt;margin-bottom:0pt"><span style=3D"font-size:11pt;=
font-family:Arial;color:rgb(0,0,0);background-color:transparent;font-weight=
:400;font-style:normal;font-variant-ligatures:normal;font-variant-caps:norm=
al;font-variant-east-asian:normal;text-decoration:none;vertical-align:basel=
ine;white-space:pre-wrap">We assume the pool to be centralized, even though=
 our payment pool scheme perhaps can be generalized</span></p><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;color:rgb(0,0,0);background-color:tran=
sparent;font-weight:400;font-style:normal;font-variant-ligatures:normal;fon=
t-variant-caps:normal;font-variant-east-asian:normal;text-decoration:none;v=
ertical-align:baseline;white-space:pre-wrap">to decentralized pools. We com=
pared the average space occupied on the blockchain and compared with the</s=
pan></p><p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bott=
om:0pt"><span style=3D"font-size:11pt;font-family:Arial;color:rgb(0,0,0);ba=
ckground-color:transparent;font-weight:400;font-style:normal;font-variant-l=
igatures:normal;font-variant-caps:normal;font-variant-east-asian:normal;tex=
t-decoration:none;vertical-align:baseline;white-space:pre-wrap">one of P2Po=
ol. The results seem to be promising in this aspect, and are even better if=
 the Pool is KYC.</span></p><br><p dir=3D"ltr" style=3D"line-height:1.38;ma=
rgin-top:0pt;margin-bottom:0pt"><span style=3D"font-size:11pt;font-family:A=
rial;color:rgb(0,0,0);background-color:transparent;font-weight:400;font-sty=
le:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-varia=
nt-east-asian:normal;text-decoration:none;vertical-align:baseline;white-spa=
ce:pre-wrap">Clearly, this is just a very brief summary of our work, that i=
s enclosed and labeled as an RFC. So, every</span></p><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;color:rgb(0,0,0);background-color:transparent;f=
ont-weight:400;font-style:normal;font-variant-ligatures:normal;font-variant=
-caps:normal;font-variant-east-asian:normal;text-decoration:none;vertical-a=
lign:baseline;white-space:pre-wrap">remark or comment may be very appreciat=
ed.</span></p><p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margi=
n-bottom:0pt" id=3D"m_2045163968729918722gmail-docs-internal-guid-90a39756-=
7fff-4eb1-7865-91daf252bc8b"></p><p dir=3D"ltr" style=3D"line-height:1.38;m=
argin-top:0pt;margin-bottom:0pt"><br></p><p dir=3D"ltr" style=3D"line-heigh=
t:1.38;margin-top:0pt;margin-bottom:0pt"><span style=3D"font-size:11pt;font=
-family:Arial;color:rgb(0,0,0);background-color:transparent;font-weight:400=
;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;f=
ont-variant-east-asian:normal;text-decoration:none;vertical-align:baseline;=
white-space:pre-wrap">Authors:</span></p><ul style=3D"margin-top:0px;margin=
-bottom:0px"><li dir=3D"ltr" style=3D"list-style-type:disc;font-size:11pt;f=
ont-family:Arial;color:rgb(0,0,0);background-color:transparent;font-weight:=
400;font-style:normal;font-variant-ligatures:normal;font-variant-caps:norma=
l;font-variant-east-asian:normal;text-decoration:none;vertical-align:baseli=
ne;white-space:pre-wrap"><p dir=3D"ltr" style=3D"line-height:1.38;margin-to=
p:12pt;margin-bottom:0pt" role=3D"presentation"><span style=3D"font-size:11=
pt;font-family:Arial;color:rgb(0,0,0);background-color:transparent;font-wei=
ght:400;font-style:normal;font-variant-ligatures:normal;font-variant-caps:n=
ormal;font-variant-east-asian:normal;text-decoration:none;vertical-align:ba=
seline;white-space:pre-wrap">Lorban (HRF),</span><a href=3D"https://github.=
com/lorbax/" style=3D"text-decoration:none" target=3D"_blank"><span style=
=3D"font-size:11pt;font-family:Arial;color:rgb(0,0,0);background-color:tran=
sparent;font-weight:400;font-style:normal;font-variant-ligatures:normal;fon=
t-variant-caps:normal;font-variant-east-asian:normal;text-decoration:none;v=
ertical-align:baseline;white-space:pre-wrap"> </span><span style=3D"font-si=
ze:11pt;font-family:Arial;color:rgb(17,85,204);background-color:transparent=
;font-weight:400;font-style:normal;font-variant-ligatures:normal;font-varia=
nt-caps:normal;font-variant-east-asian:normal;text-decoration:underline;ver=
tical-align:baseline;white-space:pre-wrap">https://github.com/lorbax/</span=
></a><span style=3D"font-size:11pt;font-family:Arial;color:rgb(0,0,0);backg=
round-color:transparent;font-weight:400;font-style:normal;font-variant-liga=
tures:normal;font-variant-caps:normal;font-variant-east-asian:normal;text-d=
ecoration:none;vertical-align:baseline;white-space:pre-wrap">, <a href=3D"m=
ailto:lorenzo.bonax@gmail.com" target=3D"_blank">lorenzo.bonax@gmail.com</a=
></span></p></li><li dir=3D"ltr" style=3D"list-style-type:disc;font-size:11=
pt;font-family:Arial;color:rgb(0,0,0);background-color:transparent;font-wei=
ght:400;font-style:normal;font-variant-ligatures:normal;font-variant-caps:n=
ormal;font-variant-east-asian:normal;text-decoration:none;vertical-align:ba=
seline;white-space:pre-wrap"><p dir=3D"ltr" style=3D"line-height:1.38;margi=
n-top:0pt;margin-bottom:0pt" role=3D"presentation"><span style=3D"font-size=
:11pt;font-family:Arial;color:rgb(0,0,0);background-color:transparent;font-=
weight:400;font-style:normal;font-variant-ligatures:normal;font-variant-cap=
s:normal;font-variant-east-asian:normal;text-decoration:none;vertical-align=
:baseline;white-space:pre-wrap">Fi3,</span><a href=3D"https://github.com/fi=
3/" style=3D"text-decoration:none" target=3D"_blank"><span style=3D"font-si=
ze:11pt;font-family:Arial;color:rgb(0,0,0);background-color:transparent;fon=
t-weight:400;font-style:normal;font-variant-ligatures:normal;font-variant-c=
aps:normal;font-variant-east-asian:normal;text-decoration:none;vertical-ali=
gn:baseline;white-space:pre-wrap"> </span><span style=3D"font-size:11pt;fon=
t-family:Arial;color:rgb(17,85,204);background-color:transparent;font-weigh=
t:400;font-style:normal;font-variant-ligatures:normal;font-variant-caps:nor=
mal;font-variant-east-asian:normal;text-decoration:underline;vertical-align=
:baseline;white-space:pre-wrap">https://github.com/fi3/</span></a></p></li>=
<li dir=3D"ltr" style=3D"list-style-type:disc;font-size:11pt;font-family:Ar=
ial;color:rgb(0,0,0);background-color:transparent;font-weight:400;font-styl=
e:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-varian=
t-east-asian:normal;text-decoration:none;vertical-align:baseline;white-spac=
e:pre-wrap"><p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-=
bottom:12pt" role=3D"presentation"><span style=3D"font-size:11pt;font-famil=
y:Arial;color:rgb(0,0,0);background-color:transparent;font-weight:400;font-=
style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-va=
riant-east-asian:normal;text-decoration:none;vertical-align:baseline;white-=
space:pre-wrap">Rachel Rybarczyk (Galaxy Digital),</span><a href=3D"https:/=
/github.com/rrybarczyk" style=3D"text-decoration:none" target=3D"_blank"><s=
pan style=3D"font-size:11pt;font-family:Arial;color:rgb(0,0,0);background-c=
olor:transparent;font-weight:400;font-style:normal;font-variant-ligatures:n=
ormal;font-variant-caps:normal;font-variant-east-asian:normal;text-decorati=
on:none;vertical-align:baseline;white-space:pre-wrap"> </span><span style=
=3D"font-size:11pt;font-family:Arial;color:rgb(17,85,204);background-color:=
transparent;font-weight:400;font-style:normal;font-variant-ligatures:normal=
;font-variant-caps:normal;font-variant-east-asian:normal;text-decoration:un=
derline;vertical-align:baseline;white-space:pre-wrap">https://github.com/rr=
ybarczyk</span></a></p></li></ul><p dir=3D"ltr" style=3D"line-height:1.38;m=
argin-top:12pt;margin-bottom:12pt"><span style=3D"font-size:11pt;font-famil=
y:Arial;color:rgb(0,0,0);background-color:transparent;font-weight:400;font-=
style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-va=
riant-east-asian:normal;text-decoration:none;vertical-align:baseline;white-=
space:pre-wrap">PS</span><span style=3D"font-size:11pt;font-family:Arial;co=
lor:rgb(0,0,0);background-color:transparent;font-weight:400;font-style:norm=
al;font-variant-ligatures:normal;font-variant-caps:normal;font-variant-east=
-asian:normal;text-decoration:none;vertical-align:baseline;white-space:pre-=
wrap"><br></span><span style=3D"font-size:11pt;font-family:Arial;color:rgb(=
0,0,0);background-color:transparent;font-weight:400;font-style:normal;font-=
variant-ligatures:normal;font-variant-caps:normal;font-variant-east-asian:n=
ormal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">Pl=
ease note that although the linked document bears some resemblance to a res=
earch paper, it is presented as an RFC. We chose to publish it as an RFC be=
cause it is not intended to be a comprehensive work.</span></p><br><p dir=
=3D"ltr" style=3D"line-height:1.38;margin-top:12pt;margin-bottom:12pt"><spa=
n style=3D"font-size:11pt;font-family:Arial;color:rgb(0,0,0);background-col=
or:transparent;font-weight:400;font-style:normal;font-variant-ligatures:nor=
mal;font-variant-caps:normal;font-variant-east-asian:normal;text-decoration=
:none;vertical-align:baseline;white-space:pre-wrap">[0]</span><a href=3D"ht=
tps://lists.linuxfoundation.org/pipermail/bitcoin-dev/2022-July/020763.html=
" style=3D"text-decoration:none" target=3D"_blank"><span style=3D"font-size=
:11pt;font-family:Arial;color:rgb(0,0,0);background-color:transparent;font-=
weight:400;font-style:normal;font-variant-ligatures:normal;font-variant-cap=
s:normal;font-variant-east-asian:normal;text-decoration:none;vertical-align=
:baseline;white-space:pre-wrap"> </span><span style=3D"font-size:11pt;font-=
family:Arial;color:rgb(17,85,204);background-color:transparent;font-weight:=
400;font-style:normal;font-variant-ligatures:normal;font-variant-caps:norma=
l;font-variant-east-asian:normal;text-decoration:underline;vertical-align:b=
aseline;white-space:pre-wrap">https://lists.linuxfoundation.org/pipermail/b=
itcoin-dev/2022-July/020763.html</span></a></p><p dir=3D"ltr" style=3D"line=
-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style=3D"font-size:11p=
t;font-family:Arial;color:rgb(0,0,0);background-color:transparent;font-weig=
ht:400;font-style:normal;font-variant-ligatures:normal;font-variant-caps:no=
rmal;font-variant-east-asian:normal;text-decoration:none;vertical-align:bas=
eline;white-space:pre-wrap">[1]</span><a href=3D"https://docs.google.com/do=
cument/d/1qiOOSOT7epX658_nhjz-jj0DlnSRvytemOv_u_OtMcc/edit?usp=3Dsharing" s=
tyle=3D"text-decoration:none" target=3D"_blank"><span style=3D"font-size:11=
pt;font-family:Arial;color:rgb(17,85,204);background-color:transparent;font=
-weight:400;font-style:normal;font-variant-ligatures:normal;font-variant-ca=
ps:normal;font-variant-east-asian:normal;text-decoration:underline;vertical=
-align:baseline;white-space:pre-wrap">https://docs.google.com/document/d/1q=
iOOSOT7epX658_nhjz-jj0DlnSRvytemOv_u_OtMcc/edit?usp=3Dsharing</span><span s=
tyle=3D"font-size:11pt;font-family:Arial;color:rgb(17,85,204);background-co=
lor:transparent;font-weight:400;font-style:normal;font-variant-ligatures:no=
rmal;font-variant-caps:normal;font-variant-east-asian:normal;text-decoratio=
n:underline;vertical-align:baseline;white-space:pre-wrap"><br></span><span =
style=3D"font-size:11pt;font-family:Arial;color:rgb(17,85,204);background-c=
olor:transparent;font-weight:400;font-style:normal;font-variant-ligatures:n=
ormal;font-variant-caps:normal;font-variant-east-asian:normal;text-decorati=
on:underline;vertical-align:baseline;white-space:pre-wrap"><br><br></span><=
/a></p><br><br><br><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;color:rg=
b(0,0,0);background-color:transparent;font-weight:400;font-style:normal;fon=
t-variant-ligatures:normal;font-variant-caps:normal;font-variant-east-asian=
:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">=
</span></p></div>
_______________________________________________<br>
bitcoin-dev mailing list<br>
<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=3D"_blank">=
bitcoin-dev@lists.linuxfoundation.org</a><br>
<a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" =
rel=3D"noreferrer" target=3D"_blank">https://lists.linuxfoundation.org/mail=
man/listinfo/bitcoin-dev</a><br>
</blockquote></div>

--000000000000f1277505fc3e2da2--