
Ethereum test exposes flaw that lets transactions skip payments
Ethereum's Glamsterdam upgrade tests reveal a flaw allowing transactions to succeed while internal payments fail, raising concerns about smart contract reliability.
Tests of Ethereum's proposed Glamsterdam upgrade have uncovered a critical flaw where transactions can succeed while internal payments fail, according to developer-published simulations. The Juicebox V6 simulations identified four specific paths where this occurs under tested Glamsterdam rules, contradicting the expected behavior on Ethereum's mainnet.
The simulations, conducted on the Sepolia test network using deployed contract code through eth_simulateV1, revealed scenarios where a buyer keeps an NFT while its payment to another project fails, or a cash-out completes without paying the associated 2.5% fee. These findings provide concrete examples of how the proposed changes could alter application payment guarantees.
Test Results
The V6 payout tests showed successful transactions that skip payments to other projects, leaving funds in the paying project. Similarly, a reserved-token distribution completes despite a failed cross-project payment, with beneficiaries receiving raw tokens instead. In the cash-out tests, gas limits between 679,622 and 817,622 allowed withdrawals to complete without paying fees.
Notably, mainnet comparison runs showed only transaction failures or complete delivery across the same ranges for all four tested paths. The discrepancy occurs because under Glamsterdam rules, an internal payment that writes fresh storage can fail before the outer transaction does, with the contract's try/catch error handling absorbing that failure.
Developer Concerns
Developer mejango highlighted that these simulations use deployed contract code and specific gas samples, noting no live incident or network-wide exposure has been established. The findings advance broader compatibility warnings from early November, leaving developers to weigh whether proposed protocol rules preserve the guarantees applications were built to deliver.
whether the impacts fall within the Ethereum Foundation's tolerance for breaking changes, linking the answer to confidence in building immutable applications whose deployed code cannot be changed in place.
Next Steps
Ethereum's Nov. 16 testing agenda explicitly lists Juicebox's compatibility concerns within the EIP-8037/8038 investigations. The Foundation's earlier guidance recommends reviewing public audit findings before deciding on specification changes or the Hoodi testnet schedule, with further discussion planned for Nov. 19.
The EIP-8037 and EIP-8038 proposals aim to support higher throughput while controlling resource demands by increasing costs for creating persistent blockchain data and updating state access costs. Core developers will use these test results to inform Thursday's execution-layer discussion before proceeding with implementation.