summaryrefslogtreecommitdiff
path: root/c6/5bfd0180abf6362273320c99aa1fac9779a6d6
blob: f0c8368f6079a5b62e0241e7a6348e8b142b0e3b (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
Return-Path: <earonesty@gmail.com>
Received: from smtp1.osuosl.org (smtp1.osuosl.org [IPv6:2605:bc80:3010::138])
 by lists.linuxfoundation.org (Postfix) with ESMTP id 2217AC0033
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Mon,  5 Dec 2022 17:01:16 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by smtp1.osuosl.org (Postfix) with ESMTP id F366281A2B
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Mon,  5 Dec 2022 17:01:13 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp1.osuosl.org F366281A2B
Authentication-Results: smtp1.osuosl.org;
 dkim=pass (2048-bit key) header.d=q32-com.20210112.gappssmtp.com
 header.i=@q32-com.20210112.gappssmtp.com header.a=rsa-sha256
 header.s=20210112 header.b=px6W6HQw
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: 0.6
X-Spam-Level: 
X-Spam-Status: No, score=0.6 tagged_above=-999 required=5
 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
 FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001,
 HEADER_FROM_DIFFERENT_DOMAINS=0.249, HTML_MESSAGE=0.001,
 PDS_OTHER_BAD_TLD=1.999, RCVD_IN_DNSWL_NONE=-0.0001,
 SPF_HELO_NONE=0.001, SPF_PASS=-0.001] 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 Fp-hGZvExkEW
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Mon,  5 Dec 2022 17:01:11 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.8.0
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp1.osuosl.org EEBD581926
Received: from mail-ua1-x931.google.com (mail-ua1-x931.google.com
 [IPv6:2607:f8b0:4864:20::931])
 by smtp1.osuosl.org (Postfix) with ESMTPS id EEBD581926
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Mon,  5 Dec 2022 17:01:10 +0000 (UTC)
Received: by mail-ua1-x931.google.com with SMTP id q6so4103505uao.9
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Mon, 05 Dec 2022 09:01:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=q32-com.20210112.gappssmtp.com; s=20210112;
 h=to:subject:message-id:date:from:in-reply-to:references:mime-version
 :from:to:cc:subject:date:message-id:reply-to;
 bh=Ded4BsaqyUsgge72qF7OM6rai2Ztj7SODSmBn96b6xM=;
 b=px6W6HQwSYkUqeZ4mG+2EMuv+GW35cUOHusF5UR5eVwj/DZaHLDCUrN/CSof84qy1A
 FexqWLjKTUANeH/+pRmhJYoYo/w5VIvWPQ2onpNWNCrsDFSGaKsc3B/xQAEDCvqCoApH
 13vQj207Oa4QiVrE7J3gpvqxZZWZt47UIhSW9yAMfNrgO9xgISWy5kCHoyKtkMPbYy0x
 HR80sbMGx7VKL+GMy7FeQzQir73GiJBhUZC0a4g1w0jbySPPqXNEDpzcuBL5P2tKaonU
 6uq2TEilgFlWVebZvmdrXV9LaGcQtqutl6LisBx/saTaX8m/TA37/FKmVTXLqV1LtmT/
 7Ktw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20210112;
 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=Ded4BsaqyUsgge72qF7OM6rai2Ztj7SODSmBn96b6xM=;
 b=DA2H5ly0nTm2JgOJKQqOL/sUQiyFb7tlOGAcrINfdgqjWgjnNSugMGq4mtdhwrBuE5
 xsv5+Tu2ZZb6KPgpV3PfrtuhKCA6s6QWKT0SyKweqGyfvU8h/6prtQMrCuVfyi6y/iUu
 lCfQFHgnzKqoXEZdRKFk8fUL4Wx4iJG7TS2ilFRgpUxtdQjyHkuBMGMwFEgMz8FWBntt
 g2zhoR1Z6W79zOTNRq2/wVk7pb2PLbhtq9fSdAZdfH/y8q3759fnXLLZhmUugeSqU+p0
 mJh7jKdeSx2fLqYWvGhpQQZZXb+MEUVJhvtMEN4JcWNZ5B/+vTK1F96WLPyX6VxW4113
 OGAw==
