0x0d74e8cf0d74…0d74e8cc
Juicebox Sepolia Tests Find Skipped Payments Under Glamsterdam Gas Rules
Nov. 14 Sepolia simulations of Juicebox V6 under Glamsterdam gas rules found skipped project payments and a forgiven 2.5% fee, feeding an Ethereum review that has delayed Hoodi.

Outputs
Nov. 14 Sepolia simulations of Juicebox V6 under Glamsterdam rules found three failed or skipped payments and one forgiven 2.5% fee.
Developer mejango swept gas limits in 2,000-gas steps using eth_simulateV1 on deployed contract code; no live transactions were involved.
Under current mainnet rules, the same paths either reverted or delivered all payments, with no skipped-payment range.
Glamsterdam includes EIP-8037 and EIP-8038, which alter gas costs for some operations and state.
An execution-layer call on Thursday, Nov. 19, will discuss the findings; the Hoodi testnet activation remains delayed.
Juicebox V6 simulations run on Ethereum's Sepolia testnet on Nov. 14 found three cases where project payments failed or were skipped, plus one case where a 2.5% cash-out fee was forgiven — all under the proposed Glamsterdam gas rules. The tests involved no live transactions and no lost funds. But they land squarely in the middle of an Ethereum Foundation review that has already delayed the Hoodi testnet activation.
Juicebox developer mejango ran deployed contract code through eth_simulateV1, starting a fresh project in each run and sweeping gas limits in 2,000-gas steps. Four outcomes stood out.
- Payout test: the payout completed, but a split to another project was skipped at gas limits from 717,310 to 1,105,310, leaving the funds in the paying project.
- NFT test: a buyer kept the token while its tier payment failed between 2,854,229 and 3,230,229 gas.
- Reserved-token test: a beneficiary received raw tokens while a split payment failed from 489,135 to 813,135 gas.
- Cash-out test: the withdrawal completed while its 2.5% fee was forgiven at gas limits from 679,622 to 817,622.
The pattern matters more than any single number. Operations that should be atomic — pay, split, cash out — can come apart at the seams under the new gas accounting.
What does this change for Juicebox?
For now, nothing in production. The simulations do not establish an exploit, any losses, or how often these outcomes might occur on mainnet. Mejango's explanation is mechanical: an internal payment can run out of gas before the larger transaction does, and the contract's try/catch handles that failure so the outer operation finishes anyway. The result is a transaction that looks successful while quietly dropping a piece of its intended work — or, in the cash-out case, waiving a fee.
The comparison runs are the key control. Under current Ethereum mainnet rules, the same tested paths either reverted entirely or delivered all payments, with no matching skipped-payment range. That gap between old and new rules is exactly what auditors and core developers are now scanning for across deployed contracts.
The trigger is Ethereum's proposed Glamsterdam upgrade, which includes EIP-8037 and EIP-8038. Both proposals would alter gas costs for certain operations and state access, which can shift where a contract's inner calls hit their gas ceilings. Contracts written when gas costs were predictable may not behave the same way once those costs move.
Why the Foundation paused Hoodi
The Ethereum Foundation has already delayed the planned Hoodi testnet activation while developers and auditors review potential effects on deployed contracts. The Juicebox tests add concrete, named cases to what had been a broader, more abstract sweep of possibly affected code. A protocol treasury system with skipped payouts and forgiven fees is a sharper illustration than a hypothetical.
Mejango framed the stakes plainly. "Confidence is the one thing we cannot sacrifice in the name of scaling, etc.," the developer wrote on Nov. 13.
What happens next
An execution-layer call scheduled for Thursday, Nov. 19, is set to discuss the findings and possible next steps. No specification change has been precommitted, and there is no new Hoodi schedule on the table yet. For teams building on Ethereum, the practical takeaway is simple: simulate your deployed contracts under Glamsterdam rules now, before the upgrade's parameters harden.
via tokenpost.com (Source)
More from Marcus Bennett
Show full bio
Senior reporter covering money, funding and market shifts around crypto and web3 industry at Mempool Brief.
1,456 articles