Posted by LearnBitcoin.com
Nov 12, 2026/14:23 UTC
Analysis of coinbase transaction sizes on Bitmain hardware reveals significant changes over time, particularly in relation to firmware updates. In earlier years, such as 2014 and 2017, typical P2Pool coinbase transactions were considerably larger, often around 13 kB and later about 4 kB, with the vast majority exceeding 750 bytes or even 2.25 kB. These transaction sizes far surpass the current limitations observed on stock S21 models, despite earlier Antminer units being able to handle them. This change is not attributed to hardware constraints themselves, but rather to limitations introduced by newer firmware versions.
Firmware differences play a crucial role in determining capacity. Braiins firmware reportedly supports arbitrary coinbase sizes on the same hardware, though this capability may vary across different firmware versions and has not been universally tested. Notably, the S21 model allows for coinbases three times larger than those accepted by the S19, indicating that these limits have shifted at least once with firmware updates. Modifying Bitmain's firmware is widely regarded as more challenging than altering Bitcoin’s consensus rules, which poses practical obstacles for users seeking greater flexibility.
The rationale behind the imposed coinbase size limit remains unclear. It is uncertain whether the restriction stems from technical factors, such as fixed buffer sizes that never required enlargement, or if it was the result of a deliberate engineering decision. Understanding this motivation is essential for future development and compatibility planning.
In adapting to these constraints, especially when considering implementations like p2poolv2, the maximum number of outputs may need to be reduced further, likely to around 16, to ensure compatibility with all participating machines. An additional complexity arises from DATUM’s workaround, which assigns coinbase transactions tailored to the maximum size each machine can process. This raises questions about sharechain operations: specifically, whether it is feasible to individualize payouts per machine, or if the necessity to agree on a single payout set effectively restricts the entire pool to the capabilities of its least capable hardware.
TLDR
We’ll email you summaries of the latest discussions from high signal bitcoin sources, like bitcoin-dev, lightning-dev, and Delving Bitcoin.
We'd love to hear your feedback on this project.
Give Feedback