0x074ff5c7074f…074ff5c4
Ethereum Testing Call Adds Juicebox to Glamsterdam Review
Nov. 16 Ethereum testing-call agenda adds Juicebox V6 compatibility to Glamsterdam review after Sepolia simulations showed payments failing silently under EIP-8037 and EIP-8038 gas changes.

Outputs
Nov. 16 testing-call agenda added Juicebox compatibility to the Glamsterdam review under EIP-8037 and EIP-8038 investigations.
Developer mejango tested deployed Juicebox V6 contracts on Sepolia on Nov. 14 across varied gas limits.
A cash-out route completed at gas limits of 679,622 to 817,622 without collecting its 2.5% fee.
Current mainnet rules produced either full failure or full payment delivery — no partial outcomes.
The Ethereum Foundation set Nov. 19 for developers to discuss the findings and next steps.
A Nov. 16 Ethereum testing-call agenda added Juicebox compatibility concerns to the Glamsterdam review, placing the fundraising protocol's deployed contracts squarely inside investigations of two proposed gas-cost overhauls, EIP-8037 and EIP-8038.
The agenda item follows simulations run Nov. 14 by the developer known as mejango, who tested deployed Juicebox V6 contracts on Ethereum's Sepolia test network. Juicebox V6 routes payments between projects on Ethereum. The tests began with newly launched and funded projects and varied transaction gas limits across scenarios.
The findings matter because they describe a new class of failure. Four tested paths allowed an overall action to complete while an internal payment failed or was silently skipped.
What did the simulations actually show?
The outcomes were specific and, for a payments-routing protocol, consequential:
- One route let a project payout finish without a split payment to another project, leaving the funds sitting in the paying project.
- A reserved-token distribution completed despite a failed cross-project transfer; the beneficiary received tokens directly.
- An NFT buyer kept the token after its related payment to another project failed.
- A cash-out route completed at gas limits between 679,622 and 817,622 without collecting its 2.5% fee.
For a protocol that moves money between projects, each of these represents revenue or funds arriving somewhere other than where the contract's logic intended. The 2.5% fee, for context, is the protocol's cut on cash-outs; a completed cash-out with no fee collected is a direct accounting gap.
Why do the proposed rules produce different failures?
Comparison simulations under current Ethereum mainnet rules ended in one of two ways: the transaction failed outright, or all payments were delivered. Partial-payment outcomes did not appear.
The mechanics are straightforward. In the tested paths, an internal payment that needed to write new blockchain data could exhaust its gas before the larger action finished. Juicebox's try/catch error handling caught that payment failure and allowed the surrounding action to complete anyway. The result is a finished contract action with an associated payment left undone.
EIP-8037 proposes higher costs for creating persistent blockchain data and changes the accounting for state creation and execution. EIP-8038 updates the costs of accessing and writing state. The agenda placed the Juicebox concerns within investigations of both proposals, which means developers must weigh protocol-level breakage against the proposals' broader gas-market objectives.
What has not been established?
The caveats are substantial. The results cover only the simulated paths and gas settings mejango tested. Independent developers have not reproduced them. No live incident has been reported on mainnet. In plain terms: this is a laboratory finding, not a demonstrated breach.
Even so, the operational stakes are clear. If Glamsterdam ships with EIP-8037 and EIP-8038 in their current form, deployed Juicebox V6 contracts could process user actions that appear successful while internal payments fail quietly. That is a worse failure mode than a reverted transaction, because users receive no signal that anything went wrong. The burden now shifts to the proposals' authors to either adjust the cost schedules or document why deployed contracts must absorb the risk.
The Ethereum Foundation scheduled a developer discussion for Thursday, Nov. 19, to review the findings and possible next steps. That meeting will indicate whether the Juicebox results force changes to the EIPs or simply enter the record as an accepted compatibility cost.
via tokenpost.com (Source)
More from Elena Vasquez
Show full bio
Staff writer covering regulation, policy and their impact on crypto and web3 industry at Mempool Brief.
1,525 articles