X-Gm-Message-State: ANoB5pk/RH+hwmBwjAN9S9159Sx9kVMuuMme4LeMAytR49Gka/vlwhBS
 vv3q8VNh4aU51PkVWdBBEI7vTN5vys9NM50+XJM+H/T5nPSW
X-Google-Smtp-Source: AA0mqf7vELN/xGkT5G0H1t7tHkL0dgc3aKL6ynVQxzKZi/XCWijsoyK+TEqL14ePrgmxrqy3mEWgKteBEnz0ynbksnI=
X-Received: by 2002:ab0:b8e:0:b0:404:3611:fb13 with SMTP id
 c14-20020ab00b8e000000b004043611fb13mr44839357uak.54.1670259668010; Mon, 05
 Dec 2022 09:01:08 -0800 (PST)
MIME-Version: 1.0
References: <Y2I3w8O5X55sD/3C@petertodd.org> <Y2qc7Ubc5xtJhxGw@petertodd.org>
 <Y3MlSE7AWkBgiCyr@erisian.com.au> <Y3OljVGQbZ/Wj8T6@petertodd.org>
 <CAPapNH3NEBP2-GVZZ_75K-QU0psGdAHyjdAus-vfq-0jffTstg@mail.gmail.com>
 <d1ea77a4-370f-d7e3-82c2-765c9fc18aa3@protonmail.com>
In-Reply-To: <d1ea77a4-370f-d7e3-82c2-765c9fc18aa3@protonmail.com>
From: Erik Aronesty <erik@q32.com>
Date: Mon, 5 Dec 2022 12:00:56 -0500
Message-ID: <CAJowKgLdsGcSyR7znhLpmMe6cPgLR9ivTiBcXx3pZPLBDUkR9A@mail.gmail.com>
To: Rijndael <rot13maxi@protonmail.com>, 
 Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary="00000000000031d3cb05ef17a2d4"
X-Mailman-Approved-At: Mon, 05 Dec 2022 18:57:59 +0000
Subject: Re: [bitcoin-dev] Announcement: Full-RBF Miner Bounty
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, 05 Dec 2022 17:01:16 -0000

--00000000000031d3cb05ef17a2d4
Content-Type: text/plain; charset="UTF-8"

note: if it was possible to enforce this, we wouldn't need proof of work at
all.   since it isn't possible, proof of work is strictly necessary.


On Mon, Dec 5, 2022 at 9:53 AM Rijndael via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:

