Bitcoin

Adam Back

<p>Bitcoin has always carried a tension: keep the base layer clean and money-first, or leave room for other stuff people want to stick in blocks. BIP-110 is where that argument gets very real.</p>
<p>At a high level, the proposal attempts to limit patterns used to stash non-financial data on-chain. Think inscriptions and similar payloads that ride along in witness data. The question underneath is simple, but loaded: who gets to decide what belongs?</p>
<p>Miners? Full node operators? Wallets? Or the market, via fees? With signaling windows ticking and high-profile voices weighing in, it’s not just a technical change. It’s a governance stress test.</p>
<p>PointDetails What BIP-110 targets A proposed consensus change to curb certain non-transactional data patterns (e.g., inscriptions-like payloads) in the witness path, aiming to re-center blockspace on payments and financial settlement. Who decides in practice Full nodes ultimately enforce rules; miners signal and assemble blocks; wallets and users create demand. Social consent across all three makes or breaks activation. Activation threshold and timing Public trackers frame a 55% miner signaling bar. As of July 15, signaling sat near 1% with an early-August lock-in window discussed in reports. Main risks Chain split if coordination fails, censorship concerns, unexpected fee market effects, and breakage for apps relying on the targeted data patterns. Economic trade-off Less non-financial data could mean more capacity for payments but possibly lower near-term miner fees tied to inscription surges. Alternatives to a fork Mempool and relay policy changes, wallet defaults, and market incentives can push behavior without touching consensus.</p>
<h2 id="what-bip-110-actually-tries-to-change">What BIP-110 actually tries to change</h2>
<blockquote>
 <p>Editor's note: Q1 and Q2 were a reminder that Bitcoin’s fee market has a mind of its own. I watched desks quietly rework batching after a couple of messy <a href="https://cryptodaily.co.uk/2026/07/bitcoin-drops-3-as-us-iran-hostilities-escalate" rel="noopener noreferrer nofollow">mempool spikes</a>, while miners reran revenue models that had leaned on inscription surges last year. The BIP-110 chatter came up in every call with exchanges I track — not about politics, but about operational risk if a fork window gets choppy. What stood out: even miners who dislike non-financial data aren’t eager to roll the dice without clear economic node support. That hesitation feels like the real signal right now. — Idris Calloway</p>
