Recently, community discussion around BIP-110 has been intensifying. The proposal suggests temporarily imposing limits on the size of certain data fields at the consensus layer to correct incentive distortions caused by standardized support for arbitrary data, and to refocus priorities on enhancing Bitcoin’s functionality as money.
We believe that this very discussion underscores the strength of Bitcoin as a decentralized consensus system. For over a decade, the Bitcoin network has consistently allowed diverse ideologies and technical paths to coexist—from the SegWit2x controversy in 2017 to the subsequent Bitcoin Cash fork—demonstrating its ability to evolve even amid disagreement.
Currently, the node signal ratio for BIP-110 is on an upward trend. According to public data:
- January 25, 2026: 2.98% (729 / 24,482 nodes)
- February 23, 2026: 7.99% (1995 / 24,981 nodes)
BIP-110 Ready Nodes
This represents an increase of approximately 5% within a month. It remains uncertain whether the proposal will ultimately reach the activation threshold, and continued monitoring is required.
In this context, we believe that products and services within the Bitcoin ecosystem should be technically prepared for multiple possible outcomes, rather than making judgments based on emotional positions or predetermined results.
The original design intent and role of Fractal
One of the core design goals of Fractal Bitcoin is to provide an environment capable of supporting more complex states and data expressions, without altering Bitcoin's mainnet consensus rules.
If the mainnet imposes stricter limitations on certain data types at the consensus layer in the future, Fractal can serve as a technically compatible extension layer, offering an alternative path for asset state continuity.
As we previously discussed:
For Ordinals, censorship on Bitcoin has always been a concrete and clear risk. If Bitcoin maintainers one day take the position that “Ordinals are spam and should be blocked in future versions,” Fractal Bitcoin can preserve all Bitcoin mainnet inscriptions via mirroring, with an additional data overhead of just 1/38 the size of the original.
It needs to be emphasized that:
- Fractal is not a fork alternative
- It is also not an adversarial response to the mainnet decision.
- It also does not preset any specific governance outcome.
Its role is more like a "buffer layer," providing continuity for assets across different consensus evolution stages.
Possible scenarios for "temporary restrictions"
BIP-110 is described as a one-year temporary restriction.
In this scenario, if the relevant assets are constrained on the mainnet, Fractal can serve as a temporary hosting environment; if the restrictions are lifted after one year, the assets can return to the mainnet.
The specific technical implementation path still offers room for further research and optimization, but the principles are clear:
- Do not disrupt mainnet consensus
- No mandatory migration
- Do not create market panic
- Provide only optional alternatives
Our position
As ecosystem participants, we respect the final consensus outcome of Bitcoin.
Regardless of the direction of BIP-110, the healthy development of the ecosystem should be built on technical preparedness and rational discussion, not on opposition.
The existence of fractals is not to create division, but to provide a technical buffer when divisions arise.