> Good morning,
>
> That sounds like a very dangerous mode of operation. You can already hand
> a transaction to a miner privately. I hand a transaction to a miner with
> some reasonable fee, and then I go and broadcast a different transaction
> with a minimal fee that spends the same inputs. The whole network
> (including the miner I handed the tx to) could all be running with a strict
> first-seen mempool policy, but we can still have a situation where the
> miner creates a block with a different transaction from what you see in
> your mempool. If anytime this happens, the nodes running your proposed rule
> drop the block, then anyone can fork those nodes off the network whenever
> they want.
>
> Even outside of adversarial settings, Bitcoin doesn't (and doesn't attempt
> to) promise consistency across mempools. Making a consensus rule that
> enforces mempool consistency is a recipe for (unintended?) chainsplits.
>
> - rijndael
>
>
> On 12/5/22 7:20 AM, El_Hoy via bitcoin-dev wrote:
>
> The only option I see against the attack Peter Todd is doing to opt-in RBF
> and 0Conf bitcoin usage is working on a bitcoin core implementation that
> stops propagation of full-rbf replaced blocks. Running multiple of such
> nodes on the network will add a risk to miners that enable full-rbf that
> would work as an incentive against that.
>
> Obviously that would require adding an option on bitcoin core (that is not
> technically but politically difficult to implement as Petter Todd already
> have commit access to the main repository).
>
> That said, a sufficiently incentivized actor (like Daniel Lipshitz or Muun
> wallet developers) could work on a fork and run several nodes with such
> functionality. As far as I understand the percolation model, with 10 to 20
> nodes running such a rule would create a significant risk for full-rbf
> miners.
>
> Regards.
>
> ---  Eloy
>
>
> On Tue, Nov 15, 2022 at 11:43 AM Peter Todd via bitcoin-dev <
> bitcoin-dev@lists.linuxfoundation.org> wrote:
>
>> On Tue, Nov 15, 2022 at 03:36:08PM +1000, Anthony Towns via bitcoin-dev
>> wrote:
>> > On Tue, Nov 08, 2022 at 01:16:13PM -0500, Peter Todd via bitcoin-dev
>> wrote:
>> > > FYI I've gotten a few hundred dollars worth of donations to this
>> effort, and
>> > > have raised the reward to about 0.02 BTC, or $400 USD at current
>> prices.
>> >
>> > Seems like this has been mostly claimed (0.014btc / $235, 9238sat/vb):
>>
>> I'm turning it back on when (if) the mempool settles down. I've got more
>> than
>> enough donations to give another run at it (the majority was donated
>> privately
>> FWIW). There's a risk of the mempool filling up again of course; hard to
>> avoid
>> that.
>>
>> Right now of course it's really easy to double spend with the obvious
>> low-fee/high-fee method as the min relay fee keeps shifting.
>>
>> >
>> https://mempool.space/tx/397dcbe4e95ec40616e3dfc4ff8ffa158d2e72020b7d11fc2be29d934d69138c
>> >
>> > The block it was claimed in seems to have been about an hour after the
>> > default mempool filled up:
>> >
>> > https://twitter.com/murchandamus/status/1592274621977477120
>> >
>> > That block actually seems to have included two
>> > alice.btc.calendar.opentimestamps.org txs, the other paying $7.88
>> > (309sat/vb):
>> >
>> >
>> https://mempool.space/tx/ba9670109a6551458d5e1e23600c7bf2dc094894abdf59fe7aa020ccfead07cf
>>
>> The second is because I turned down the full-rbf reward to more normal fee
>> levels. There's also another full-rbf double-spend from the Bob calendar,
>> along
>> the same lines:
>> 7e76b351009326a574f3120164dbbe6d85e07e04a7bbdc40f0277fcb008d2cd2
>>
>> I double-spent the txin of the high fee tx that got mined. But I
>> mistakenly had
>> RBF enabled in that double-spend, so while it propagated initially, I
>> believe
>> it was replaced when something (someone?) rebroadcast the high-fee 397dcb
>> tx.
>>
>> > Timeline (utc) to me looks like:
>> >
>> >  - 13:12 - block 763148 is mined: last one that had a min fee <
>> 1.5sat/vb
>> >  - 13:33 -
>> f503868c64d454c472859b793f3ee7cdc8f519c64f8b1748d8040cd8ce6dc6e1
>> >            is announced and propogates widely (1.2sat/vb)
>> >  - 18:42 -
>> 746daab9bcc331be313818658b4a502bb4f3370a691fd90015fabcd7759e0944
>> >            is announced and propogates widely (1.2sat/vb)
>> >  - 21:52 - ba967010 tx is announced and propogates widely, since
>> >            conflicting tx 746daab9 has been removed from default
>> >          mempools
>> >  - 21:53 - murch tweets about default mempool filling up
>> >  - 22:03 - 397dcbe4 tx is announced and propogates widely, since
>> >            conflicting tx f503868 has already been removed from default
>> >          mempools
>>
>> Is that 22:03 time for 397 from your node's logs? It was originally
>> announced
>> hours earlier. From one of my full-rbf nodes:
>>
>>     2022-11-14T14:08:37Z [mempool] replacing tx
>> 764867062b67fea61810c3858d587da83a28290545e882935a32285028084317 with
>> 397dcbe4e95ec40616e3dfc4ff8ffa158d2e72020b7d11fc2be29d934d69138c for
>> 0.00468 additional fees, -1 delta bytes
>>
>> >  - 22:35 - block 763189 is mined
>> >  - 22:39 - block 763190 is mined
>> >  - 23:11 - block 763191 is mined
>> >  - 23:17 - block 763192 is mined including 397dcbe4
>> >
>> > miningpool.observer reports both 397dcbe4 and ba967010 as missing in the
>> > first three blocks, and gives similar mempool ages for those txs to what
>> > my logs report:
>> >
>> >
>> https://miningpool.observer/template-and-block/0000000000000000000436aba59d8430061e0e50592215f7f263bfb1073ccac7
>> >
>> https://miningpool.observer/template-and-block/00000000000000000005600404792bacfd8a164d2fe9843766afb2bfbd937309
>> >
>> https://miningpool.observer/template-and-block/00000000000000000004a3073f58c9eae40f251ea7aeaeac870daeac4b238fd1
>> >
>> > That presumably means those pools (AntPool twice and "unknown") are
>> > running with large mempools that didn't kept the earlier 1.2sat/vb txs.
>>
>> To be clear, you think that AntPool and that other exchange is running
>> with a
>> larger than normal max mempool size limit? You mean those miners *did*
>> keep the
>> earlier 1.2sat/vb tx?
>>
>> > The txs were mined by Foundry:
>> >
>> >
>> https://miningpool.observer/template-and-block/00000000000000000001382a226aedac822de80309cca2bf1253b35d4f8144f5
>> >
>> > This seems to be pretty good evidence that we currently don't have any
>> > significant hashrate mining with fullrbf policies (<0.5% if there was a
>> > high fee replacement available prior to every block having been mined),
>> > despite the bounty having been collected.
>>
>> Oh, we can put much lower bounds on that. I've been running OTS calendars
>> with
>> full-rbf replacements for a few months without clear evidence of a
>> full-rbf
>> replacement.  While there was good reason to think some miners were mining
>> full-rbf before a few years back, they probably didn't bother to reapply
>> their
>> patches each upgrade. `mempoolfullrbf=1` is much simpler to use.
>>
>> --
>> https://petertodd.org 'peter'[:-1]@petertodd.org
>> _______________________________________________
>> 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
>

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

