Sprinter Co-Founder Warns Ethereum Testnets Miss Breakages Like EIP-1559

A former maintainer of web3.js says Ethereum's testnets cannot catch every edge case that breaks live applications, citing the EIP-1559 upgrade in August 2021 as evidence. Greg Markou, co-founder and CEO of Sprinter, made the remarks during a public discussion among Ethereum developers about the realities of shipping protocol changes on the network.

Markou's position carries weight because he maintained web3.js during the London hard fork, which shipped in August 2021. web3.js is the JavaScript library that lets applications communicate with the Ethereum blockchain — the translation layer between a website and the network itself.

What broke during the London hard fork?

According to Markou, an update tied to the EIP-1559 upgrade had consequences nobody anticipated: nearly every application relying on web3.js was affected. The culprit was an invariant involving MetaMask that went undetected through testing. An invariant is a condition developers assume will always hold true. When that assumption quietly stops holding, everything built on top of it can fail.

A hard fork changes Ethereum's core rules across the entire network. Every node must adopt the new rules, which means software built on old assumptions can suddenly find itself out of step with the chain. Markou described Ethereum as an "absolute monolithic beast" — a system grown so large and interconnected that predicting how a single change ripples outward is genuinely difficult.

Why testnets are not the safety net developers assume

Testnets are practice versions of a blockchain where developers trial changes without risking real money. Markou acknowledged they are beneficial. His argument is narrower: they fail to cover all the edge cases that hit live applications.

On mainnet, applications interact with wallets, libraries and other contracts in combinations no single test environment fully reproduces. The MetaMask invariant that disrupted web3.js users in 2021 is a case study in exactly that kind of blind spot — a dependency chain no rehearsal could have exposed.

For practitioners, the operational lesson is direct. Passing a testnet run does not certify application compatibility with an upcoming fork. Teams maintaining libraries and infrastructure should audit their assumptions about wallet and client behavior before each activation, because the blast radius of a broken invariant in a widely used library like web3.js can reach nearly every application that depends on it.

Who is Greg Markou, and what is Sprinter building?

Markou previously co-founded ChainSafe Systems, the firm that maintained web3.js. Sprinter launched out of ChainSafe, and Markou now leads it as CEO.

The company raised $5.2 million in a seed round in November 2025. Its focus is cross-chain credit and infrastructure, with a pitch it calls "solving-as-a-service." Sprinter also plans a native governance token called SPRINT.

No new upgrades or protocol changes resulted from the discussion. The exchange was about lessons learned rather than announcements. Still, the timing matters for infrastructure teams: as Ethereum continues to schedule protocol changes, Markou's account of 2021 serves as a standing reminder that the gap between testnet success and mainnet stability is where production applications get damaged.

Developers shipping on Ethereum should treat each future fork as a live compatibility audit, not a formality cleared by testnet rehearsal.