# Package aware Fee estimator post cluster mempool

**URL:** <https://delvingbitcoin.org/t/package-aware-fee-estimator-post-cluster-mempool/312>\
**Category:** Implementation\
**Created:** [December 20, 2023, 9:33pm UTC](https://delvingbitcoin.org/t/package-aware-fee-estimator-post-cluster-mempool/312 "2023-12-20T21:33:06Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![ismaelsadeeq](https://delvingbitcoin.org/user_avatar/delvingbitcoin.org/ismaelsadeeq/32/151_2.png) [@ismaelsadeeq](https://delvingbitcoin.org/u/ismaelsadeeq)\
**Post date:** [December 24, 2023, 1:18pm UTC](https://delvingbitcoin.org/t/package-aware-fee-estimator-post-cluster-mempool/312/7 "2023-12-24T13:18:40Z")

</div>

> I don’t think we need to cluster/linearize/chunk the received block; the transactions in the block can be looked up one by one in the mempool to find their chunk feerate?

Yes, not even CTxMempool but the fee estimator Internal MapMempoolTxs.

> Do we bump the count back up to however long P has been sitting in the mempool?

I am assuming For each chunk, the time-in mempool to be the time of entry of the sponsor of the chunk (which should be the youngest transaction in the chunk) - the block height the chunk was mined.

I the case you mentioned the block height P entered the mempool - block height P was mined.

---

_[View the full topic](https://delvingbitcoin.org/t/package-aware-fee-estimator-post-cluster-mempool/312)._
