Summary Schwartz criticized BIP-110 supporters for portraying Bitcoin’s established blockchain as a legacy network requiring correction through alternative governance rule proposals. BLAKE2b
Ripple CTO emeritus David Schwartz criticized a BIP-110 supporter for claiming developers sought to fix Bitcoin’s established blockchain network governance. According to Schwartz, BIP-110 supporters shifted from governance participation toward attack when they rejected the outcome of their campaign entirely.
Loogart countered that the group accepted defeat, chose another proof-of-work system, and began developing an independent Bitcoin blockchain voluntarily elsewhere. He argued that open dialogue, soft forks, and hard forks remain legitimate choices because nobody must support any alternative blockchain.
Schwartz challenged Loogart’s description of Bitcoin as a legacy chain requiring repairs determined by one dissatisfied group of network participants. His brief response, “Listen to yourself,” highlighted the assumption behind presenting Bitcoin’s dominant blockchain as technically broken or improperly governed.
The discussion originated when an X user described BLAKE2b as a Bitcoin attack resembling the Bitcoin Cash and Bitcoin SV forks. Loogart rejected that comparison, arguing that opposing Bitcoin Core and creating separate rules does not constitute coercion against existing users.
Also Read: XRP ETFs Attract $110 Million as Price Retreats Below $1.37
BLAKE2b changes Bitcoin’s SHA-256d mining system, allowing the breakaway chain to operate without relying on miners securing the established network. Developer Luke Dashjr backs the project, which is scheduled to launch on September 1 under its alternative proof-of-work mining algorithm.
However, no major cryptocurrency exchange, wallet provider, or Lightning implementation has committed support for the proposed blockchain before its launch. That limited backing creates obstacles involving liquidity, accessibility, mining security, reliable block production, user participation, and meaningful commercial adoption overall.
BLAKE2b follows an earlier BIP-110 minority chain that attempted to restrict non-financial data placed within Bitcoin blocks across the network. Those proposed limits targeted inscriptions, Ordinals, BRC-20 tokens, Runes, and arbitrary payloads that supporters considered harmful to Bitcoin’s financial purpose.
Critics maintained that users should access available block space whenever they meet network rules and pay the required transaction fees. The minority fork mined only two blocks across eight hours before insufficient participation stalled its operations and exposed infrastructure support.
Ultimately, BLAKE2b must attract dependable miners, developers, wallets, exchanges, and users before establishing itself as a viable independent Bitcoin network.
Also Read: Blockchain Association Backs Stablecoin Rules Exempting Peer-to-Peer Transfers
The post Ripple CTO Emeritus Slams BIP-110 Supporter Over Bitcoin Legacy Chain Claim appeared first on 36Crypto.
