Exchange Ranking
Top Exchanges
24h Volume Ranking
Popularity Ranking
Exchange BTC Balance
Proof of Reserves
Decentralized Exchanges
Funding Rate
Funding Heatmap
Liquidation Data
Max Pain
Long/Short Ratio
Whale L/S Ratio
Binance/Okex/Huobi L/S
Bitfinex Margin L/S
ETF Tracker
Solana ETF
XRP ETF
Hong Kong ETF
Bitcoin Treasuries
Crypto Reversal
Ethereum Reserves
HyperLiquid Wallet Analysis
Hyperliquid Whale Watch
Large Transactions
On-chain Movement
Bitcoin ROI
Stablecoin Market Cap
Options Analysis
News
Articles
Economic Calendar
Features
Wallet
Contract Calculator
Security
Collections
Watchlist
Following
BTC Adam Back and Michael Saylor oppose the BIP110 proposal
Blockstream co-founder Adam Back and Strategy founder Michael Saylor have publicly opposed the Bitcoin improvement proposal BIP110, which is a temporary soft fork for Bitcoin. A report on July 12 summarized their comments. Back said the plan attempts to regulate transactions that other users choose to send, and believes this approach conflicts with Bitcoin's decentralized, permission-free design philosophy.
Back also warned that if supporters enforce rules without broad consensus, they could create a separate chain. Saylor expressed similar views in his public statement. "BIP 110 transforms the spam transaction controversy into a consensus change," he said, which would reject certain transactions currently accepted by Bitcoin. Saylor called the precedent "extremely dangerous" and believes developers should focus on the larger threat.
What will BIP 110 change
The official BIP 110 specification calls it a "data reduction temporary soft fork." It will implement additional consensus rules in about a year. These rules will restrict large field data, certain Taproot features, and multiple methods used to embed images or other files in transactions. The proposal limits OP_RETURN output to 83 bytes and limits multiple payloads to 256 bytes.
The proposal says the restrictions will reduce the amount of data stored on Bitcoin and allow the network to focus on currency functions. It exempts UTXOs created before activation, so existing output can still be used under old rules. Proponents believe the measure will reduce the storage needs of node operators. Critics say paying users should decide for themselves how to use block space.
Luke Dashjr continues to support the proposal
Bitcoin developer Luke Dashjr still supports BIP 110. On July 6, it was reported that he refused to withdraw the proposal and said that "it was too late to cancel BIP 110." He believes that uses such as Ordinals and Runes write non-financial data to Bitcoin, increasing the cost of long-term storage and providing blockchain services.
Previous reports mentioned that Back had responded to supporters saying that discussion channels had blocked the proposal. Back refuted the claim and noted that many participants had reviewed the plan. The report showed that node support was low at that time and did not receive clear support from major mining pools.
Miner support rate is well below threshold
BIP110 adopts a modified activation process. Miners need to express support in 1109 of the 2016 blocks (or 55%) to lock in the proposal. The specification requires mandatory signaling before Block 963,648 and activation in Block 965,664 (expected around September 1, 2026). The interim rules will then take effect for about a year.
The current support rate is well below this level. A report released on July 12 stated that miners 'signal markers were zero during the active period and never exceeded about 1% in the early stages. No major mining pool supports the proposal. Without widespread adoption, nodes executing BIP 110 may follow a few chains, while other nodes continue to accept existing transaction rules.
Exchanges, wallets, miners and node operators now face an August planning window. They must decide which software and rules to support before mandatory signaling begins. Market participants can track centralized exchange reserves through tools, but these data do not measure Bitcoin consensus support. The final result of BIP 110 depends on software adoption, miners 'signal markings, and user choices.
