Simulations published by a developer show that under Ethereum's proposed Glamsterdam upgrade, a transaction can succeed even when a payment within it fails. The tests used Juicebox V6 project-payment contracts.
Four tested paths produced this outcome in the developer's simulations on the Sepolia test network, giving core developers concrete examples of how the changes could affect payment guarantees in applications.
The Nov. 14 runs examine Juicebox V6 contracts that route payments between projects. The published results include a buyer keeping an NFT even though its associated payment to another project fails, and a cash-out completing while a 2.5% fee is waived.
A successful Ethereum transaction receipt can conceal a missed payment
Developer mejango says the tests use deployed contract code through eth_simulateV1. A new project is launched and funded in each simulation, then a payment path is tested at different transaction gas limits. Each scenario is fixed to a specific blockchain block.
The V6 payout test records successful transactions that skip a split payment to another project, leaving the money in the paying project. A reserved-token distribution also completes despite a failed cross-project payment, with the beneficiary receiving raw tokens instead.
In the cash-out test, sampled gas limits in the reported 679,622-to-817,622 range allow the withdrawal to complete without paying the fee.
Across the sampled ranges, the mainnet comparison runs show either transaction failures or complete delivery for all four paths.
According to the developer's explanation, the difference depends on which operation runs out of gas first. Under the tested Glamsterdam rules, an internal payment that writes fresh storage can fail before the outer transaction runs out of gas.
The contract's try/catch error handling catches that failure and allows the surrounding operation to finish.
EIP-8037 proposes higher costs for creating persistent blockchain data and separate accounting for state creation and execution, while EIP-8038 updates the costs of accessing and writing state. The changes aim to support greater throughput while controlling resource demands.
Ethereum's Nov. 16 testing-call agenda specifically includes Juicebox's compatibility concerns and proofs of concept in the EIP-8037/8038 investigations. The findings are intended to inform Thursday's execution-layer discussion.
In a Nov. 13 comment on the agenda, mejango asked whether the impacts fall within the Ethereum Foundation's tolerance for breaking changes. The comment linked the answer to confidence in building immutable applications, whose deployed code cannot be changed in place.
The tests build on the broader compatibility warning from early November by providing specific payment outcomes from deployed contract code. Developers are left to weigh whether the proposed protocol rules preserve the guarantees those applications were designed to provide.
In its earlier Nov. 9 update, the Foundation recommended reviewing public audit findings before deciding on specification changes or the Hoodi testnet schedule. It lists Nov. 19 for discussing the findings and possible next steps, with no decision made in advance.

