0x1580535e1580…1580535b

ConfirmedInfrastructure541 vB134 sat/vB3 min decode

Ethereum Developers Set Nov. 19 Review After Sepolia Tests Expose Glamsterdam Payment Bugs

Ethereum developers will review Glamsterdam on Nov. 19 after Sepolia tests found four payment-failure scenarios, including an NFT delivered after a failed payment.

Ethereum Developers Plan Nov. 19 Review of Glamsterdam Test Risks
WitnessEthereum Developers Plan Nov. 19 Review of Glamsterdam Test RisksAI-generated

Outputs

  1. Ethereum core developers scheduled a Nov. 19 meeting to discuss Glamsterdam compatibility issues.

  2. Nov. 14 Juicebox tests on Sepolia found four payment-failure scenarios under EIP-8037 and EIP-8038.

  3. One scenario delivered an NFT after a project payment failed; another waived a 2.5% cash-out fee.

  4. Equivalent tests under current mainnet rules either failed in full or completed in full.

  5. Glamsterdam activated on the Sepolia test network on Oct. 6.

Ethereum core developers will meet on Nov. 19 to review compatibility problems in the Glamsterdam upgrade after Nov. 14 tests on the Sepolia network surfaced four payment-related failure scenarios under two proposed gas-accounting changes, EIP-8037 and EIP-8038.

The tests, run by developers at Juicebox, simulated contract behavior under the proposed changes and found cases where contract actions continued even though payments had failed. The most serious result: in one scenario, a buyer received an NFT after a project payment failed. In another, a cash-out completed without charging a 2.5% fee.

Ethereum activated Glamsterdam on the Sepolia test network on Oct. 6. The Juicebox simulations are the latest in a series of tests examining how the upgrade's gas-accounting revisions interact with existing protocol contracts.

What did the Nov. 14 tests find?

Juicebox developers ran the simulations on Nov. 14 under the gas-accounting changes proposed in EIP-8037 and EIP-8038. They identified four distinct payment-related scenarios, two of which carry direct business consequences:

  • A buyer received an NFT after a project payment failed.
  • A cash-out completed without collecting the 2.5% fee owed to the protocol.
  • Two additional payment-failure scenarios involved failed or skipped project payments.

The control cases tell the sharper story. Equivalent tests run under current Ethereum mainnet rules either failed in full or completed in full. Under the proposed Glamsterdam rules, contracts instead executed partially: payments failed while downstream contract actions proceeded anyway.

That partial-execution pattern is the core operational risk. On mainnet today, a failed payment halts the transaction, and state changes revert together. The Sepolia results suggest the new gas-accounting rules can split those outcomes, letting an NFT transfer or a fee-exempt cash-out persist even when the payment that should trigger or fund the action does not succeed.

Why does this matter for protocols?

The findings affect any protocol whose contract logic assumes atomic payment-and-delivery behavior. Crowdfunding and treasury platforms like Juicebox sit closest to the exposure, because their flows bundle project payments, fee collection, NFT issuance and cash-outs into single transactions.

A waived 2.5% fee is a direct revenue leak for the protocol and its project creators. An NFT delivered on a failed payment is worse: it mints a benefit without the corresponding consideration, and it does so at the contract layer, where no off-process reconciliation can easily claw it back.

Because the equivalent mainnet-rule tests either passed or failed cleanly, the divergence points at the Glamsterdam changes themselves rather than at Juicebox's contract code.

What happens on Nov. 19?

Core developers plan to discuss the compatibility issues at the Nov. 19 meeting and weigh possible changes to the upgrade before it moves further through the test pipeline. The Glamsterdam activation on Sepolia on Oct. 6 remains the reference environment for this work.

The four scenarios from Nov. 14, together with earlier Sepolia simulations covering failed or skipped project payments and a waived fee, give developers a concrete regression set to test any revision against. How developers resolve the partial-execution behavior — by amending EIP-8037, EIP-8038 or the affected contract assumptions — will shape the upgrade's path toward a mainnet schedule.

via tokenpost.com (Source)

More from Tom Whitfield

Tom Whitfield

Show full bio

News editor covering technology and product news in crypto and web3 industry at Mempool Brief.

1,374 articles