<div dir=3D"ltr">note: if it was possible=C2=A0to enforce this, we wouldn&#=
39;t need proof of work at all.=C2=A0 =C2=A0since it isn&#39;t possible, pr=
oof of work is strictly necessary.<div><br></div></div><br><div class=3D"gm=
ail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Mon, Dec 5, 2022 at 9:5=
3 AM Rijndael via bitcoin-dev &lt;<a href=3D"mailto:bitcoin-dev@lists.linux=
foundation.org">bitcoin-dev@lists.linuxfoundation.org</a>&gt; wrote:<br></d=
iv><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;bord=
er-left:1px solid rgb(204,204,204);padding-left:1ex">
   =20
 =20
  <div>
    <p>Good morning,<br>
    </p>
    <p>That sounds like a very dangerous mode of operation. You can
      already hand a transaction to a miner privately. I hand a
      transaction to a miner with some reasonable fee, and then I go and
      broadcast a different transaction with a minimal fee that spends
      the same inputs. The whole network (including the miner I handed
      the tx to) could all be running with a strict first-seen mempool
      policy, but we can still have a situation where the miner creates
      a block with a different transaction from what you see in your
      mempool. If anytime this happens, the nodes running your proposed
      rule drop the block, then anyone can fork those nodes off the
      network whenever they want. <br>
    </p>
    <p>Even outside of adversarial settings, Bitcoin doesn&#39;t (and
      doesn&#39;t attempt to) promise consistency across mempools. Making a
      consensus rule that enforces mempool consistency is a recipe for
      (unintended?) chainsplits. <br>
    </p>
    <p>- rijndael<br>
    </p>
    <p><br>
    </p>
    <div>On 12/5/22 7:20 AM, El_Hoy via
      bitcoin-dev wrote:<br>
    </div>
    <blockquote type=3D"cite">
     =20
      <div dir=3D"ltr">
        <div>The only option I see against the attack Peter Todd is
          doing to opt-in RBF and 0Conf bitcoin usage is working on a
          bitcoin core implementation that stops propagation of full-rbf
          replaced blocks. Running multiple of such nodes on the network
          will add a risk to miners that enable full-rbf that would work
          as an incentive against that.</div>
        <div><br>
        </div>
        <div>Obviously that would require adding an option on bitcoin
          core (that is not technically but politically difficult to
          implement as Petter Todd already have commit access to the
          main repository).</div>
        <div><br>
        </div>
        <div>That said, a sufficiently incentivized actor (like Daniel
          Lipshitz or Muun wallet developers) could work on a fork and
          run several nodes with such functionality. As far as I
          understand the percolation model, with 10 to 20 nodes running
          such a rule would create a significant risk for full-rbf
          miners.</div>
        <div><br>
        </div>
        <div>Regards.<br>
        </div>
        <div><br>
        </div>
        <div>
          <div dir=3D"ltr">
            <div dir=3D"ltr"><span style=3D"color:rgb(56,118,29)"><span sty=
