Glamsterdam review brings application payment paths into focus
Juicebox simulations show why a successful transaction can be an incomplete compatibility test.

The November 16 Ethereum testing-call agenda put EIP-8037 and EIP-8038 compatibility investigations alongside auditor findings and application-team concerns. It explicitly linked Juicebox proofs of concept, with further discussion planned for November 19. These are proposed execution changes under review, not evidence that current mainnet payments are generally failing.
Developer mejango published simulations against Juicebox V6 code, comparing mainnet with Glamsterdam Sepolia rules. Four tested paths could finish their outer action while a cross-project payment or fee was skipped under particular gas limits. The repository describes simulated calls, with no transaction deployed: https://github.com/mejango/glamsterdam-pocs. This edition reviewed the published results; it did not independently reproduce them.
For builders, checking only transaction success is too coarse. A useful compatibility test also checks recipient balances, fee collection and recovery behavior after an inner call fails. That turns the repricing debate into concrete application evidence while keeping simulated outcomes separate from a live incident.