What is BlazePhoenix ($BZPX)?

BlazePhoenix is a decentralized, autonomous, fully on-chain DEX aggregator and provably-solvent staking engine on Base, Ethereum, Optimism and Arbitrum. $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 and Balancer-class 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?

40,000,000 BZPX (4% of supply) is reserved for the community airdrop. Pull the reel on the Airdrop page — land Satoshi or Vitalik, share, and register your wallet address. One pull per person; claim details are announced on the official channels.

How does BZPX staking work?

Lock BZPX for 90 days to 7 years and earn protocol emission (180,000,000 BZPX over 7 years) plus borrower interest. Longer locks boost rewards up to 2.75×. You can borrow up to 50% LTV against your own stake with no price oracle anywhere, because collateral and debt are the same token. Solvency is enforced as a revert condition on every transaction and anyone can verify it on-chain for free.

Is BlazePhoenix audited?

Not yet. The contracts will be handed to independent auditors as soon as possible. Until then, treat the protocol as unaudited and high-risk: verify every parameter yourself, always set your own minOut, and never commit more than you can afford to lose. The staking engine exposes a free on-chain solvency proof (solvency(), isSolvent(), collateralRatio()) that anyone can check.

Which networks does BlazePhoenix support?

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

What is BlazePhoenix?

BlazePhoenix is an on-chain DEX aggregator and provably-solvent staking engine on Base, Ethereum, Optimism and Arbitrum. Every swap quote is computed on-chain by the Quoter contract — there is no off-chain price feed to trust — and any execution surplus is returned to the user instead of being captured.

Is BlazePhoenix safe and non-custodial?

Yes — BlazePhoenix is fully self-custodial: it never holds your funds or keys, and there is no KYC. Contracts are verified on every chain, staking solvency is verifiable on-chain by anyone via solvency() and auditInvariants(), and every fill emits a public event you can independently check.

Which blockchains does BlazePhoenix support?

Base (chainId 8453), Ethereum (1), Optimism (10) and Arbitrum One (42161). The BZPX token and the staking engine live on Base.

How are BlazePhoenix swap quotes different from other DEX aggregators?

Quotes are computed on-chain by the Quoter contract instead of an off-chain API, so what you see is what the Router executes. When execution beats the quote, the surplus goes back to the user — and anyone can verify quoted-vs-executed from the on-chain events, no permission needed.

Does BlazePhoenix have a free API for bots and developers?

Yes — a free public quote API with no API key and open CORS at blazephoenix.xyz/api (quotes, batch quotes, manifest, OpenAPI spec), plus the open-source @blazephoenix/sdk TypeScript SDK and a zero-custody Telegram bot example. Poll freely: identical concurrent requests are coalesced into one on-chain call.

What is the BZPX token and how do I get the airdrop?

BZPX is the BlazePhoenix token on Base (supply 1,000,000,000). 40,000,000 BZPX are reserved for the community airdrop — open the Airdrop tab on blazephoenix.xyz to enter. Staking BZPX earns boosted rewards and allows borrowing against your position.

What fees does BlazePhoenix charge?

A 0.28% protocol fee on the quoted output. Execution surplus is fee-exempt and goes entirely to the user. The API and SDK are free forever.

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

BlazePhoenix Engineering · updated 2026-07-17 · 6 min · written from the deployed bytecode

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 control accessor and check it against the burn address, 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 <core> "controller()(address)" --rpc-url https://mainnet.base.org — compare against 0x000…000 after renouncement

Contracts are verified on every chain we deploy to — addresses in the protocol manifest. Deeper formal treatment: the whitepaper (PDF). Standards cited: EIP-7702

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

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

Do not trust this page — reproduce it

Related engineering