Loading prices…
🩸BEARISH

Ethereum Tests Expose Glamsterdam Skipped-Payment Flaw

The simulations expose a compatibility risk in EIP-8037/8038, forcing developers to test payment guarantees before protocol changes advance.

Ethereum Tests Expose Glamsterdam Skipped-Payment Flaw
Ethereum Tests Expose Glamsterdam Skipped-Payment Flaw

Simulations of Juicebox V6 contracts exposed four tested paths where an Ethereum transaction succeeds while an internal payment fails under proposed Glamsterdam rules. The results included a buyer retaining an NFT without its associated cross-project payment and a cash-out completing without paying a 2.5% fee. In the cash-out scenario, sampled gas limits from 679,622 to 817,622 allowed the withdrawal to finish without the fee.

The tests ran on Sepolia using deployed contract code through eth_simulateV1. Across sampled mainnet comparisons, Ethereum produced either transaction failures or complete delivery, with no skipped-payment band identified. Developer mejango attributed the difference to the order in which operations exhausted gas: under the tested rules, an internal payment writing fresh storage could fail before the outer transaction, while try/catch handling allowed the surrounding operation to finish.

Why it matters

The findings turn a general compatibility concern into concrete payment outcomes. EIP-8037 proposes higher persistent-data creation costs and separate accounting for state creation and execution, while EIP-8038 updates state access and write costs. Both changes aim to increase throughput while controlling resource demands, but their interaction with existing applications remains under examination.

That matters for applications that cannot easily change deployed code. The open issue is whether transaction success can be separated from the payment guarantees relied upon by immutable contracts.

Market impact

Ethereum's Nov. 16 testing-call agenda includes Juicebox's concerns and proofs of concept within the EIP-8037/8038 investigations. The Foundation's Nov. 9 guidance recommended reviewing public audit findings before deciding on specification changes or the Hoodi testnet schedule, with a further discussion listed for Nov. 19.

No decision has been precommitted. For ETH holders and builders, the immediate focus is whether the proposed protocol rules preserve established payment behavior, since unresolved compatibility concerns can shape the timing and substance of any Glamsterdam changes.

Related tokens
$ETH

Frequently asked questions

  1. What did the Ethereum Glamsterdam simulations uncover?

    They uncovered four tested paths where an outer Ethereum transaction succeeded while an internal Juicebox V6 payment failed under the proposed rules.

  2. Which payment failures appeared in the simulations?

    One path allowed a buyer to retain an NFT without its associated cross-project payment. Another allowed a cash-out without paying the 2.5% fee.

  3. How did the Sepolia results differ from mainnet comparisons?

    The sampled Sepolia simulations produced skipped-payment outcomes, while the sampled mainnet comparisons showed transaction failures or complete delivery across the four paths.

  4. Why could an internal payment fail while the transaction succeeded?

    An internal payment writing fresh storage could exhaust gas before the outer transaction. Contract try/catch handling absorbed that failure and allowed the surrounding operation to complete.

  5. What Ethereum decisions remain unresolved?

    The Foundation has scheduled further discussion for Nov. 19. No decision has been precommitted on specification changes or the Hoodi testnet schedule.

Source attribution
Aggregated from CryptoSlate · Verified · Last refreshed 2h ago
Open original →