BIP-110 Supporters Discuss Hard Fork to Change Stalled Chain Mining Algorithm to BLAKE2b

BIP-110 supporters are discussing a hard fork to change the stalled minority chain's mining algorithm from SHA-256d to BLAKE2b. Before the fork, transaction history would remain shared by both chains, and if transaction and signature rules stay the same, the same transaction could be copied to the other chain and replayed, creating a replay attack.According to Odaily, BIP-110's miner support peaked at about 2.53%, and 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 running and widened the block-height gap. The BIP-110 proposal was later marked closed, and supporters shifted to discussing a BLAKE2b proof-of-work plan.Bitcoin Knots plans to add a new signature-hash option, while RDTS will keep compatibility with Bitcoin Core's existing signature-hash types. Ordinary transactions may remain valid on both chains, and users will need the new option, along with wallet or hardware-signing firmware support, to separate assets.Luke Dashjr said on August 18 that Bitcoin should bear responsibility for replay protection and referred to it as "Spamcoin." If the BLAKE2b fork moves forward around September 1, exchanges, wallets, and holders will need to distinguish between cross-chain transactions and chain-specific transactions.