</blockquote>
<p>Strip the noise and you get this: BIP-110 is pitched as a way to trim back non-financial data that has piggybacked on Bitcoin’s witness space since Taproot-era scripting flexibility made it easier to do so. The details live in how you define and detect those patterns, and that’s where it gets tricky. If you’re too narrow, people route around it in a week. If you’re too broad, you risk breaking legitimate use cases or, worse, edge-case wallet behavior.</p>
<p>The intent is not to delete history that’s already there. It’s about what gets accepted moving forward under new rules. Supporters argue the base layer should remain monetary plumbing, not a general storage layer. Critics see a slippery slope and warn about enshrining a political or cultural definition of what counts as “financial.”</p>
<p>There’s a cultural note here. Bitcoin has always relied on minimal rules with maximal predictability. The more you start drawing lines around acceptable data categories, the more interpretation you invite. That’s the governance tension people feel, even if they don’t say it in those words.</p>
<h2 id="activation-mechanics-thresholds-and-the-august-clock">Activation mechanics, thresholds, and the August clock</h2>
<p>Let’s talk about where signaling stands, because the calendar matters. The official BIP-110 monitor shows miners signaling at roughly 1.13% for the current difficulty-adjustment period as of a July 15 update, with 6 signaling blocks out of 529 tracked and a long way to go before a 55% threshold (<a href="https://bip110.org/monitor" rel="noopener noreferrer nofollow">BIP-110 (official monitor)</a>). If you zoom out, this tracks with earlier reporting. CoinDesk noted the current signaling period and said miner support was basically at zero around July 12–13, while pointing to a voluntary lock-in deadline expected in early August (<a href="https://www.coindesk.com/tech/2026/07/12/bitcoin-s-bip-110-fork-deadline-nears-with-miner-support-at-zero" rel="noopener noreferrer nofollow">CoinDesk</a>).</p>
<p>Looking back to late June, Bitcoin.com tallied signaling near 0.31% of hashrate, roughly 5 EH/s out of about 940 EH/s back then, and highlighted a mandatory-signaling window beginning around block 961,632, projected August 7 (<a href="https://news.bitcoin.com/bip-110-pushes-bitcoin-toward-august-fork-deadline-with-only-5-eh-s-signaling/" rel="noopener noreferrer nofollow">Bitcoin.com</a>). Timelines wiggle with hashrate, so treat dates as rough, but the point stands: unless something changes fast, miner support looks thin.</p>
<p>Separately, the current period bounds cited by CoinDesk were blocks 957,600–959,615, and progress during that window appeared minimal (<a href="https://www.coindesk.com/tech/2026/07/12/bitcoin-s-bip-110-fork-deadline-nears-with-miner-support-at-zero" rel="noopener noreferrer nofollow">CoinDesk</a>). If your mental model is “miners decide,” this weak signaling should make you pause. There’s clearly not yet a broad coalition behind it.</p>
<h2 id="so-who-should-control-non-financial-data-on-bitcoin">So who should control non-financial data on Bitcoin?</h2>
<p>Control sounds top-down. Bitcoin isn’t built that way. Here’s a more accurate framing: what levers exist, who holds them, and what are the trade-offs if they pull?</p>
<h3 id="full-nodes-set-the-hard-boundary">Full nodes set the hard boundary</h3>
<p>Consensus rules live in node software. If a rule is changed there and a supermajority of economy-facing nodes upgrade, those nodes will reject non-compliant blocks. That’s real power. It’s also why people are cautious about turning cultural preferences into rules. You need overwhelming alignment or you risk a persistent fork.</p>
<h3 id="miners-curate-the-near-term-flow">Miners curate the near-term flow</h3>
<p>Miners choose which mempool transactions to include. They respond to fees, risk, and policy. If they collectively deprioritize certain patterns, that’s a de facto filter. But unless there’s a consensus rule change, any miner can still include whatever is valid by the old rules and get paid. Coordination is fragile here.</p>
<h3 id="wallets-and-services-create-the-demand">Wallets and services create the demand</h3>
<p>Wallets set defaults that shape the network. If wallet developers nudge users away from data-heavy patterns, outcomes change fast without a fork. Same for exchanges and merchant processors that set what they accept, how they batch, and what scripts they use.</p>
<h3 id="the-fee-market-is-the-referee">The fee market is the referee</h3>
<p>If blockspace is expensive, data that doesn’t pay for itself gets crowded out. That’s the simple story. The complication is that inscriptions did pay during peak hype. They bought room at the table. If you think that’s a problem, you’re making an argument that price alone shouldn’t decide. That’s a philosophical shift.</p>
<h2 id="fees-miner-incentives-and-the-blockspace-economy">Fees, miner incentives, and the blockspace economy</h2>
<p>Miners live on two revenue lines: subsidy and fees. The subsidy trends to zero. Fees matter more every cycle. When inscriptions got hot, fees spiked. Some miners quietly welcomed it. Others hated the churn and political risk. You can hold both thoughts: the money was real, and the long-term optics were messy.</p>
<p>What happens if BIP-110 lands and successfully cuts out a chunk of non-financial data? You might get:</p>
<ul>
 <li>More space for standard payments and exchange consolidations at lower median fees, at least initially.</li>
 <li>A likely drop in inscription-driven surges. Good for predictability, potentially worse for miner fee peaks.</li>
 <li>Migration of data demand to L2s or alt-chains, or creative workarounds that test the new line.</li>
</ul>
<p>That last point matters. Demand doesn’t vanish. It moves. If you’re an <a href="https://cryptodaily.co.uk/2026/07/empery-digital-sells-1400-btc-ai-pivot" rel="noopener noreferrer nofollow">exchange treasurer planning fee budgets</a>, or a miner modeling revenue, those flow shifts are the difference between a good quarter and a tight one.</p>
<h2 id="precedent-censorship-fears-and-open-source-norms">Precedent, censorship fears, and open-source norms</h2>
<p>Here’s the emotional center of the debate. The minute Bitcoin starts saying “this data good, that data bad,” it’s accused of content policy. Defenders reply it’s not about content, it’s about format and cost. True, but the optics are still loaded. And the social layer remembers precedents.</p>
<p>Mid-July brought public opposition from well-known figures. Michael Saylor said on X there are “110 things more dangerous to Bitcoin than spam,” arguing BIP-110 sets a risky precedent, with reports the same weekend noting Adam Back also voiced objections (<a href="https://www.coindesk.com/tech/2026/07/12/bitcoin-s-bip-110-fork-deadline-nears-with-miner-support-at-zero" rel="noopener noreferrer nofollow">CoinDesk (reporting Saylor &amp; Back posts)</a>).</p>
<blockquote>
 <p>Once you bless a rule that filters a class of data, you create a template. The next filter might be easier to sell. That’s the slope critics point at.</p>
