Casual research on running `mempoolfullrbf`

valuedmammal · August 31, 2024, 1:28pm

Murch might be referring to the research on block reconstruction which I agree is pretty remarkable

Comment by 0xB10C - policy: enable full-rbf by default

bitcoin:master ← 1440000bytes:2023-07-enable-full-rbf

> I shared my concerns with another bitcoiner who likes to monitor network healt…h, they replicated, and got similar results (which I presume they'll share eventually). Correct, I too found enabling `mempoolfullrbf` to be helpful for compact block reconstruction without requesting transactions. By analyzing compact block reconstructions in the debug.logs (with `debug=cmpctblock` enabled) of my [monitoring nodes](https://public.peer.observer/), I noticed that many block reconstructions need an additional round-trip to fetch unknown transactions. While this situation has slightly improved over the last weeks (~50% -> 70+%) as mempool activity died down, this still clearly shows a divergence in policy. I suspected that the divergence might originate from [nearly all pools](https://github.com/bitcoin/bitcoin/pull/28132#issuecomment-2059120917) mining with mempoolfullrbf. I enabled `-mempoolfullrbf=1` on the monitoring node/host `erin` on 2024-07-26. Since then, this node needed request transactions during significantly fewer blocks reconstructions than the other nodes. Concept ACK ![image](https://github.com/user-attachments/assets/a1d62976-e727-4ad9-a324-669970de8730) <sub>(note that while 75% or so might show up as light green here, doesn't necessarily mean that 75% is "good". Ideally, we want this to be close to 100% of blocks reconstructions needing no transaction requests)</sub>