# Great Consensus Cleanup Revival

**URL:** <https://delvingbitcoin.org/t/great-consensus-cleanup-revival/710>\
**Category:** Protocol Design\
**Created:** [March 24, 2024, 5:29pm UTC](https://delvingbitcoin.org/t/great-consensus-cleanup-revival/710 "2024-03-24T17:29:42Z")\
**Posts on this page:** 1\
**Showing post:** 89

<div class="post-metadata">

**Author:** ![sjors](https://delvingbitcoin.org/user_avatar/delvingbitcoin.org/sjors/32/59_2.png) [@sjors](https://delvingbitcoin.org/u/sjors)\
**Post date:** [December 4, 2025, 2:31pm UTC](https://delvingbitcoin.org/t/great-consensus-cleanup-revival/710/89 "2025-12-04T14:31:13Z")

</div>

> [@ajtowns](#):
>
> a cost of between 15 to 31 bytes of additional coinbase data

Keep in mind that Bitcoin Core block templates reserve 8000 weight units by default for coinbase (and header). Afaik miners rarely push this to the limit (`-blockreservedweight` has a minimum of 2000, but patching can of course take it lower).

Ocean Pool uses extra large coinbases and Datum users are instructed ( [GitHub - OCEAN-xyz/datum\_gateway: Decentralized Alternative Templates for Universal Mining](https://github.com/OCEAN-xyz/datum_gateway?tab=readme-ov-file#node-configuration) ) to set `blockmaxweight=3985000` which means 15 kWu is reserved. In practice their coinbase transactions ( [mempool - Bitcoin Explorer](https://mempool.space/nl/mining/pool/ocean) ) vary wildly in size, e.g. recently I saw one that was 3 kWu and another 9.4.

Perhaps in the future miners are going to be more concerned about squeezing every last byte out of a block, but at the moment 15 to 31 extra bytes would just eat into the existing safety margin and have no revenue effect.

---

_[View the full topic](https://delvingbitcoin.org/t/great-consensus-cleanup-revival/710)._
