Glamsterdam Readiness Clinic: 1:1s with ChainSecurity Engineers @ Devcon

Glamsterdam changes how gas is accounted for, and some contracts will behave differently without a single line of code changing.Our research found that the upcoming Glamsterdam hard fork affects how many smart contracts handle failed calls. We so far identified

13 real-world examples

affected by this change.All week at Devcon, ChainSecurity engineers are running private 1:1 sessions

. Bring your call paths and we'll help you work out whether Glamsterdam affects your protocol, or discuss potential solutions.

Contracts that warrant particular review are those that continue after a failed subcall, for example to record a permanent failure, process batches or switch to a fallback, as well as proxies and intermediaries. Protocol teams should:recalculate the gas their failure paths need under both Osaka and Glamsterdam rulescheck for storage slots that are set and cleared within the same transactionrevalidate fixed gas budgets and thresholds against the proposed costs and gas-accounting rulestest direct and nested subcall failures, including out-of-gas failures across different gas budgets and reservoir balances, and verify that insufficient gas cannot permanently disable retries or invalidate otherwise valid claimsBefore booking, please read the blog to see whether this applies to you:

Glamsterdam Hard Fork: When Spent Gas Comes BackAfter you RSVP here, our team will ping you to schedule your 1:1 and tell you what to share beforehand, so we can come prepared.