Solia saysEIP-1153 transient storage (TSTORE/TLOAD) persists within a single transaction and is wiped at the end — cheap mutex state, callback context, and reentrancy guards.
EIP-1153 added TSTORE and TLOAD opcodes for transient storage: 256-bit slots that live for one transaction only and cost 100 gas per access (no init premium). They are perfect for state that needs to survive nested calls within a tx but should not consume permanent storage — reentrancy guards, callback parameter passing, and one-shot mutex flags.
At transaction end the entire transient namespace is wiped automatically, so contracts cannot leak state across transactions through it. The demo shows TSTORE/TLOAD persisting within a tx and disappearing after.
Power-ups you unlock
TSTORE/TLOAD opcodes added by EIP-1153
Slots live for one transaction only
Cost: 100 gas per access, no init premium
Ideal for reentrancy guards and callback context
Automatically wiped at transaction end
The Reentrancy Reaper attacks — common mistakes
Relying on transient storage across transactions (it is wiped)
Using TSTORE for state that should be permanent
Forgetting transient storage is per-account (each contract gets its own)
Treating TSTORE like SSTORE for refunds — there are none
Boss battleWrite a value with TSTORE, read it back within the same transaction, then show TLOAD returns 0 in the next transaction.