Glamsterdam Test Shows Why a Successful Transaction May Not Mean Every Payment Succeeded

When testing a contract that makes payments inside a larger transaction, developers need to check the outcome of each payment—not just whether the overall transaction succeeded.

In a November 17, 2026 report citing CryptoSlate, PANews said developers simulated Juicebox V6 contracts on Ethereum’s Sepolia testnet under Glamsterdam upgrade rules. They found four paths in which an internal payment failed even though the overall transaction succeeded. In one example, a buyer kept an NFT while a payment intended for another project was skipped. In another, a user withdrew funds without a 2.5% fee being deducted.

The developers attributed the behavior to gas, the execution resource consumed by contract code. Under the rules being tested, an internal payment that writes to new storage could run out of gas and fail before the outer transaction does. These are test results, not a report that the behavior has occurred on Ethereum mainnet.