During Ethereum’s Glamsterdam trials, developers uncovered overlooked project payouts alongside waived withdrawal charges, sparking fresh doubts about whether the network’s smart contracts can be reliably trusted.
Simulations of Juicebox V6’s project-payment contracts, released by developers, demonstrate that Ethereum’s upcoming Glamsterdam upgrade lets a transaction go through even as an underlying payout fails.
During the developer’s trials on the Sepolia test network, four distinct execution paths yielded that result, offering core engineers tangible proof of how these updates might reshape payment assurances across applications.
The Nov. 14 trials evaluate Juicebox V6 contracts that direct funds between projects. Published findings reveal a buyer retaining an NFT despite a failed transfer to a linked project, alongside a withdrawal finalizing even as a 2.5% fee gets waived.
Ethereum Transaction Receipts Can Show Success Even When Payments Fail
Developer mejango explains that the trials run live contract code via eth_simulateV1. Each simulation spins up and funds a new project before testing a payment route across varying transaction gas limits, with every scenario anchored to a specific blockchain block.
Findings from the V6 payout test highlight successful transactions that bypass a split meant for another project, keeping those funds within the originating pool. Similarly, a reserved-token allocation wraps up even when a cross-project transfer fails, leaving the recipient with raw tokens instead.
During the cash-out trial, sampled gas limits within the reported 679,622-to-817,622 range allowed the withdrawal to finalize without the fee being collected.
Mainnet benchmark runs reveal either outright transaction failures or full execution across the tested ranges for every one of the four paths.
According to the developer’s breakdown, the difference hinges on which operation exhausts its gas supply first. Under the evaluated Glamsterdam rules, an internal payment writing new storage can stall out before the outer transaction gets halted.
The contract’s try/catch error-handling mechanism absorbs that failure, allowing the surrounding operation to be completed smoothly.
EIP-8037 puts forward higher fees for generating persistent blockchain data alongside distinct accounting for state creation and execution, whereas EIP-8038 adjusts the expenses tied to accessing and writing state. Together, these updates seek to boost network throughput while resource demands are kept in check.
Ethereum’s Nov. 16 testing-call agenda specifically highlights Juicebox’s compatibility issues and proofs of concept under the EIP-8037/8038 reviews. These findings were compiled to guide Thursday’s execution-layer meeting.
In a Nov. 13 remark on that agenda, mejango questioned whether these side effects stay within the Ethereum Foundation’s threshold for breaking changes, tying the answer to developer confidence in building immutable apps where deployed code cannot be altered in place.
These trials build upon the wider compatibility alert issued in early November, presenting concrete payment outcomes drawn from live contract code. They leave developers evaluating whether the proposed protocol rules uphold the guarantees these applications were originally built to deliver.
In its prior Nov. 9 statement, the Foundation advised examining public audit results ahead of locking in specification tweaks or the Hoodi testnet timeline. The group scheduled Nov. 19 to review those discoveries and weigh potential next steps, with no final outcome predetermined.

