Test a transient storage lock across calls in one transaction
A transient slot survives a return from an internal call frame when the write succeeds. A test that issues only isolated transactions can miss a lock left behind by a contract.
Exercise a sequential multicall
In a local test harness, invoke a guarded function on contract A twice through one multicall. If the first invocation sets a transient lock and returns without clearing it, the second invocation sees the set lock. Two separate transactions start with fresh transient storage.
multicall → A.guarded() → return
→ A.guarded() → read previous lock
Add a regression case for cleanup on the successful path. A reverted frame rolls back its writes, so cover caught failures separately when the parent continues executing.
Track the storage owner under delegation
Like persistent storage, transient storage belongs to the caller’s context under DELEGATECALL. Libraries used by one proxy may share slot keys. Give independent guards appropriately scoped keys and run the test on an EVM fork that supports TLOAD and TSTORE. eips.ethereum.org EIP-1153