Ethereum's Glamsterdam Upgrade Testing Reveals Payment Bugs
Written with artificial intelligence.

Testing of Ethereum's Glamsterdam upgrade has uncovered potential issues where internal payment operations may fail despite a transaction being successful overall. Developers identified four scenarios during simulations on the Sepolia testnet, highlighting concerns related to gas consumption during code execution.
Testing Findings
Recent tests on the Ethereum Glamsterdam upgrade have revealed significant bugs that could affect payment operations within successful transactions. Conducted using the Juicebox V6 contract on the Sepolia testnet, developers found that certain internal payment operations could fail even when the main transaction completed successfully.
Identified Scenarios
Developers documented four specific scenarios where this issue could occur:
- A buyer successfully retains an NFT, but funds intended for another project are skipped.
- A user successfully withdraws funds, yet a 2.5% fee is not deducted as expected.
Causes of the Issue
The developers attributed these failures to gas consumption during code execution. Under the new rules of the Glamsterdam upgrade, internal payments that write to new storage may exhaust gas before the main external transaction is completed, leading to errors. The contract's built-in try/catch error handling mechanism can obscure these errors, resulting in the main transaction appearing successful despite the internal failures.
Mainnet Comparison
In contrast, tests conducted on the mainnet did not exhibit the same issues, as all four identified paths resulted in either direct transaction failures or complete delivery, without any skipped payments. This discrepancy highlights the need for further investigation before the upgrade goes live.
