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.

Renouncing power without abandoning the protocol: the control/curator split

BlazePhoenix separates CONTROL (parameters, upgrades, funds — renounceable) from CURATION (candidate maintenance — operational), so decentralization does not have to mean neglect. Plus EIP-7702 as a first-class entry path.

Known formally as The One-Way Door in the BlazePhoenix whitepaper.

BlazePhoenix Engineering · updated 2026-07-17 · data through 2026-10-11 · 6 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 — CONTROL (parameters, funds — renounceable forever) is separated from CURATION (pool maintenance, fenced by Hub rules), so decentralization does not decay into neglect; EIP-7702 EOAs are first-class callers.

Português — CONTROLO (parâmetros, fundos — renunciável para sempre) está separado de CURADORIA (manutenção de pools, cercada pelas regras do Hub), para que a descentralização não apodreça em abandono; EOAs EIP-7702 são callers de primeira classe.

Español — El CONTROL (parámetros, fondos — renunciable para siempre) está separado de la CURADURÍA (mantenimiento de pools, acotada por las reglas del Hub), para que la descentralización no degenere en abandono; las EOA EIP-7702 son llamantes de primera clase.

Français — Le CONTRÔLE (paramètres, fonds — renonçable à jamais) est séparé de la CURATION (maintenance des pools, bornée par les règles du Hub) : la décentralisation ne pourrit pas en négligence ; les EOA EIP-7702 sont des appelants de premier rang.

Deutsch — KONTROLLE (Parameter, Gelder — für immer verzichtbar) ist von KURATION (Pool-Pflege, eingezäunt durch Hub-Regeln) getrennt, damit Dezentralisierung nicht zu Verwahrlosung verkommt; EIP-7702-EOAs sind erstklassige Aufrufer.

Русский — КОНТРОЛЬ (параметры, средства — отказ навсегда) отделён от КУРИРОВАНИЯ (обслуживание пулов, ограниченное правилами Хаба), чтобы децентрализация не превращалась в запустение; EOA с EIP-7702 — полноправные вызыватели.

Türkçe — KONTROL (parametreler, fonlar — kalıcı olarak feragat edilebilir) ile KÜRATÖRLÜK (Hub kurallarıyla çevrili havuz bakımı) ayrılmıştır; böylece merkeziyetsizlik ihmale dönüşmez. EIP-7702 EOA'ları birinci sınıf çağırıcılardır.

العربية — الفصل بين السيطرة (المعايير والأموال — قابلة للتنازل نهائياً) والتنسيق (صيانة المجمّعات، مسيّجة بقواعد الـHub) يمنع تحول اللامركزية إلى إهمال؛ وحسابات EIP-7702 مستدعية من الدرجة الأولى.

हिन्दी — CONTROL (पैरामीटर, फंड — हमेशा के लिए त्यागने योग्य) को CURATION (पूल रखरखाव, Hub नियमों से घिरा) से अलग किया गया है, ताकि विकेंद्रीकरण उपेक्षा में न बदले; EIP-7702 EOA प्रथम श्रेणी के कॉलर हैं।

日本語 — CONTROL（パラメータ・資金、永久放棄可能）はCURATION（Hubルールに縛られたプール保守）から分離されています。分散化が放置に腐らないためです。EIP-7702のEOAは第一級の呼び出し元です。

中文 — 控制权（参数、资金——可永久放弃）与策展权（受 Hub 规则约束的池维护）相分离，去中心化才不会腐化为无人维护；EIP-7702 EOA 是一等调用者。

한국어 — CONTROL(파라미터·자금 — 영구 포기 가능)은 CURATION(Hub 규칙에 갇힌 풀 유지보수)과 분리되어, 탈중앙화가 방치로 썩지 않습니다. EIP-7702 EOA는 일급 호출자입니다.

Bahasa Indonesia — KONTROL (parameter, dana — dapat dilepas selamanya) dipisahkan dari KURASI (pemeliharaan pool, dipagari aturan Hub), agar desentralisasi tidak membusuk menjadi penelantaran; EOA EIP-7702 adalah pemanggil kelas satu.

বাংলা — CONTROL (প্যারামিটার, তহবিল — চিরতরে পরিত্যাগযোগ্য) CURATION (Hub নিয়মে ঘেরা পুল রক্ষণাবেক্ষণ) থেকে আলাদা, যাতে বিকেন্দ্রীকরণ অবহেলায় না পচে; EIP-7702 EOA প্রথম শ্রেণির কলার।

Filipino — Hiwalay ang CONTROL (mga parameter, pondo — maaaring talikuran magpakailanman) sa CURATION (pagpapanatili ng pool, nababakuran ng mga panuntunan ng Hub), kaya hindi nabubulok sa kapabayaan ang desentralisasyon; first-class caller ang EIP-7702 EOAs.

"Renounced" usually means one of two things in DeFi: the owner kept a backdoor and renounced theatre, or the owner genuinely left and the protocol slowly rots because nobody can do maintenance. Both outcomes come from bundling every power into one owner key.

BlazePhoenix splits the powers. CONTROL covers everything dangerous — parameter changes, treasury movement, anything that could redirect user funds — and renounceControl() burns it irreversibly. CURATION covers what must stay operational for routing quality: proposing candidate pools to the Hub's fitness contest. A curator cannot touch funds, fees, floors or math; the Hub's eviction rules constrain what curation can even do.

EIP-7702: smart-account UX without a new trust assumption

On the entry side, the Router treats EIP-7702 delegated EOAs as first-class callers: a plain wallet can temporarily behave as a smart account (batching approve+swap in one signature) without the user migrating to a contract wallet or trusting a third-party relayer with custody. The safety properties — iron floor, per-leg floors, surplus routing — are enforced by the Router regardless of what kind of account calls it.

The result is a protocol where the dangerous keys can be provably destroyed while the maintenance path stays alive and fenced. Verify it: call the Router's controlRenounced accessor and check that it returns true, then read what the curator role is actually permitted to call.

Do not trust this page — reproduce it

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

cast call <router> "controlRenounced()(bool)" --rpc-url https://mainnet.base.org — true after renouncement (public flag at src/BlazePhoenixRouter.sol:234, set by renounceControl() at :337-351). The Hub keeps its flag in storage with no getter; its renounceControl() (src/BlazePhoenixHub.sol:419-432) emits ControlRenounced(), and that event is the proof there

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). Renouncing power without abandoning the protocol: the control/curator split. BlazePhoenix Engineering. https://blazephoenix.xyz/learn/control-split

@misc{blazephoenix_control_split,
  title  = {Renouncing power without abandoning the protocol: the control/curator split},
  author = {BlazePhoenix},
  year   = {2026},
  url    = {https://blazephoenix.xyz/learn/control-split},
  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-7702

Related engineering

Share𝕏 Farcaster LinkedIn Discuss on Telegram

Next in Invariants & security · 14 / 17

The Master Conservation Identity: making a hidden shortfall unreachable, not just observable ›One equation the whole staking book obeys — balance + badDebt = net principal + reserves + accrued-unpaid — enforced per-transaction by a conserves guard. A tx that would leak value reverts itself.7 min