EIP-1153 transient storage: route context that cannot outlive the transaction
BlazePhoenix Engineering · updated 2026-07-17 · 5 min · written from the deployed bytecode
Abstract in 15 languages · resumo · resumen · 摘要 · 要旨 · ملخص
English — BlazePhoenix uses EIP-1153 transient storage for reentrancy locks and in-flight route flags: the EVM itself zeroes them at transaction end, making stale-state leaks unrepresentable.
Português — A BlazePhoenix usa transient storage EIP-1153 para locks de reentrância e flags de rota em curso: o próprio EVM zera-os no fim da transação, tornando fugas de estado obsoleto irrepresentáveis.
Español — BlazePhoenix usa almacenamiento transitorio EIP-1153 para bloqueos de reentrada y banderas de ruta en curso: la propia EVM los pone a cero al final de la transacción, haciendo irrepresentables las fugas de estado obsoleto.
Français — BlazePhoenix utilise le stockage transitoire EIP-1153 pour ses verrous de réentrance et drapeaux de route : l'EVM elle-même les remet à zéro en fin de transaction, rendant les fuites d'état périmé irreprésentables.
Deutsch — BlazePhoenix nutzt EIP-1153-Transientspeicher für Reentrancy-Locks und Routen-Flags: Die EVM selbst nullt sie am Transaktionsende — veraltete Zustandslecks werden damit unrepräsentierbar.
Русский — BlazePhoenix использует транзиентное хранилище EIP-1153 для блокировок реентерабельности и флагов маршрута: сама EVM обнуляет их в конце транзакции, делая утечки устаревшего состояния невозможными по построению.
Türkçe — BlazePhoenix, yeniden giriş kilitleri ve rota bayrakları için EIP-1153 geçici depolamayı kullanır: EVM'nin kendisi işlem sonunda bunları sıfırlar; bayat durum sızıntıları temsil bile edilemez hale gelir.
العربية — تستخدم BlazePhoenix التخزين العابر EIP-1153 لأقفال إعادة الدخول ورايات المسار الجارية: تقوم آلة EVM نفسها بتصفيرها عند نهاية المعاملة، فتصبح تسريبات الحالة القديمة غير قابلة للتمثيل أصلاً.
हिन्दी — BlazePhoenix रीएंट्रेंसी लॉक और रूट फ्लैग के लिए EIP-1153 ट्रांज़िएंट स्टोरेज उपयोग करता है: EVM खुद उन्हें ट्रांज़ैक्शन के अंत में शून्य कर देता है, जिससे बासी-स्टेट लीक असंभव हो जाते हैं।
日本語 — BlazePhoenixはリエントランシーロックと経路フラグにEIP-1153トランジエントストレージを使います。EVM自体がトランザクション終了時にゼロ化するため、古い状態の漏出は表現すら不可能になります。
中文 — BlazePhoenix 将 EIP-1153 瞬态存储用于重入锁与途中路由标志：EVM 本身在交易结束时将其归零，使陈旧状态泄漏在构造上不可能存在。
한국어 — BlazePhoenix는 재진입 락과 경로 플래그에 EIP-1153 일시적 저장소를 사용합니다. EVM 자체가 트랜잭션 종료 시 0으로 만들어, 오래된 상태 누출이 표현 자체가 불가능해집니다.
Bahasa Indonesia — BlazePhoenix menggunakan penyimpanan transien EIP-1153 untuk kunci reentrancy dan penanda rute: EVM sendiri yang menolkannya di akhir transaksi, membuat kebocoran status basi mustahil terwakili.
বাংলা — BlazePhoenix রিএন্ট্রান্সি লক ও রুট ফ্ল্যাগের জন্য EIP-1153 ট্রানজিয়েন্ট স্টোরেজ ব্যবহার করে: EVM নিজেই লেনদেন শেষে সেগুলো শূন্য করে দেয়, ফলে বাসি-অবস্থা ফাঁস উপস্থাপনযোগ্যই থাকে না।
Filipino — Ginagamit ng BlazePhoenix ang EIP-1153 transient storage para sa reentrancy locks at route flags: ang EVM mismo ang nagzezero sa mga ito sa dulo ng transaksyon, kaya imposibleng mairepresenta ang stale-state leaks.
A whole class of DeFi exploits is really one bug: state that was supposed to be scoped to a transaction survived it, or was observable mid-transaction by a reentrant caller. Storage-based reentrancy locks work but cost thousands of gas per swap and must be manually reset — and a missed reset is a permanent brick.
EIP-1153 gives the EVM transient storage: TSTORE/TLOAD slots that are automatically zeroed when the transaction ends. Not by convention — by protocol rule. The BlazePhoenix Router uses transient slots for its reentrancy lock and for in-flight route context like the fee-on-transfer flag that tells the settlement path a token bites on transfer.
Why this is a correctness feature, not a gas trick
The gas savings are real (transient ops cost ~100 gas versus thousands for warm/cold SSTORE cycles), but the deeper win is that a whole failure family becomes unrepresentable: there is no code path in which the lock or the FOT flag leaks into the next transaction, because the EVM itself erases them. You cannot forget to clean up state that the protocol cleans up for you.
This is the same design instinct as the iron floor: move the safety property from "our code remembered to do it" to "the chain enforces it".
Do not trust this page — reproduce it
Every claim above is checkable against the chain. Start here:
inspect the verified Router source on Basescan — search for tstore/tload in the assembly blocksContracts are verified on every chain we deploy to — addresses in the protocol manifest. Deeper formal treatment: the whitepaper (PDF). Standards cited: EIP-1153