Analyzing Mining Pool Behavior to Address Bitcoin Core's Double Coinbase Reservation Issue

Implementation
7

Can you clarify F2Pool’s min and max coinbase weights? In the table above the min is larger than max.

This inconsistency is due to a mix-up when compiling the data. Also, I meant the minimum block weight coinbase weight, not the minimum coinbase weight. I’ve separated the coinbase weight stats from the block weight stats and update the coinbase chart.

  • For block 779729 with the max block weight of 3,998,554, a coinbase weight of ‎1588 WU and 332 WU for header+tx_count leaves me with a default of 3,996,634 WU. That seems to be an odd number to use as a custom -blockmaxweight (and only possible with patches to Bitcoin Core).

If you have the data, it might be interesting to calculate block weight - coinbase weight - header weight for the F2Pool blocks to get a better feeling about the weight they reserve.

I think we are a certain that F2Pool is using a patch of Bitcoin Core after mining: bugfix: Fix duplicate coinbase tx weight reservation by ismaelsadeeq · Pull Request #31384 · bitcoin/bitcoin · GitHub

However, it would be useful to review the data for confirmation.

1 Like