BIP-110 mandatory signaling explained guides node operators in assessing split risk and next steps.
BIP-110 mandatory signaling explained in plain terms: what it is, why it matters now, and how to judge your risk. Bitcoin just entered a user-activated soft fork push with very low miner support. Use this guide to understand the rules, the four-week window, the chance of a split, and simple steps to protect your funds.
Bitcoin hit block 961,632 and started a mandatory signaling window for BIP-110. The proposal aims to limit non-financial data on-chain for a time. Miner support is under 3%, far below the 55% target. Supporters want a user-activated soft fork, where nodes enforce the rule and reject blocks that do not signal. Critics, including Michael Saylor and Adam Back, say this move is a bad idea. The next four weeks could be calm, or they could bring a messy split. Your risk depends on how you use Bitcoin, how fast you need to move funds, and who controls the software you rely on.
BIP-110 mandatory signaling explained: what just changed
The new rule push and who enforces it
BIP-110 changes the rules that full nodes use to accept blocks. Users who upgrade to BIP-110 code will only accept blocks that include a signaling bit. If a miner does not signal, these nodes reject that block. This is a user-activated soft fork. It leans on node operators, not miners, to press change.
The window and the target
The signaling window runs from block 961,632 to about 965,664, which should take around four weeks. The proposal watchers set 55% signaling as the success line. Right now, signaling is about 2.5%. That is far from the goal.
Why the proposal exists
BIP-110 is meant to curb non-financial data on Bitcoin for a temporary period. Supporters argue this reduces spam and keeps block space open for money use. Opponents argue the market should decide how block space is used, not a new rule pushed by a small group of users.
How signaling works and why support matters
Miner signaling
Miners can set a bit in the blocks they find to show support. If enough miners signal, the new rule can lock in. If support stays low, the new rule does not gain miner backing within the window.
Node enforcement
If users run BIP-110 code, their nodes will reject non-signaling blocks. If only a small slice of users do this, those nodes will diverge from the main chain that most miners build. That creates two networks:
The main chain: backed by almost all hash power and most capital.
The minority chain: made of BIP-110 enforcing nodes and any miners who decide to follow them.
What could happen next
The minority chain grows if more nodes switch to BIP-110 and if some miners follow.
The minority chain stalls if not enough miners build on it.
The main chain keeps going if miners and most users ignore the new rule.
Who is for and against the change
Public opposition
Michael Saylor and Adam Back both said they oppose BIP-110. Many miners also do not signal. That shows weak support among hash power and key public voices.
Supporters’ view
BIP-110 backers point to 2017. Users pushed SegWit activation via BIP-148. They argue user choice can move miners. They believe node operators can set the norm by choosing what blocks to accept.
Risk map: what different users should expect
If you hold bitcoin and move it rarely
Your main risks are service delays and price swings. If a split happens, some wallets and exchanges may pause deposits and withdrawals. Confirmations may take longer. Prices may be choppy.
If you send or receive often
You face timing risk. If the network splits, a payment on one chain may not appear on the other. Services may increase the number of required confirmations. You may pay higher fees to get into blocks if there is a rush.
If you run a business (exchange, custodian, merchant)
You face operational risk. You may need to choose which chain to support. You may need to adjust confirmation policies and pause some services during uncertainty. Clear customer notices reduce confusion.
If you run a node
Your risk is chain selection. If you enforce BIP-110, you may end up on a minority chain. If you do not enforce it, you stay with the majority. Make a plan and know how to switch if needed.
How to assess risk and prepare
1) Map your exposure
List where you hold funds: self-custody, exchanges, custodians.
Rank what must move in the next four weeks versus what can wait.
Note who controls the software: you, your vendor, or your custodian.
2) Check your providers’ plans
Read your exchange or wallet notices. Look for deposit/withdrawal rules, confirmation counts, and any chain selection policy.
Confirm customer support contacts if you need to act fast.
3) Watch the key metrics
Miner signaling share. Go to the live monitor and note daily trends.
Node counts reporting BIP-110 enforcement.
Mempool size and fee levels. Spikes mean slower confirmations.
Service status pages for major wallets and exchanges.
4) Set transaction safety rules
For important transfers, wait for more confirmations than usual.
Avoid large, urgent moves during peak uncertainty.
Split big transfers into smaller ones if you must move.
5) Prepare a communications plan
Businesses should draft short notices on delays, fees, and chain policy.
Publish clear cutoffs and confirmation requirements.
6) Decide your node policy
If you enforce BIP-110, understand you may follow a minority chain.
If you do not enforce, you likely follow the main chain.
Document how to revert or switch if conditions change.
Scenarios through block 965,664
Scenario A: No miner shift, no split
Miners keep signaling under 3%. Most users do not enforce. The window ends with no lock-in. The network runs as before. Impact: minimal, aside from a few service warnings and some debate.
Scenario B: Minority node chain appears
A visible group of users enforces BIP-110. Miners mostly ignore it. A minority chain forms. It has low hash power and slow blocks. Some nodes and services follow it; most stay on mainnet. Impact: confusion risk, service pauses, and possible price noise.
Scenario C: Late miner pivot
Some large miners flip and push signaling toward 55%. Confidence rises fast. Users prepare for lock-in. Impact: short-term fee and confirmation churn, then normalization.
What to watch each week
Week 1: Baseline support
Look for any jump from 2.5% signaling. If support stays flat, the status quo holds.
Week 2: Node momentum
Track growth in BIP-110 enforcing nodes. If the number climbs, split risk rises.
Week 3: Exchange policies
Exchanges start to post chain and deposit rules. Read them and adapt.
Week 4: Final positioning
Miners, services, and users show their final stance. Be ready to delay non-urgent moves until the window closes.
Practical actions to reduce pain
Individuals
Keep an on-chain buffer so you do not need urgent transfers.
Use higher confirmation targets for large payments.
Bookmark your providers’ status pages.
Businesses
Raise confirmation thresholds during the window.
Test deposit and withdrawal flows with small amounts first.
Publish simple customer updates and support hours.
Miners and service operators
Monitor orphan and stale block rates to track risk.
Coordinate internal incident response and rollback steps.
Document your signaling or non-signaling policy for partners.
Bottom line and next steps
BIP-110 is a live network event with low miner support and strong opinions on both sides. The risk of a minority chain is real if enough users enforce the rule, but it may also fade if support stays small. Keep your moves simple, raise confirmation counts, and follow public updates from your providers. With BIP-110 mandatory signaling explained here, you can cut noise, watch the right signals, and act only when you must.
(Source: https://www.coindesk.com/tech/2026/08/07/frame-bitcoin-s-bip-110-enters-mandatory-signaling-with-less-than-3-miner-support)
For more news: Click Here
FAQ
Q: What is BIP-110 and what does the mandatory signaling window mean?
A: BIP-110 mandatory signaling explained shows it is a proposal to temporarily curb non-financial data embedded on Bitcoin’s blockchain, and the mandatory signaling window is the set period when nodes and miners register support for that rule change. The window began at block 961,632 and runs until about block 965,664 (roughly four weeks), during which upgraded nodes would reject blocks that do not include a signaling bit.
Q: How much miner support does BIP-110 currently have, and what level is needed?
A: Miner signaling is under 3% (about 2.5%), which is far below the 55% threshold set by proposal watchers for success. If miner support stays low through the window, the proposal will not gain the miner backing needed to lock in.
Q: How does a user-activated soft fork (UASF) work in the context of BIP-110?
A: A UASF relies on node operators rather than miners to enforce a rule change by upgrading their software to reject blocks that don’t signal support. In BIP-110’s case, upgraded nodes would refuse non-signaling blocks, which could pressure miners to signal or create a minority chain of enforcing nodes.
Q: What immediate effects could BIP-110 enforcement have on everyday Bitcoin users?
A: Users may face service delays, paused deposits and withdrawals, longer confirmation times, and price volatility if a split or prolonged uncertainty occurs. The level of disruption depends on how often you move funds, how quickly you need access, and which software or custodial services control your funds.
Q: Could BIP-110 lead to a chain split, and what would the two chains look like?
A: Yes; one possible outcome is a dominant mainnet backed by the vast majority of hash power and institutional capital and a minority chain made up of BIP-110 enforcing nodes and any miners who choose to follow them. The minority chain would likely have low hash power and slower blocks, and it could either grow if more nodes join or grind to a halt without sufficient mining support.
Q: What practical steps can individuals and businesses take to reduce risk during the signaling window?
A: Individuals should map where they hold funds, keep an on-chain buffer, wait for extra confirmations for important transfers, and avoid large urgent moves during the window. Businesses should raise confirmation thresholds, test deposit and withdrawal flows with small amounts, publish clear customer notices, and prepare a communications plan for delays or chain-policy decisions.
Q: Which metrics and weekly milestones should I monitor to judge whether a split or lock-in is likely?
A: Monitor miner signaling share, counts of nodes enforcing BIP-110, mempool size and fee spikes, and service status pages for major wallets and exchanges. Weekly milestones to watch are baseline support in week 1, node momentum in week 2, exchange policy postings in week 3, and final positioning by miners and services in week 4.
Q: If I run a full node, what are the consequences of enforcing or not enforcing BIP-110?
A: Enforcing BIP-110 means your node will reject non-signaling blocks and could end up following a minority chain with low hash power, while not enforcing leaves you on the majority mainnet. Node operators should document their policy, understand how to revert or switch if conditions change, and plan for the chain-selection consequences.