le=3D"font-family:arial,helvetica,sans-serif">---=C2=A0
                  Eloy</span></span><br>
            </div>
          </div>
        </div>
        <br>
      </div>
      <br>
      <div class=3D"gmail_quote">
        <div dir=3D"ltr" class=3D"gmail_attr">On Tue, Nov 15, 2022 at 11:43
          AM Peter Todd via bitcoin-dev &lt;<a href=3D"mailto:bitcoin-dev@l=
ists.linuxfoundation.org" target=3D"_blank">bitcoin-dev@lists.linuxfoundati=
on.org</a>&gt;
          wrote:<br>
        </div>
        <blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex=
;border-left:1px solid rgb(204,204,204);padding-left:1ex">On
          Tue, Nov 15, 2022 at 03:36:08PM +1000, Anthony Towns via
          bitcoin-dev wrote:<br>
          &gt; On Tue, Nov 08, 2022 at 01:16:13PM -0500, Peter Todd via
          bitcoin-dev wrote:<br>
          &gt; &gt; FYI I&#39;ve gotten a few hundred dollars worth of
          donations to this effort, and<br>
          &gt; &gt; have raised the reward to about 0.02 BTC, or $400
          USD at current prices.<br>
          &gt; <br>
          &gt; Seems like this has been mostly claimed (0.014btc / $235,
          9238sat/vb):<br>
          <br>
          I&#39;m turning it back on when (if) the mempool settles down.
          I&#39;ve got more than<br>
          enough donations to give another run at it (the majority was
          donated privately<br>
          FWIW). There&#39;s a risk of the mempool filling up again of
          course; hard to avoid<br>
          that.<br>
          <br>
          Right now of course it&#39;s really easy to double spend with the
          obvious<br>
          low-fee/high-fee method as the min relay fee keeps shifting.<br>
          <br>
          &gt; <a href=3D"https://mempool.space/tx/397dcbe4e95ec40616e3dfc4=
ff8ffa158d2e72020b7d11fc2be29d934d69138c" rel=3D"noreferrer" target=3D"_bla=
nk">https://mempool.space/tx/397dcbe4e95ec40616e3dfc4ff8ffa158d2e72020b7d11=
fc2be29d934d69138c</a><br>
          &gt; <br>
          &gt; The block it was claimed in seems to have been about an
          hour after the<br>
          &gt; default mempool filled up:<br>
          &gt; <br>
          &gt; <a href=3D"https://twitter.com/murchandamus/status/159227462=
