0x203a665d203a…203a665a

ConfirmedInfrastructure571 vB75 sat/vB3 min decode

Ethereum tests expose skipped payments under proposed gas rules

Ethereum simulations found successful transactions that skipped project splits and fees under proposed gas rules, reviving compatibility questions for Juicebox and immutable apps.

Ethereum test exposes flaw that lets transactions skip payments
WitnessEthereum test exposes flaw that lets transactions skip paymentsAI-generated

Outputs

  1. The V6 payout test produced successful transactions that skipped a split and left the money with the payer.

  2. A cash-out simulation completed without its fee at sampled gas limits of 679,622 to 817,622.

  3. EIP-8037 proposes higher persistent-data creation costs and separate creation and execution accounting.

  4. The Nov. 16 testing-call agenda lists Juicebox compatibility concerns and proofs of concept.

  5. The Foundation scheduled discussion of the findings and possible next steps for Nov. 19, with no decision precommitted.

At sampled gas limits of 679,622 to 817,622, an Ethereum cash-out simulation reported success without paying its fee, according to developer mejango.

The developer’s tests exercised deployed contract code through eth_simulateV1. Each simulation launched and funded a fresh project. The tests then examined a payment path across different transaction gas limits. Every scenario was pinned to a blockchain block.

The tests produced three notable outcomes:

  • The V6 payout test generated successful transactions that skipped a split to another project. The unpaid money remained with the paying project.
  • A reserved-token distribution completed after a cross-project payment failed. The beneficiary received raw tokens instead.
  • In the cash-out test, gas limits sampled within 679,622 to 817,622 allowed the withdrawal to complete without paying the fee.

Mainnet comparison runs behaved differently. Across the sampled ranges for all four paths, they produced either transaction failures or complete delivery. They did not reproduce the intermediate state in which a transaction succeeded while an internal obligation went unsettled.

The divergence comes from operation order and gas consumption, mejango said. Under the tested Glamsterdam rules, an internal payment that writes fresh storage can run out of gas before the outer transaction does. The contract’s try/catch handling absorbs that failure and lets the surrounding operation finish.

That creates a specific accounting problem for applications built around nested payments. A successful outer receipt can coexist with a failed inner transfer. A recipient may receive raw tokens rather than the intended distribution, or a user may cash out without paying the required fee. The test provides no monetary loss figure, but it does show how proposed gas rules could change the meaning of transaction success.

The simulations extend a broader compatibility warning first raised in early November. They now connect proposed gas behavior to specific payment outcomes from deployed contracts. Developers are weighing whether the protocol changes preserve the guarantees those applications were designed to deliver.

The findings sit inside Ethereum’s active specification work. EIP-8037 proposes higher costs for creating persistent blockchain data and separate accounting for state creation and execution. EIP-8038 updates the costs of accessing and writing state. The proposals aim to support more throughput while controlling resource demands.

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

On Nov. 13, mejango asked whether the impacts fall within the Ethereum Foundation’s tolerance for breaking changes. The developer linked the answer to confidence in building immutable applications whose deployed code cannot be changed in place.

The Foundation’s Nov. 9 update recommended reviewing public audit findings before deciding on specification changes or the Hoodi testnet schedule. It listed Nov. 19 for discussion of the findings and possible next steps. No decision was precommitted.

What does this change for Juicebox?

It puts deployed-contract payment guarantees back under review. Developers must distinguish a completed outer transaction from a completed inner obligation, especially where try/catch handling masks an internal failure. The mainnet comparison narrows the issue to the tested Glamsterdam gas rules, but it does not settle whether EIP-8037 or EIP-8038 should proceed unchanged. The Nov. 19 discussion is the next point at which the Foundation can record a path forward, including any implications for the Hoodi testnet schedule.

via cryptonews.net (Source)

More from Marcus Bennett

Marcus Bennett

Show full bio

Senior reporter covering money, funding and market shifts around crypto and web3 industry at Mempool Brief.

1,456 articles