</blockquote>
<p>This isn’t an argument-ender. It’s a reminder that Bitcoin’s social contract is part code, part custom. Mess with custom too much, and even the best code runs into human limits.</p>
<h2 id="could-policy-level-fixes-beat-a-hard-rule">Could policy-level fixes beat a hard rule?</h2>
<p>Plenty of engineers would rather exhaust policy levers before touching consensus. Policy means mempool and relay rules that are not consensus-critical. They can throttle or deprioritize transactions exhibiting patterns the network would rather not encourage, without making old blocks invalid. A few angles here:</p>
<ul>
 <li>Relay limits and package rules. Nodes choose what to forward. Tightening those policies changes what tends to confirm.</li>
 <li>Wallet defaults. If popular wallets don’t generate disfavored patterns, demand for blockspace tilts.</li>
 <li>Miner templates. Pools can enforce templates that exclude certain structures, a softer layer of coordination that can be revised without forks.</li>
</ul>
<p>Pro tip: If you run infra, keep a staging node on testnet or signet mirroring your prod config. Trial new policy sets for a week before flipping anything in production. It’s the difference between a smooth change and a weekend of surprises.</p>
<p>Policy doesn’t give you guarantees. A single miner with a different view can still include transactions that others ignore, and if fees are good enough, they might. But when most of the network shifts defaults, behavior often follows.</p>
<h2 id="what-changes-for-wallets-miners-and-exchanges-if-bip-110-locks-in">What changes for wallets, miners, and exchanges if BIP-110 locks in</h2>
<h3 id="wallet-developers">Wallet developers</h3>
<ul>
 <li>Audit script templates and signing flows. If your stack ever relied on large witness payloads or exotic script paths, run regression tests.</li>
 <li>Revisit fee estimation. Less competition from data-heavy transactions could change mempool shape and confirmation targets.</li>
 <li>Communicate early. If certain features might break or require updates, flag it in-app with clear options.</li>
</ul>
<h3 id="mining-pools-and-solo-miners">Mining pools and solo miners</h3>
<ul>
 <li>Update templates and transaction selection logic to avoid rule breaks the second the fork activates.</li>
 <li>Model fee sensitivity. If data-driven spikes fade, hedge exposure to fee dry spells. Consider smoothing via longer payout windows.</li>
 <li>Coordinate messaging. Unclear pool policies create arbitrage and friction with clients.</li>
</ul>
<h3 id="exchanges-and-custodians">Exchanges and custodians</h3>
<ul>
 <li>Batching still matters. You may get more predictable fees. Keep batching aggressive, but monitor change output policies.</li>
 <li>Watch for chain reorg risk during activation windows. Boost confirmations temporarily if uncertainty rises.</li>
 <li>Compliance teams should review on-chain data exposure policies. Even debates like this can trigger internal audits or policy updates.</li>
</ul>
<h3 id="mistakes-to-avoid">Mistakes to avoid</h3>
<ul>
 <li>Assuming “miners will sort it out.” Without broad node upgrades, miner signaling doesn’t bind the economy.</li>
 <li>Shipping last-minute patches during the activation window. Freeze risky changes, stage them early, or wait until the dust settles.</li>
 <li>Over-promising on fee relief. Markets adapt. If demand migrates to other patterns, pressure could return.</li>
