News linked to both this project and an event.
Odaily News: BIP-110 supporters are discussing a hard fork to change the stalled minority chain's mining algorithm from SHA-256d to BLAKE2b. Transaction history before the fork remains shared by both chains. If transaction and signature rules remain consistent, the same transaction could be replayed on the other chain, creating a replay attack.BIP-110's peak miner support was approximately 2.53%. After the consensus rules took effect on August 8, the minority chain produced only two consecutive blocks before stalling, while the Bitcoin main chain continued operating and widening the block height gap. The BIP-110 proposal was subsequently marked as closed, and supporters shifted focus to discussing the BLAKE2b proof-of-work scheme.Bitcoin Knots plans to add a new signature hash option, but RDTS will still maintain compatibility with Bitcoin Core's existing signature hash types. Regular transactions may continue to be valid on both chains. Users will need to use the new option and rely on wallets or hardware signing firmware that support it to achieve asset separation.Luke Dashjr stated on August 18 that Bitcoin should bear the responsibility for replay protection, calling it "Spamcoin." If the BLAKE2b fork proceeds around September 1, exchanges, wallets, and holders will need to distinguish between cross-chain transactions and chain-specific transactions. (Bitcoin.com News)
Odaily News – Luke Dashjr, co-founder, chairman, and CTO of Jack Dorsey-backed Bitcoin mining pool Ocean, has announced he is temporarily stepping away from these roles to focus on Bitcoin and open-source project development. Ocean's communications lead, Bitcoin Mechanic, has also announced a temporary departure. Both have stated this is a temporary leave of absence rather than a permanent resignation.The BIP-110 minority chain has mined only two blocks since splitting at block height 961,632, and has since stalled due to inheriting Bitcoin's 127,480,000 difficulty and a relatively low share of SHA-256d hashrate. Bitcoin Knots developers are preparing a hard fork that plans to reset the proof-of-work, adjust the block header, and add replay protection.Developers plan to select the new PoW algorithm from BLAKE2b-256, SHA3x, BLAKE2s, Scrypt, BLAKE3x2, and Eaglesong, using a commit-reveal mechanism, with the algorithm to be determined by the next block produced after 14:00 UTC the following day. Dashjr, Kyle, and Chris Guida are respectively responsible for the block header and PoW, replay protection, and RDTS adaptation. BIP-110 shares transaction history with Bitcoin, and developers believe changes such as transaction signatures are needed to prevent Bitcoin transactions from becoming valid on the minority chain. The Bitcoin community has criticized the fork for producing only two blocks so far, arguing that nodes can execute custom rules but cannot compel users, miners, exchanges, and businesses to switch to the chain. (Bitcoin News)
Odaily News: After forking at block height 961632, the BIP-110 minority chain has only mined two blocks, 961632 and 961633, and has since stalled due to inheriting Bitcoin's difficulty of approximately 127.48 trillion while receiving extremely low SHA-256d hash power. Pre-fork miner support was approximately 0% to 2.6%. BIP-110 supporters are discussing replacing the proof-of-work algorithm to break free from reliance on Bitcoin miners and SHA-256d hash power. Luke Dashjr has proposed selecting the final algorithm from a shortlist of candidates through a deterministic random process, with options under discussion including RandomX, KT256, BLAKE3, Scrypt, as well as CPU and GPU mining. No PoW changes have been enabled or approved yet, no algorithm has been selected or activation height announced, and Bitcoin Knots has not committed to adjusting the PoW. Relevant experimental code has been ported to the recent Bitcoin Knots codebase, but the BIP-110 minority chain has still not resumed block production.
Odaily News Bitcoin nodes running BIP-110 rules have begun enforcing mandatory signaling mechanisms at block height 961,632. Latest data shows that BIP-110 miner signaling support fluctuates between just 0.3% and 2.6%, with no major mining pool publicly supporting the proposal. Nodes enabling BIP-110 enforcement rules are mainly operated by users running Bitcoin Knots software. These nodes subsequently reject blocks that do not emit signals, effectively isolating themselves from the Bitcoin main network.It is reported that the BIP-110 signaling period will continue until Bitcoin block height 965,664, expected to conclude in approximately four weeks. At that point, the community will face the critical decision of whether to activate the proposal. If the 55% miner support threshold is reached during the signaling period, BIP-110's data limit rules will take effect at block height 965,664 and remain active for approximately one year, covering around 52,416 blocks.Analysts point out that unlike the 2017 Bitcoin Cash fork, the BIP-110 split lacks substantial miner support and exchange infrastructure. If the number of nodes and hash power separating from the main chain proves insufficient, the forked chain could face severe block production speed issues. Since Bitcoin's difficulty adjustment mechanism relies on stable hash power, when a minority chain loses adequate miner support, block generation times could extend from the target 10 minutes to several hours or even days.For Bitcoin Knots node operators who have already enabled BIP-110 rules, the current practical impact is that their nodes can no longer stay synchronized with the Bitcoin main network. Going forward, they will need to either disable the enforcement rules and resynchronize with the main chain, or continue running this independent network that lacks widespread support. (Cryptobriefing)
Bitcoin developer Chris Guida has reset the PoW change code written by Bitcoin developer Luke Dashjr in 2017 onto the recent Bitcoin Knots codebase. The code has not yet been scheduled for activation, and Guida stated that it serves as a contingency plan and is not an imminent fork. BIP-110 is a temporary soft fork proposal that aims to restrict arbitrary data embedded in Bitcoin transactions within approximately one year, including restoring the OP_RETURN 83-byte consensus limit. The proposal requires 55% miner signaling support, meaning 1,109 blocks out of 2,016 blocks, to achieve early lock-in. If the threshold is not met, the forced signaling window will begin at block 961,632, expected to occur around August 8 or 9. Nodes implementing BIP-110 will subsequently reject blocks that do not emit a support signal, with lock-in expected no later than block 963,648 and activation targeted at approximately block 965,664. As of 8:15 AM Eastern Time on August 7, 2026, the chain tip height is 961,425, with 207 blocks remaining until the forced window begins. Only 47 out of 1,818 blocks have emitted a BIP-110 support signal, with the current signaling rate at approximately 2.59%.
BIP-110 supporter Dathon Ohm stated that forced signaling for BIP-110 is expected to begin after approximately 290 blocks, equivalent to about 48 hours. At that time, miners must indicate readiness for BIP-110 through block signaling, otherwise relevant blocks may be deemed invalid and discarded. He also suggested miners and users upgrade to Bitcoin Knots nodes, and stated that continuing to run Bitcoin Core after forced signaling activates will pose security risks.
Odaily News: Bitcoin's BIP-110 will enter the enforcement phase after block 961,632, where nodes will reject blocks that do not signal support. Monitoring page data shows that among the 1,674 blocks counted in the current cycle, only 41 blocks support BIP-110, putting the miner signal support rate at 2.45%. BIP-110, officially named "Reduced Data Temporary Softfork," plans to tighten certain data rules in Bitcoin transactions within approximately one year, restricting the size of certain data elements used by Ordinals inscriptions and multiple token protocols. The proposal is primarily distributed through Bitcoin Knots, and Bitcoin Core has not adopted it. Major mining pools such as Foundry, Antpool, F2pool, and Viabtc have not issued support signals. If BIP-110 nodes execute as planned, the network could see two transaction histories, with the majority of miners and Bitcoin Core users expected to continue using the existing rules. Australian Bitcoin exchange Hardblock stated that BIP-110 activation is expected around August 7-8 and may temporarily suspend buying, selling, deposits, and withdrawals. Lightning Network tools and analytics provider Amboss has warned of a fork risk in early August, and Australian Bitcoin exchange Bitaroo plans to freeze deposits and withdrawals as the mandatory signaling deadline approaches.
Bitcoin News posted on X platform that Bitcoin developer Chris Guida stated he has rebased Luke Dashjr's 2017 proof-of-work change code onto the latest version of Bitcoin Knots, as a contingency plan in case miners refuse to signal support for BIP-110. The proposal will serve as a last-resort option to replace the existing mining network if major mining pools are deemed unsupportive of the BIP-110 soft fork. Luke Dashjr stated that he hopes the plan will not be needed, "but it's probably better to prepare in advance, just in case." Supporters such as Mechanic expressed support for preparing the code in advance, noting that the threat of proof-of-work changes helps ensure miners remain accountable to node operators, rather than dominating Bitcoin's rules.
According to Decrypt, Strategy Executive Chairman Michael Saylor recently published a long article titled "110 Reasons BIP 110 Is a Bad Idea," comprehensively opposing the Bitcoin BIP-110 soft fork proposal. BIP-110 aims to temporarily restrict non-financial data such as Ordinals and inscriptions from being on-chain by tightening consensus rules. Supporters (including developer Luke Dashjr and the Bitcoin Knots camp) characterize it as an "anti-spam transaction" measure. Saylor raised three core objections to this: • Precedent Risk: Bitcoin cannot identify data "intent"; blocking a type of usage via consensus means will set a dangerous template for future innovations targeting privacy tools, stablecoin settlements, etc., "The restriction period is about one year, but the precedent exists permanently" • Activation Mechanism Risks: BIP-110 lowers the miner signaling threshold from 95% to 55%, and removes the proposal natural expiration option. With the current signaling rate below 1%, inconsistent execution could lead to network split • Classification Controversy: Saylor believes "spam" is not a consensus-layer concept; dislike for a certain type of usage does not equal invalidity. "Bitcoin does not need guardians of purity, but guardians of neutrality" Saylor's stance aligns with Blockstream CEO Adam Back, Casa Co-founder
Odaily Strategy Executive Chairman Michael Saylor published a 110-point article opposing the proposed Bitcoin soft fork BIP-110. BIP-110 plans to tighten Bitcoin's consensus rules within about a year, restricting the technology used for embedding arbitrary data, targeting non-financial data such as Ordinals and inscriptions. Michael Saylor stated that BIP-110 would invalidate currently valid transactions that pay fees through consensus changes, and claimed that Bitcoin cannot differentiate data intent. He believes that including a specific use case within the consensus layer restrictions would set a governance precedent. While the specific restrictions would expire in about a year, the precedent would not disappear. He also opposed the proposal's activation design, stating it lowers the miner signaling threshold from the 95% used in earlier soft forks to 55%, and removes the option that typically allows proposals to naturally expire. Data from a proposal monitoring dashboard shows current signaling support is below 1%. The mandatory signaling window for BIP-110 is scheduled to open in August, with a target activation date around September 1st. Michael Saylor's stance aligns with Blockstream CEO Adam Back, Casa's Jameson Lopp, and Bitcoin proponent Samson Mow. Opponents include developer Luke Dashjr and the Bitcoin Knots camp.
the Bitcoin BIP-110 proposal is approaching its early August deadline, with miner support currently below 1%. In the current cycle, support stands at 0%, and no major mining pools have signaled in favor. BIP-110, officially titled "Reduced Data Temporary Soft Fork," aims to restrict OP_RETURN data capacity within one year, prohibit most arbitrary data writes exceeding 256 bytes, and limit certain script formats primarily used for data storage. Strategy founder Michael Saylor and Blockstream co-founder Adam Back have both publicly opposed BIP-110. Data shows that BIP-110 adopts a user-activated soft fork mechanism, setting a 55% miner signal threshold. The proportion of nodes running BIP-110 software remains in the single digits, primarily from Bitcoin Knots users. The current signaling cycle for this proposal is expected to end near block height 959,615, entering a voluntary lock-in period around early August, with activation planned for approximately September. If broad support remains absent by then, it could lead to a small number of nodes forming a split chain.