Foundry’s BIP-110 Vote Tests Bitcoin’s Decentralization and Market Stability
Foundry Digital is asking its mining clients to vote on BIP-110, a proposal designed to curb blockchain spam. The scale is the story: Foundry controls roughly one-third of Bitcoin’s hashrate. My take: the result will offer a real-world test of decentralized governance, while potentially changing how traders judge Bitcoin’s stability.
The vote, announced Friday, concerns a temporary restriction on non-monetary blockchain data. Narrow technical issue? Not really. It reopens the argument over whether Bitcoin should serve as peer-to-peer money or a store of value. Then there is the broader vision: a network that supports other uses as well.
Foundry, based in Rochester, New York, will let clients use their computing power, or hashrate, to vote for or against Bitcoin Improvement Proposal 110. The proposed soft fork would remain compatible with older software while limiting the amount of non-monetary data allowed in transactions. Most new outputs would be capped at 34 bytes. OP_RETURN outputs would return to an 83-byte limit. Data pushes larger than 256 bytes would be rejected. Foundry told clients, “As miners, it’s important for you to have a voice and participate in the governance of the network.”
Foundry calls BIP-110 one of the “more actively debated proposals in Bitcoin right now.” Supporters want Bitcoin to operate more strictly as peer-to-peer money; they regard the extra data as needless bloat. Strategy founder Michael Saylor and Blockstream co-founder Adam Back disagree. Their objection is blunt: BIP-110 would elevate a policy preference into a consensus rule, potentially invalidating transactions even when users paid the required fees. I’ll be honest: that is much harder to dismiss than a generic argument about spam.
Michael Saylor and Adam Back give the dispute obvious market visibility. Still, the standard assumption that every protocol fight must become an immediate price event is only half right. Bitcoin has survived bitter internal fights before. This one matters if it damages confidence in BTC’s stability or weakens its appeal as a long-term store of value—especially if the vote becomes a referendum on who actually controls the network.
The mechanism is clean. Each account’s vote will be weighted according to its average hashrate over the 10 days from July 6 through July 15. Foundry will follow the majority of those weighted votes. Signaling is expected to continue until block 961,632 in early August.
The default vote is “No.” Foundry will signal “Yes” with all its blocks only if more than 51% of the participating hashrate supports the proposal. No response also counts as “No.” That matters. Abstention is therefore not neutral, and I would not be surprised if this rule influences the result as much as declared opposition.
Foundry’s clients collectively control about one-third of Bitcoin’s hashrate. That is enough to move the signaling numbers substantially, so shrugging off the result would be difficult. Analysts at BGeometrics have identified two pools—Foundry and Antpool—as the ones most likely to push daily signaling into a meaningful range.
Here is the awkward bit. A mining pool can give individual clients a vote and still retain enormous influence over which proposals ever gain traction. Most decentralization narratives skip that tension. They shouldn’t. An internal process may be democratic, yet a large portion of network power can remain concentrated among a small group of operators.
Does that prove Bitcoin is centralized? No. It does make the tidy claim that no large organization can sway the protocol much harder to defend. Investors who buy BTC partly because it operates outside governments and major institutions may care deeply about that distinction during economic or regulatory turmoil. I keep coming back to this: decentralization is not a switch that reads on or off.
BIP-110 raises a practical adoption question too. Tighter data limits could restrict activity beyond ordinary payments. Advocates of a narrower design consider that a feature. Others want developers to retain room for more complex experiments, including applications built indirectly on top of Bitcoin. Counter to the usual advice, more technical flexibility is not automatically better; it creates tradeoffs rather than erasing them.
The familiar labels are “pure money” and “programmable money.” Neither quite works. A more restrictive network may appeal to institutions that want Bitcoin to remain simple and predictable. They may also value resistance to change, which supports the digital gold thesis. A less restrictive network gives developers and companies more room to build, potentially attracting new users. It could also create stronger links with conventional finance. Either direction carries costs.
This vote will not decide Bitcoin’s future by itself. That sounds obvious, but market commentary often treats a single signaling window as a final verdict. It isn’t. Large investors and technology companies may nevertheless use the outcome to reassess the network. Sovereign wealth funds may put predictability first; developers may favor flexibility. Same count. Very different conclusions.
What this means
Foundry’s BIP-110 vote determines how the pool treats a proposed limit on blockchain data. It also offers an imperfect but useful view of Bitcoin governance when a contentious proposal reaches miners. Why does this matter? Because the mechanics are technical, but the fight is about power.
A strong “Yes” vote would support tighter limits and a version of Bitcoin centered mainly on peer-to-peer money. Some traders may read that as an efficiency or security improvement, strengthening the safe-haven argument. A “No” vote would leave more room for future applications. One camp calls it flexibility. The other calls it clutter. My read: neither description is neutral.
Traders should watch price and trading volume during the signaling period, although the vote may not trigger a sharp move. Most guides would stop at “watch for volatility.” That is too simple. Markets often ignore governance disputes until implementation appears probable; volatility becomes more likely if the fight rapidly changes how investors understand Bitcoin’s purpose.
Block 961,632, projected for early August, is the marker worth watching. By then, the mandatory signaling window should provide a clearer answer. Foundry’s combined result carries more weight than scattered remarks or individual miners’ stated preferences. Comments from Michael Saylor or Adam Back could still influence how investors interpret the outcome.
The lasting issue is trust. If a few mining pools can steer protocol changes, investors may question Bitcoin’s censorship resistance and independence. Yet if those pools faithfully carry their clients’ votes, supporters can cite the identical result as evidence that miners—not pool operators—make the decisions. Yes, those readings conflict. That is the point.
I suspect both camps will claim vindication. The count will show what miners chose. It will not settle the harder argument over what that choice says about Bitcoin.