</ul>
<p>Risk note: Any consensus change carries non-zero split risk. If you move funds during the activation window, add confirmations and keep an eye on status dashboards.</p>
<h2 id="how-to-follow-signaling-and-stay-prepared">How to follow signaling and stay prepared</h2>
<p>You don’t need to sit on X all day. Build a simple checklist and stick to it.</p>
<ul>
 <li>Check the official BIP-110 monitor at least daily for real progress toward the 55% bar (<a href="https://bip110.org/monitor" rel="noopener noreferrer nofollow">BIP-110 (official monitor)</a>).</li>
 <li>Read pool announcements and miner dashboards. If a major pool flips on, others may follow with short lag.</li>
 <li>Follow reputable reporting for period boundaries and activation windows, including projected block heights and any last-minute changes (<a href="https://www.coindesk.com/tech/2026/07/12/bitcoin-s-bip-110-fork-deadline-nears-with-miner-support-at-zero" rel="noopener noreferrer nofollow">CoinDesk</a>, <a href="https://news.bitcoin.com/bip-110-pushes-bitcoin-toward-august-fork-deadline-with-only-5-eh-s-signaling/" rel="noopener noreferrer nofollow">Bitcoin.com</a>).</li>
 <li>Keep one node on the latest release candidates for early warnings. If something breaks in staging, you want to find it first, not your customers.</li>
 <li>Document a rollback plan. If a fork stutters, you don’t want to debate procedures in a war room.</li>
</ul>
<p>If you want deeper coverage as the window approaches, we’re tracking it closely at <a href="https://cryptodaily.co.uk" rel="noopener noreferrer nofollow">Crypto Daily</a> without the hype.</p>
<h2 id="frequently-asked-questions">Frequently Asked Questions</h2>
<h3 id="does-bip-110-ban-ordinals-or-inscriptions">Does BIP-110 “ban” Ordinals or inscriptions?</h3>
<p>It aims to limit certain data-heavy patterns often used by those projects. The effect depends on the exact rule language and how quickly devs find workarounds. It’s safer to say it could shrink their room at the base layer rather than erase them completely.</p>
<h3 id="what-happens-if-miners-signal-but-node-operators-don-t-upgrade">What happens if miners signal but node operators don’t upgrade?</h3>
<p>Miners can’t force a rule onto nodes that don’t run it. If blocks are mined that rely on the new rules but a big chunk of the economy still enforces the old ones, you risk orphaned blocks or a split. Broad node alignment is essential.</p>
<h3 id="is-a-55-signaling-threshold-enough-for-a-safe-activation">Is a 55% signaling threshold enough for a safe activation?</h3>
<p>Threshold choice is a social decision as much as a technical one. Even hitting 55% doesn’t guarantee safety if large economic nodes, exchanges, and wallets aren’t on board. Watch for alignment across the ecosystem, not just the headline number.</p>
<h3 id="could-mempool-policy-changes-solve-this-without-a-fork">Could mempool policy changes solve this without a fork?</h3>
<p>They could go a long way. Relay and template policies can strongly discourage targeted patterns without making old blocks invalid. The trade-off is that any miner can still include them if the transactions are otherwise valid, so results may be uneven.</p>
<h3 id="will-this-lower-my-transaction-fees">Will this lower my transaction fees?</h3>
<p>Maybe, maybe not. If non-financial data gets crowded out, pressure on fees could ease. But demand shifts fast. New patterns or L2 traffic can soak up space. Treat any promised fee relief as temporary.</p>
<h3 id="what-s-the-realistic-timeline-right-now">What’s the realistic timeline right now?</h3>
<p>Public trackers show signaling still around the low single digits in mid-July. Reports have flagged an early-August window and a mandatory-signaling phase around block 961,632. Unless the pace changes, lock-in looks uncertain.</p>
<h3 id="how-can-i-tell-if-my-wallet-or-app-will-be-affected">How can I tell if my wallet or app will be affected?</h3>
<p>Scan your transaction builder. If you’ve been relying on large witness payloads or scripts designed to carry arbitrary data, set up a test environment and run through your flows under the proposed rules. If you’re a simple UTXO wallet with standard scripts, impact should be minimal.</p>
<p>Disclaimer: This article is provided for informational purposes only. It is not offered or intended to be used as legal, tax, investment, financial, or other advice.</p>

Bitcoin BIP-110 Explained: Who Should Control Non-Financial Data on the Network?

Table of Contents

Crypto Daily™

Other articles published on Jul 15, 2026

Join our free newsletter for daily crypto updates!