1977477120" rel=3D"noreferrer" target=3D"_blank">https://twitter.com/murcha=
ndamus/status/1592274621977477120</a><br>
          &gt; <br>
          &gt; That block actually seems to have included two<br>
          &gt; <a href=3D"http://alice.btc.calendar.opentimestamps.org" rel=
=3D"noreferrer" target=3D"_blank">alice.btc.calendar.opentimestamps.org</a>
          txs, the other paying $7.88<br>
          &gt; (309sat/vb):<br>
          &gt; <br>
          &gt; <a href=3D"https://mempool.space/tx/ba9670109a6551458d5e1e23=
600c7bf2dc094894abdf59fe7aa020ccfead07cf" rel=3D"noreferrer" target=3D"_bla=
nk">https://mempool.space/tx/ba9670109a6551458d5e1e23600c7bf2dc094894abdf59=
fe7aa020ccfead07cf</a><br>
          <br>
          The second is because I turned down the full-rbf reward to
          more normal fee<br>
          levels. There&#39;s also another full-rbf double-spend from the
          Bob calendar, along<br>
          the same lines:
          7e76b351009326a574f3120164dbbe6d85e07e04a7bbdc40f0277fcb008d2cd2<=
br>
          <br>
          I double-spent the txin of the high fee tx that got mined. But
          I mistakenly had<br>
          RBF enabled in that double-spend, so while it propagated
          initially, I believe<br>
          it was replaced when something (someone?) rebroadcast the
          high-fee 397dcb tx.<br>
          <br>
          &gt; Timeline (utc) to me looks like:<br>
          &gt; <br>
          &gt;=C2=A0 - 13:12 - block 763148 is mined: last one that had a m=
in
          fee &lt; 1.5sat/vb<br>
          &gt;=C2=A0 - 13:33 -
          f503868c64d454c472859b793f3ee7cdc8f519c64f8b1748d8040cd8ce6dc6e1<=
br>
          &gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 is announced and pr=
opogates widely (1.2sat/vb)<br>
          &gt;=C2=A0 - 18:42 -
          746daab9bcc331be313818658b4a502bb4f3370a691fd90015fabcd7759e0944<=
br>
          &gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 is announced and pr=
opogates widely (1.2sat/vb)<br>
          &gt;=C2=A0 - 21:52 - ba967010 tx is announced and propogates
          widely, since<br>
          &gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 conflicting tx 746d=
aab9 has been removed from
          default<br>
          &gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 mempools<br>
          &gt;=C2=A0 - 21:53 - murch tweets about default mempool filling u=
p<br>
          &gt;=C2=A0 - 22:03 - 397dcbe4 tx is announced and propogates
          widely, since<br>
          &gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 conflicting tx f503=
868 has already been
          removed from default<br>
          &gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 mempools<br>
          <br>
          Is that 22:03 time for 397 from your node&#39;s logs? It was
          originally announced<br>
          hours earlier. From one of my full-rbf nodes:<br>
          <br>
          =C2=A0 =C2=A0 2022-11-14T14:08:37Z [mempool] replacing tx
          764867062b67fea61810c3858d587da83a28290545e882935a32285028084317
          with
          397dcbe4e95ec40616e3dfc4ff8ffa158d2e72020b7d11fc2be29d934d69138c
          for 0.00468 additional fees, -1 delta bytes<br>
          <br>
          &gt;=C2=A0 - 22:35 - block 763189 is mined<br>
          &gt;=C2=A0 - 22:39 - block 763190 is mined<br>
          &gt;=C2=A0 - 23:11 - block 763191 is mined<br>
          &gt;=C2=A0 - 23:17 - block 763192 is mined including 397dcbe4<br>
          &gt; <br>
          &gt; miningpool.observer reports both 397dcbe4 and ba967010 as
          missing in the<br>
          &gt; first three blocks, and gives similar mempool ages for
          those txs to what<br>
          &gt; my logs report:<br>
          &gt; <br>
          &gt;=C2=A0 =C2=A0<a href=3D"https://miningpool.observer/template-=
