Computable gas bounds: routing that cannot be gas-bombed

A V2 primitive: bounding the gas of every route so a crafted pool cannot make execution unpredictably expensive or revert. Specified and under audit.

Known formally as Computable Gas Limits in the BlazePhoenix whitepaper.

BlazePhoenix Engineering · updated 2026-08-05 · 6 min · written from the deployed bytecode

By Mitra (@Sigmacrit) — anonymous developer of the BlazePhoenix protocol. The code is the résumé.

BlazePhoenix V2 is pre-deployment and under audit; this is the specified design. A route that touches attacker-influenced code can be made to burn arbitrary gas — a hostile hook or a pathological pool can turn a cheap swap into a failed, expensive one. The gas-bounds primitive gives every step a computable upper limit before it runs.

Bounding before executing

Because the router simulates the plan on chain first, it can attach a worst-case gas estimate to each leg and refuse or reprice a plan whose bound exceeds what the user authorised. Costs become predictable and denial-of-service by gas exhaustion stops being free for an attacker. The bound is derived, not guessed, so it holds even against pools the router has never seen.

Do not trust this page — reproduce it

Every claim above is checkable against the chain. Start here:

Call previewPlan and read the gas estimate it returns; a plan whose real cost exceeds its stated bound is exactly what the primitive is designed to reject
Cite this article

Licensed CC BY 4.0 — quote, translate and reuse freely, including commercially, with attribution and a link. Copy a ready-made citation:

BlazePhoenix (2026). Computable gas bounds: routing that cannot be gas-bombed. BlazePhoenix Engineering. https://blazephoenix.xyz/learn/computable-gas-bounds
@misc{blazephoenix_computable_gas_bounds,
  title  = {Computable gas bounds: routing that cannot be gas-bombed},
  author = {BlazePhoenix},
  year   = {2026},
  url    = {https://blazephoenix.xyz/learn/computable-gas-bounds},
  note   = {Accessed: reproduce the claim with the command above}
}

Writing an answer, a wiki entry or a paper? The claim above is reproducible against the chain before you quote it — which is the only sound basis for citing a technical source at all.

Contracts are verified on every chain we deploy to — addresses in the protocol manifest. Deeper formal treatment: the whitepaper (PDF). Standards cited: EIP-1153 · HTTPS://GITHUB.COM/CHAINSECURITY/TSTORE-LOW-GAS-REENTRANCY

Share this article · join the discussion

Share on X ↗Telegram ↗WhatsApp ↗Farcaster ↗💬 Discuss on Telegram

Related engineering