TLDR
Simulations of Ethereum’s Glamsterdam upgrade show transactions that succeed while internal payments fail.
A developer found four such payment paths in Juicebox V6 contracts on the Sepolia test network.
In one test, a cash-out finished without paying its 2.5% fee.
Mainnet comparison runs showed only full delivery or transaction failure.
The Ethereum Foundation has set Nov. 19 to discuss findings and possible next steps.
Simulations of Ethereum’s proposed Glamsterdam upgrade show that a transaction can report success while a payment inside it fails. The tests were run on Juicebox V6, a set of contracts that route payments between projects.
A developer known as mejango published the results from runs dated Nov. 14. Four tested payment paths produced the same outcome on the Sepolia test network, according to a CryptoSlate report.
The findings come days before Ethereum core developers are set to discuss the upgrade again. Ether traded at $1,791.53, down 0.57% over 24 hours.
How the Tests Were Run
The developer said the simulations used deployed contract code through a tool called eth_simulateV1. In each run, a fresh project was launched and funded inside the simulation.
A payment path was then tested across different transaction gas limits. Each scenario was pinned to a specific blockchain block.
The same four paths were also tested under current mainnet rules for comparison. Those runs showed only two results: the transaction failed, or every payment was delivered in full.
Four Paths Where Payments Slipped
In the payout test, transactions succeeded while skipping a split meant for another project. That money stayed in the paying project instead.
A reserved-token distribution also completed even though a cross-project payment failed. The beneficiary received raw tokens instead.
Another result showed a buyer keeping an NFT while the related payment to another project failed. The purchase still went through.
In the cash-out test, gas limits between 679,622 and 817,622 let a withdrawal finish without paying a 2.5% fee. The fee was forgiven while the user still received the cash-out.
The developer said the difference comes down to which operation runs out of gas first. Under the tested rules, an internal payment that writes fresh storage can fail before the outer transaction does.
The contract’s try/catch error handling then absorbs that failure. The surrounding operation is allowed to finish.
The results are developer simulations and have not been independently reproduced. They cover tested paths and gas samples only, and no live incident has been reported.
The upgrade includes EIP-8037, which proposes higher costs for creating persistent blockchain data. It also separates the accounting for state creation and execution.
EIP-8038 updates the costs of accessing and writing state. Together, the changes aim to support more throughput while controlling resource demands.
In a Nov. 13 comment, mejango asked whether the impacts fall within the Ethereum Foundation’s tolerance for breaking changes. The developer tied the answer to confidence in building immutable applications, whose code cannot be changed after deployment.
Ethereum’s Nov. 16 testing-call agenda listed Juicebox’s compatibility concerns and proofs of concept under the EIP-8037 and EIP-8038 investigations. The findings are meant to inform Thursday’s execution-layer discussion.
In a Nov. 9 update, the Ethereum Foundation recommended reviewing public audit findings before deciding on specification changes or the Hoodi testnet schedule. It set Nov. 19 for discussion of findings and possible next steps, with no decision made in advance.
Comments are closed.