and-block/0000000000000000000436aba59d8430061e0e50592215f7f263bfb1073ccac7"=
 rel=3D"noreferrer" target=3D"_blank">https://miningpool.observer/template-=
and-block/0000000000000000000436aba59d8430061e0e50592215f7f263bfb1073ccac7<=
/a><br>
          &gt;=C2=A0 =C2=A0<a href=3D"https://miningpool.observer/template-=
and-block/00000000000000000005600404792bacfd8a164d2fe9843766afb2bfbd937309"=
 rel=3D"noreferrer" target=3D"_blank">https://miningpool.observer/template-=
and-block/00000000000000000005600404792bacfd8a164d2fe9843766afb2bfbd937309<=
/a><br>
          &gt;=C2=A0 =C2=A0<a href=3D"https://miningpool.observer/template-=
and-block/00000000000000000004a3073f58c9eae40f251ea7aeaeac870daeac4b238fd1"=
 rel=3D"noreferrer" target=3D"_blank">https://miningpool.observer/template-=
and-block/00000000000000000004a3073f58c9eae40f251ea7aeaeac870daeac4b238fd1<=
/a><br>
          &gt; <br>
          &gt; That presumably means those pools (AntPool twice and
          &quot;unknown&quot;) are<br>
          &gt; running with large mempools that didn&#39;t kept the earlier
          1.2sat/vb txs.<br>
          <br>
          To be clear, you think that AntPool and that other exchange is
          running with a<br>
          larger than normal max mempool size limit? You mean those
          miners *did* keep the<br>
          earlier 1.2sat/vb tx?<br>
          <br>
          &gt; The txs were mined by Foundry:<br>
          &gt; <br>
          &gt;=C2=A0 =C2=A0<a href=3D"https://miningpool.observer/template-=
and-block/00000000000000000001382a226aedac822de80309cca2bf1253b35d4f8144f5"=
 rel=3D"noreferrer" target=3D"_blank">https://miningpool.observer/template-=
and-block/00000000000000000001382a226aedac822de80309cca2bf1253b35d4f8144f5<=
/a><br>
          &gt; <br>
          &gt; This seems to be pretty good evidence that we currently
          don&#39;t have any<br>
          &gt; significant hashrate mining with fullrbf policies
          (&lt;0.5% if there was a<br>
          &gt; high fee replacement available prior to every block
          having been mined),<br>
          &gt; despite the bounty having been collected.<br>
          <br>
          Oh, we can put much lower bounds on that. I&#39;ve been running
          OTS calendars with<br>
          full-rbf replacements for a few months without clear evidence
          of a full-rbf<br>
          replacement.=C2=A0 While there was good reason to think some mine=
rs
          were mining<br>
          full-rbf before a few years back, they probably didn&#39;t bother
          to reapply their<br>
          patches each upgrade. `mempoolfullrbf=3D1` is much simpler to
          use.<br>
          <br>
          -- <br>
          <a href=3D"https://petertodd.org" rel=3D"noreferrer" target=3D"_b=
lank">https://petertodd.org</a>
          &#39;peter&#39;[:-1]@<a href=3D"http://petertodd.org" rel=3D"nore=
ferrer" target=3D"_blank">petertodd.org</a><br>
          _______________________________________________<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/bit=
coin-dev" rel=3D"noreferrer" target=3D"_blank">https://lists.linuxfoundatio=
n.org/mailman/listinfo/bitcoin-dev</a><br>
        </blockquote>
      </div>
    </blockquote>


</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>

--00000000000031d3cb05ef17a2d4--