BitVM: The largest Disprove tx too large to be included in a block under default Bitcoin Core settings
Hi there,
We, the Babylon team, have encountered a practical issue with the largest Disprove tx size that may impact the usability of the BitVM bridge design in real-world deployments.
Context
- The Assert transaction in our setup contains 378 assertions.
- Through analysis, we found that the largest Disprove tx corresponds to assertion index 372.
- We’re simulating a case where this assertion is invalid and must be disproved on-chain.
The Problem
The resulting Disprove tx is 3,996,294 weight units, but cannot be mined under default Bitcoin Core settings due to two key constraints:
Before Bitcoin Core 29.0
- Default
blockmaxweightisMAX_BLOCK_WEIGHT - 4000 = 3,996,000, which is already too small for this Disprove tx. - Many miners are still on versions < 29.0, so this limitation is highly relevant today.
Starting from Bitcoin Core 29.0
blockmaxweightnow defaults toMAX_BLOCK_WEIGHT, which looks promising.- However, a new flag
blockreservedweight=8000is introduced, reserving 8000 weight units for fixed block overhead (header, tx count, coinbase). - This further reduces the space available for normal transactions, again making the Disprove tx inclusion impossible in reality.
Impact
Unless miners override defaults, this tx will not be accepted into blocks, making BitVM bridges unusable in worst-case assertion scenarios.
About this issue
- Original URL
- State: closed
- Created a year ago
- Reactions: 2
- Comments: 15 (15 by maintainers)
Great work, @manishbista28!
I’ve verified that your patch brings the largest disprove tx weight down from 3,996,294 to 3,954,000. With this change, we no longer need to adjust
-blockreservedweightfor inclusion, only the non-standard tx flag remains. That’s a solid improvement 👏 !BTW, the number looks good to include the largest disprove tx at first glance. I’ll update our dep to your patch to double check it can be included into a block on regtest using the default settings. Will report back later
After including witness, I got number fairly close to yours. Yes – this is something I will have to fix. Thank you for pointing this out.