Meta Force Space
BTC $65,008.00 +0.09% ETH $1,831.77 +0.69% SOL $72.65 +1.01% XRP $0.9664 +0.50% BNB $594.05 +0.39% DOGE $0.0594 +0.63%
← Back to the news

Ethereum test exposes flaw that lets transactions skip payments

Quick Take

  1. Developer-published Juicebox V6 simulations report four paths where transactions succeed while internal payments fail under tested Glamsterdam rules.
  2. The sampled mainnet comparison shows transaction failures or complete delivery across those paths, with no skipped-payment band reported.
  3. Ethereum's Nov. 16 testing agenda includes Juicebox's findings, while the Foundation's earlier guidance lists Nov. 19 for further discussion.

Tests of Ethereum's proposed Glamsterdam upgrade show that a transaction can succeed while a payment inside it fails, according to developer-published simulations of Juicebox V6's project-payment contracts.

Four tested paths produced that outcome in the developer's simulations on the Sepolia test network, giving core developers concrete examples of how the changes could alter application payment guarantees.

The Nov. 14 runs examine Juicebox V6 contracts that route payments between projects. Their published results include a buyer keeping an NFT while its associated payment to another project fails, and a cash-out completing while a 2.5% fee is forgiven.

A successful Ethereum receipt can miss a payment

The developer mejango says the tests use deployed contract code through eth_simulateV1. A fresh project is launched and funded inside each simulation, then a payment path is tested across different transaction gas limits. Each scenario is pinned to a blockchain block.

The V6 payout test reports successful transactions that skip a split to another project, leaving that 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 band let the withdrawal complete without paying the fee.

The mainnet comparison runs show only transaction failures or complete delivery across the sampled ranges for all four paths.

The distinction comes from which operation runs out of gas first, according to the developer's explanation. Under the tested Glamsterdam rules, an internal payment that writes fresh storage can fail before the outer transaction does.

The contract's try/catch error handling absorbs that failure and lets the surrounding operation finish.

Transaction success can hide a missed fee

Developer-reported Juicebox V6 simulations dated Nov. 14 compare cash-out outcomes on mainnet and Glamsterdam Sepolia.

Compare the developer's cash-out tests

In the reported skip band, the cash-out completes while its internal fee fails. These are simulated outcomes.

In these simulations, transaction status and internal payment delivery are distinct outcomes.

Developer simulations, not independently reproduced. Tested paths and gas samples only; no live incident or network-wide exposure established.

Sources and evidence

Sources

  1. Developer's Sepolia simulation output
  2. Developer's mainnet comparison output
  3. Developer's methodology and mechanism
  4. Repository history and run date
  5. V6 test revision and methodology

Supporting facts

  • Developer mejango's November 14 committed Juicebox V6 simulations report four paths where an outer transaction succeeds while an internal payment fails under the Glamsterdam rules on Sepolia. [3] [1] [4] [5]
  • In the developer's Sepolia cash-out sweep, sampled gas limits in the reported 679,622 to 817,622 band let cash-out succeed while its 2.5% fee payment fails and the fee is forgiven. [1]
  • The developer's mainnet comparison output shows each of the four tested paths reverting or delivering everything within the sampled gas ranges, with no skipped-payment outcome band. [2] [3]
  • The developer attributes the difference to an internal payment writing fresh storage exhausting gas first under Glamsterdam, with try/catch handling that failure while the outer transaction completes. [3] [5]
  • The simulations provide project-specific examples of payment guarantees changing under the tested rules, but do not establish a live theft, exposed-funds total or network-wide prevalence. [1] [2] [3]

Method

Schematic flow based on the developer's published V6 cash-out and comparison runs. Branches show outcomes, not amounts or probabilities. The Sepolia sweep used 2,000-gas steps; the reported fee-skip band is 679,622 to 817,622 gas. No independent reproduction or derived values.

Scope

Developer simulations, not independently reproduced. Tested paths and gas samples only; no live incident or network-wide exposure established.

Infographic by CryptoSlate

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. Those changes aim to support more throughput while controlling resource demands.

Ethereum's Nov. 16 testing-call agenda explicitly lists Juicebox's compatibility concerns and proofs of concept within the EIP-8037/8038 investigations. The findings are intended to inform Thursday's execution-layer discussion.

In a Nov. 13 comment on that agenda, mejango asked whether the impacts fall within the Ethereum Foundation's tolerance for breaking changes, linking the answer to confidence in building immutable applications whose deployed code cannot be changed in place.

The tests advance the broader compatibility warning from early November, with specific payment outcomes from deployed contract code. They leave developers weighing whether proposed protocol rules preserve the guarantees those applications were built to deliver.

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 discussion of findings and possible next steps, with no decision precommitted.

Editorial credits

Liam 'Akiba' Wright
Liam 'Akiba' Wright
Editor-in-Chief CryptoSlate

Also known as "Akiba," Liam Wright is a reporter, podcast producer, and Editor-in-Chief at CryptoSlate. He believes that decentralized technology has the potential to make…

Gino Matos
Gino Matos
Reporter CryptoSlate

Gino Matos is a law school graduate and a seasoned journalist with six years of experience in the crypto industry. His expertise primarily focuses on the Brazilian blockchain…

Originally published by CryptoSlate on

Read the original on CryptoSlate ↗

Text and images are the property of CryptoSlate and are reproduced here with attribution and a link to the original publication.

More stories

All the latest news