The first event is BIP-110, also known as the Data Reduction Temporary Soft Fork. This is a draft proposal written by Dathon Ohm and assigned December 2025. This action imposes a temporary one-year consensus soft fork. Bitcoin By restricting arbitrary data storage in a particular format within a transaction. Supporters describe the proposal as a response to incentives they say have expanded after the ordinal and epitaph waves that began in 2022.
Temporary soft fork with permanent stake
BIP-110 is designed to enter the mandatory signaling phase at block 961,632, which lasts until block 963,647. Between the windows, node Primarily runs BIP-110 compatible software Bitcoin Not forks reject non-signaling blocks as invalid. This mechanism is intended to guarantee lock-in up to block 963,648 at the latest, followed by activation.
Its design forms the first hard pressure point. It’s not just about encouraging miners to signal. This creates a period where non-signaling can result in direct economic costs for miners whose blocks are rejected by the part of the network that enforces the ruleset. This proposal uses version bit 4, which allows early activation if 55% of miners (equivalent to 1,109 out of 2,016 blocks) send a signal within the retargeting period.
What BIP-110 limits
The temporary rules in BIP-110 restrict some transactional behavior for approximately 52,416 blocks, or approximately one year. Output containing a ScriptPubKey larger than 34 bytes is invalid, except for OP_RETURN, which is limited to 83 bytes. Large data pushes and monitoring items will be limited to 256 bytes, and some Taproot-related features will face temporary limitations.
input expenditure UTXO Anything created before activation will remain exempt forever. The restriction also automatically expires after a one-year period, making design choice proponents set the frame as a temporary line rather than a permanent rewrite. Bitcointrading policy.
For proponents, see Discipline; for critics, see Risk Division
Including supporters Bitcoin Knots users and Ocean Pool participants may, by BIP-110, blockchain distention, inferior node Reducing and reinforcing operating costs Bitcoinfinancial purpose. They frame the proposal as a corrective to the embedding of non-monetary data and a cultural signal about what it looks like. Bitcoin Block space should be used for:
Critics warn that the proposal could destroy consensus, hinder advanced scripting work, create uncertainty for developers and set a precedent for protocol-level filtering of paid block spaces. Current miner signaling remains very low, with only 0.31% signaling as of June 22nd, making the August deadline even more important.
Sztorc’s eCash plan adds another forkfight
Another August development unrelated to BIP-110 is also poised to gain attention. Paul Sztorc, creator of Drivechain and BIP 300 associated with Layertwo Labs, announced plans for an eCash hard fork in August 2026, targeting around 964,000 blocks. This plan creates a new SHA-256d chain that starts as a near copy of . Bitcoin Core, difficulty is reset only once at startup, 1:1 air drop to BTC A holder based on a fork block.
The eCash offer is not >
The stakes are different from previous fork cycles. Bitcoin is now widely held through spot exchange-traded funds (ETFs), corporate treasuries, and regulated custody structures. The eCash plan has also drawn criticism for its handling of Satoshi-era coins, with discussions about partial reallocation for development and community incentives. Critics have attacked the concept as unfair, but supporters, including Stork, argue that forks are voluntary and holders can decide what to do with the new chain.
One window in August, two separate disputes
What turns these two separate events into dual pressure points is the timing. The mandatory signaling window for BIP-110 begins at block 961,632 and is designed to guarantee lock-in until block 963,648. The eCash fork targets around block 964,000, just a few hundred blocks later. In terms of block time, the two conflicts are piled up in the same narrow period of time.
The interesting thing about both of these events is that they are different proposals, supported by different factions, and aimed at different issues. Connections can be manipulated according to context. Tested in one event. Bitcoinone to perform the data policy and consensus change process, and the other to test the fork. air dropand expanded politics almost immediately thereafter.
Miners face a choice between revenue, signaling and hashing power
For miners, compressed windows can create conflicting incentives. During the mandatory signaling period of BIP-110, miners may face pressure to signal bit 4 to avoid mandatory orphan risk. node. However, currently it is only 5.37 exahash per second (EH/s). Bitcoin940 EH/s total hash rate Transmitting BIP-110 signal. Shortly after, the launch of eCash could offer a new SHA-256d chain with difficulty reset and potential sidechain-related revenue.
eCash includes 1:1, so air dropthe planned launch is likely to garner more market and public attention than BIP-110, which in many ways already has. Forks give miners a second economic incentive. You can merge mine while directing the same SHA-256d hardware or old machines to new assets. side chain Secured through blind merge mining.
Exchanges and custodians become the front line of operations
Infrastructure may be more strained than market views suggest. Exchanges and custodians may be asked to process coin split requests, assess replay protection, and identify dominant coins. Bitcoin Track the cascade of BIP-110-related splits as they occur and explain policy decisions to users in real-time.
The operational layer is important because once deposits, withdrawals, accounting, and user balances are involved, protocol disputes become more than technical arguments. Under severe stress, small delays, unclear policies, or contradictory chain signals can become even larger.
Markets read timing as risk
For markets, setups are less directional than tense. 1:1 electronic cash air drop It may incentivize some holders to keep their Bitcoin via fork blocks. The challenged BIP-110 enforcement policies could prompt other exchanges to reduce exposure before the deadline, especially if exchanges warn of service suspensions, replay concerns, or storage delays.
The central issue here is that two conflicting protocol events are arriving within the same compression window. One is a temporary soft fork with mandatory signaling and data limits. The other is a hard fork with new assets and drivechain activation. Together, these create an intensive test of Bitcoin’s technical discipline, miner coordination, market confidence, and public narrative.
What to watch next
What matters next are miner actions leading up to block 961,632, node adoption around BIP-110 compatible clients, exchange and custodian statements regarding eCash, and whether major infrastructure providers flag replays, deposits, withdrawals, or accounting risks ahead of block 964,000. If these signals remain fragmented, August could focus more on how Bitcoin handles two different governance tests simultaneously, rather than addressing either proposal in isolation.
