What is new in BlazePhoenix — what makes it different from other DEX aggregators?

The quote and the execution are one computation: the route is derived on chain, inside the transaction that executes it, by the same evaluator that priced it — no server, no oracle, no keeper. Whitepaper v2.3 names eighteen innovations behind this, including the Meta-Equation, Uniswap V4 routed entirely in-frame with hooks screened by address bits, the Iron-Law floor re-derived at execution, and a 0.28% fee with no setter. Map with the mathematics: https://blazephoenix.xyz/learn/the-eighteen-innovations

What is BlazePhoenix ($BZPX)?

BlazePhoenix is a decentralized, autonomous, fully on-chain DEX aggregator on Base, Ethereum, Optimism, Arbitrum and Robinhood Chain, and a single-asset staking engine with solvency enforced on every state-changing call. $BZPX is its fixed-supply token (1,000,000,000) on Base. The price you are quoted is computed by the same on-chain function that settles the swap — compute, do not trust.

How do I swap tokens on Base at the best price?

Connect a wallet at blazephoenix.xyz, pick the pair and amount, set your own max slippage (minOut is always your explicit choice), and execute. The on-chain Solver splits the order across the deepest pools — Uniswap V2/V3/V4, Aerodrome, Velodrome, Camelot, Curve venues — in up to 5 parallel legs, and any surplus above the quote is paid 100% to you.

What is the BZPX airdrop and how do I join?

130,000,000 BZPX (13% of supply) is the Airdrop & Bounties pool, which funds the community airdrop. There is no entry form and nothing to submit: eligibility is measured from on-chain behaviour, so running many wallets gains no advantage over one real user. Rules and the claim contract publish on-chain ahead of the snapshot, announced only on the official channels.

How does BZPX staking work?

Lock BZPX for 90 days to 7 years and earn protocol emission plus borrower interest. Emission is a 180,000,000 BZPX budget on a biennial halving curve — eight periods over sixteen years, 90M then 45M then 22.5M and so on, emitting 179,296,875 in total with 703,125 recoverable afterwards. Longer locks boost rewards up to 2.75×. You can borrow against your own stake with no price oracle anywhere, because collateral and debt are the same token; the limit is 50% of net equity, which works out to a third of the stake, and liquidation only begins at 95%. Solvency is enforced as a revert condition on every transaction and anyone can verify it on-chain for free.

Is BlazePhoenix audited?

No independent external audit has been completed. What exists instead is verification rather than attestation, and the honest picture is asymmetric. The contracts are immutable — no upgradeable proxy, so the code cannot be changed — and source is verified on Base, Ethereum, Optimism and Arbitrum; the Robinhood Chain contracts run executable code byte-identical to the Optimism and Arbitrum ones. Staking solvency is enforced as a revert condition and anyone can read it free at any block (isSolvent(), solvency(), collateralRatio(), auditInvariants()). The router repository gates every merge on two symbolic proofs under Halmos, a static-analysis run that fails on high severity, and a bytecode-size gate stricter than the protocol limit; the staking repository runs neither a prover nor a static analyser. The paid bounty has run nine disclosure waves with thirty-six credited researchers and no critical finding; every confirmed report was reproduced, fixed or documented with its bound, and anchored by a regression test that fails against the pre-fix code. Five are published as advisories at /security/advisories. Verify parameters yourself, always set your own minOut, and never commit more than you can afford to lose.

Which networks does BlazePhoenix support?

Five live chains: Base (home of $BZPX), Ethereum mainnet, Optimism, Arbitrum One and Robinhood Chain. The interface is non-custodial and works with injected wallets, Coinbase Wallet and WalletConnect — no KYC, no allowlist, no off-chain solver.

Slippage, explained: why you got fewer tokens than the screen promised

What slippage actually is, why it happens, what a sandwich attack does to you, and what a real protection looks like — in plain language.

BlazePhoenix Engineering · updated 2026-07-17 · data through 2026-10-11 · 4 min · written from the deployed bytecode

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

Abstract in 15 languages · resumo · resumen · 摘要 · 要旨 · ملخص

English — You confirmed 100 and got 97 — the missing 3 are slippage. Some is natural, some is your size, some is a sandwich bot. Your shield is a minimum enforced by the CONTRACT at execution, not by the website.

Português — Confirmaste 100 e recebeste 97 — os 3 em falta são slippage. Parte é natural, parte é o teu tamanho, parte é um bot sanduíche. O teu escudo é um mínimo imposto pelo CONTRATO na execução, não pelo site.

Español — Confirmaste 100 y recibiste 97 — los 3 que faltan son slippage. Parte es natural, parte es tu tamaño, parte es un bot sándwich. Tu escudo es un mínimo impuesto por el CONTRATO al ejecutar, no por la web.

Français — Vous avez confirmé 100 et reçu 97 — les 3 manquants, c'est le slippage. Une part est naturelle, une part vient de votre taille, une part d'un bot sandwich. Votre bouclier : un minimum imposé par le CONTRAT à l'exécution, pas par le site.

Deutsch — Du hast 100 bestätigt und 97 erhalten — die fehlenden 3 sind Slippage. Teils natürlich, teils deine Größe, teils ein Sandwich-Bot. Dein Schild ist ein Minimum, das der VERTRAG bei Ausführung erzwingt, nicht die Website.

