TLOAD and TSTORE provide contract state for communication within one transaction. Their lifetime differs from both ordinary memory and persistent storage.

What the primary record establishes

EIP-1153, created on 15 June 2018 and marked Final, defines TLOAD and TSTORE. Transient values are discarded after every transaction rather than serialized to persistent storage. Ethereum — EIP-1153, Final ↗

The specification describes communication among execution frames, including a contract being re-entered within the same transaction. It also sets rollback behavior when a frame reverts. Ethereum — EIP-1153, Final ↗

What the distinction changes

This gives a reentrancy lock a different lifetime from ordinary call memory. It does not make the lock a permanent account setting or preserve it for tomorrow’s transaction.

Application correctness still depends on setting and clearing values at the right points. Transaction-wide availability can matter when several operations share one transaction.

What to check before drawing a conclusion

Review which contract owns the transient state and which execution paths revert. A generic claim that all temporary data behave like memory would miss the cross-frame use case.

The specification is historical, not a newly announced October upgrade. Its benefit is a particular state mechanism; security claims require examining the complete control flow and cannot be inferred from the presence of TSTORE alone.