# Stats on compact block reconstructions

**URL:** <https://delvingbitcoin.org/t/stats-on-compact-block-reconstructions/1052>\
**Category:** Protocol Design\
**Created:** [August 2, 2024, 11:58am UTC](https://delvingbitcoin.org/t/stats-on-compact-block-reconstructions/1052 "2024-08-02T11:58:02Z")\
**Posts on this page:** 1\
**Showing post:** 21

<div class="post-metadata">

**Author:** ![0xB10C](https://delvingbitcoin.org/user_avatar/delvingbitcoin.org/0xb10c/32/15_2.png) [@0xB10C](https://delvingbitcoin.org/u/0xB10C)\
**Post date:** [February 4, 2025, 2:03pm UTC](https://delvingbitcoin.org/t/stats-on-compact-block-reconstructions/1052/21 "2025-02-04T14:03:58Z")

</div>

> [@ajtowns](#):
>
> One thing that could be worth looking into is doing a better job of populating prefilledtxns – ie, “I’m pretty sure my peers don’t know about these txs in the block, so I’ll send them straight away”.

I’ve started recording the contents of inbound and outbound `getblocktxn` messages a week ago. This should allow for some insights into “are peers often missing the same transactions?” and “can we pre-fill the transactions we had to request our self?”. I haven’t taken a closer look at the data yet.

Also, I’ve changed one of my nodes to run with `blockreconstructionextratxn=10000` and updated two nodes to a `master` that includes [p2p: track and use all potential peers for orphan resolution #31397](https://github.com/bitcoin/bitcoin/pull/31397). Probably need to wait until the mempool fills up again to see the effects of this.

---

_[View the full topic](https://delvingbitcoin.org/t/stats-on-compact-block-reconstructions/1052)._