Русский — Вы подтвердили 100, а получили 97 — недостающие 3 и есть проскальзывание. Часть естественна, часть — ваш размер, часть — сэндвич-бот. Ваш щит — минимум, который КОНТРАКТ навязывает при исполнении, а не сайт.

Türkçe — 100 onayladınız, 97 aldınız — eksik 3 kaymadır. Bir kısmı doğal, bir kısmı işleminizin boyutu, bir kısmı sandviç botudur. Kalkanınız, web sitesinin değil SÖZLEŞMENİN yürütmede dayattığı asgaridir.

العربية — أكدت 100 واستلمت 97 — الـ3 الناقصة هي الانزلاق. بعضه طبيعي وبعضه حجم صفقتك وبعضه بوت الساندويتش. درعك حدٌّ أدنى يفرضه العقد عند التنفيذ، لا الموقع.

हिन्दी — आपने 100 कन्फर्म किए और 97 मिले — गायब 3 स्लिपेज हैं। कुछ स्वाभाविक, कुछ आपके आकार से, कुछ सैंडविच बॉट से। आपकी ढाल वह न्यूनतम है जिसे निष्पादन पर कॉन्ट्रैक्ट लागू करता है, वेबसाइट नहीं।

日本語 — 100を確認したのに97しか届かない。消えた3がスリッページです。一部は自然、一部は注文サイズ、一部はサンドイッチボット。あなたの盾は、ウェブサイトではなくコントラクトが実行時に強制する最低受取額です。

中文 — 你确认了 100，却收到 97——消失的 3 就是滑点。有的是自然波动，有的是你的订单规模，有的是三明治机器人。你的盾牌是由合约在执行时强制的最低值，而不是网站说了算。

한국어 — 100을 확인했는데 97을 받았다면, 사라진 3이 슬리피지입니다. 일부는 자연스럽고, 일부는 주문 크기, 일부는 샌드위치 봇 때문입니다. 당신의 방패는 웹사이트가 아니라 컨트랙트가 실행 시 강제하는 최소 수령량입니다.

Bahasa Indonesia — Anda mengonfirmasi 100 dan menerima 97 — 3 yang hilang adalah slippage. Sebagian alami, sebagian ukuran order Anda, sebagian bot sandwich. Perisai Anda adalah minimum yang dipaksakan KONTRAK saat eksekusi, bukan situs web.

বাংলা — আপনি ১০০ নিশ্চিত করলেন, পেলেন ৯৭ — হারানো ৩-ই স্লিপেজ। কিছু স্বাভাবিক, কিছু আপনার অর্ডারের আকার, কিছু স্যান্ডউইচ বট। আপনার ঢাল হলো সেই ন্যূনতম যা সম্পাদনের সময় কন্ট্রাক্ট প্রয়োগ করে, ওয়েবসাইট নয়।

Filipino — Kinumpirma mo ang 100 at nakatanggap ng 97 — ang nawawalang 3 ay slippage. May natural, may dahil sa laki mo, may sandwich bot. Ang kalasag mo ay minimum na ipinapatupad ng KONTRATA sa execution, hindi ng website.

Slippage is the difference between the amount a swap quoted and the amount you actually receive, because the price moved between the quote and the moment the trade executed. You limit it with a minimum output: if the trade cannot deliver at least that, it cancels.

You saw 100 tokens on the screen, confirmed, and received 97. The missing 3 are slippage: the price moved between the moment you looked and the moment your trade landed. Some of it is natural (other people trade too), some of it is your own trade's size (big orders push the price), and some of it is hostile.

The hostile kind is the sandwich attack: a bot sees your pending trade, buys right before you (pushing the price up), lets your trade execute at the worse price, then sells right after — pocketing your loss. It is legal-ish, automated, and constant. Your only shield is the MINIMUM you demand: if the trade cannot deliver at least that, it must cancel instead of executing badly.

What real protection looks like

Weak protection: the website calculates your minimum and the contract obeys whatever the website says — a hacked website can set your minimum to zero. Strong protection: the CONTRACT recomputes the minimum itself at execution, and the website's number can only make it stricter, never weaker. BlazePhoenix does the second — it is called the iron floor, and it goes further: every individual step of your route must deliver at least 80% of its plan, so an attack cannot hide inside one step of an otherwise fine trade.

Practical takeaway: always set a slippage limit you would actually accept (0.5% is sane for major pairs), and prefer venues where the floor is enforced by the contract, not the frontend.

Do not trust this page — reproduce it

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

quote the same trade twice a minute apart — the difference you see IS the market moving; your slippage setting is how much of that you tolerate

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). Slippage, explained: why you got fewer tokens than the screen promised. BlazePhoenix Engineering. https://blazephoenix.xyz/learn/what-is-slippage

@misc{blazephoenix_what_is_slippage,
  title  = {Slippage, explained: why you got fewer tokens than the screen promised},
  author = {BlazePhoenix},
  year   = {2026},
  url    = {https://blazephoenix.xyz/learn/what-is-slippage},
  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).

Related engineering

Share𝕏 Farcaster LinkedIn Discuss on Telegram

Next in Start here · 53 / 56

How to swap tokens safely: a five-minute checklist ›The pre-trade checklist experienced people actually run: verify the site, check the token address, test with dust, set a real slippage limit, and check the pool's real liquidity first.4 min