Markets
BTC $56,195 -8.74% ETH $1,571 -9.04% BNB $517 -8.93% XRP $0.8799 -8.71% SOL $66.06 -8.42% LINK $8.14 -7.40% BTC $56,195 -8.74% ETH $1,571 -9.04% BNB $517 -8.93% XRP $0.8799 -8.71% SOL $66.06 -8.42% LINK $8.14 -7.40% TOTAL $1.97T BTC.D 57.2%

Blockchain Technology

Ethereum’s Glamsterdam Tests Show a Transaction Can Succeed While Its Payment Fails

Developer-run simulations on Sepolia found four payment paths that complete on Glamsterdam while the transfer nested inside them is silently skipped.

Simulations of Ethereum’s proposed Glamsterdam upgrade, run against already-deployed Juicebox V6 payment contracts, have produced four cases where a transaction completes successfully while a payment nested inside it fails. The results, published by Juicebox developer mejango and dated Nov. 14, give core developers concrete examples of how the coming fork could change what an application-level payment guarantee means.

The tests ran on the Sepolia test network through eth_simulateV1 against contract code that is already live. Each simulation launches and funds a fresh project, pins the run to a specific block, and then exercises one payment path across a range of transaction gas limits. The same paths and gas samples were run against mainnet for comparison.

The sharpest case involves a cash-out. Across a sampled gas band running from 679,622 to 817,622, the withdrawal completes while the 2.5% fee attached to it is never paid. On mainnet the same samples either revert the whole transaction or deliver both parts — there is no band in which one succeeds and the other is quietly forgiven.

A second path shows a buyer keeping an NFT while the associated payment routed to another project fails, leaving the money in the paying project. A third shows a reserved-token distribution completing even though a cross-project payment failed, with the beneficiary receiving raw tokens instead of the routed result. In each case the outer transaction is recorded as a success.

The mechanism, according to the developer’s explanation, sits in the ordering of gas consumption. Under the tested Glamsterdam rules, an internal payment that writes fresh storage can exhaust its gas before the outer transaction does. The contract’s try/catch handling absorbs that failure and lets the surrounding operation finish. On mainnet’s current rules the internal failure lands first and takes the entire call down with it.

That is a narrow difference with wide reach for contracts that treat a nested transfer as a condition of the outer action. Juicebox’s design assumes a fee or a split charged inside the same call will either be paid or force a revert. The simulations show the Glamsterdam rules can break that assumption without a single line of Juicebox code changing.

The write-up is explicit about what it does not establish. These are developer simulations, not an independently reproduced result, and they cover only the tested paths and gas samples. No live incident and no network-wide exposure has been shown. Whether the behaviour reaches the final fork depends on how the storage and gas rules are specified when Glamsterdam ships.

What the runs do provide is a template. The failure is not a contract bug but an interaction between storage costs and error handling, and it appears only inside a gas window a caller can hit without meaning to. The practical takeaway for any application that routes value through a nested call is that “the transaction succeeded” and “the payment arrived” are now two separate questions that have to be checked separately.

Share this article

Viber uses viber://forward?text= when the app is installed.