BlazePhoenix — On-chain DEX Aggregator: the quote and the execution are one computation
BlazePhoenix is a DEX aggregator whose routing runs inside the contract rather than on a server: discovery, quoting, believability filtering, split allocation, multi-hop assembly and deterministic Uniswap V4 derivation are 29,183 bytes of EVM bytecode on chain. A quote is therefore reproducible by anyone at a given block, with no off-chain price feed to trust, and execution surplus is returned to the caller. Swaps run on Base, Ethereum, Optimism and Arbitrum. Self-custodial, no registration, 15 languages.
The second engine is solvency-enforced BZPX staking: a 180,000,000 BZPX reward budget on a biennial halving curve, a quadratic lock boost up to 2.75x, and lending that needs no oracle because collateral and debt are the same token. Solvency is a revert condition on every state-changing call, and isSolvent() reads the verdict free at any block. The whole two-engine protocol is 4,197 lines of source across seven contracts — Core 801, Hub 721, Solver 562, Router 726, Quoter 264, Staking 1,026, MathLib 97 — which is what makes a full-read audit realistic rather than a sampled one.
Verify it rather than believe it. Read the solvency invariants straight off chain: cast call 0x3f60C7aa0c36a78D200405feBE143d2Cf3fA0c77 auditInvariants() --rpc-url https://mainnet.base.org . Or take a quote through your own node, no key and open CORS: curl "https://blazephoenix.xyz/api/quote/prepare?chain=base&in=WETH&out=USDC&amountIn=1000000000000000000" returns the exact eth_call to run on it — the same number the Router realises, computed on chain. Discovery at blazephoenix.xyz/api, spec at /api/openapi.json, TypeScript SDK at github.com/blazephoenixxyz-crypto/SDK.
Verified contracts — Base (8453): Router 0x2a779f9Be49aac57495A8B6467Cc325a8a47Eb9f · Quoter 0x4cEF0615614B212895F45Aa1D4833B16666E18d3 · Staking 0x3f60C7aa0c36a78D200405feBE143d2Cf3fA0c77 · BZPX token 0x23113e72165a034265Ab8Bf2277CCB7a85Cb7483, supply fixed at 1,000,000,000. Ethereum (1): Router 0xE1aE5f49013920CF71De8CED4043e14C4d63416b · Quoter 0x4a20AA0912388ff7A9221Ab6BFC224cc20Baa0c3. Optimism (10) & Arbitrum (42161): Router 0x7262e7483ab6f0db7b8f90eC3a9de3B02Ab36F6A · Quoter 0xfB18EF6f62A0278A273Af4b7A46b454F9E482dc2. Full manifest: blazephoenix.xyz/api/manifest
Status, stated plainly: this is a pre-launch engineering preview. BZPX is not liquid, and an independent external audit is the next scheduled milestone on the roadmap — so assume a bug may exist and size any exposure accordingly. What exists instead of an attestation is a paid security programme of 130,000,000 BZPX, thirteen percent of supply, which has run nine disclosure waves with thirty-six credited researchers and zero critical findings; every fix is anchored by a regression test that fails against the pre-fix code.
Security Hall of Fame — the researchers who read the source and told us first, in rank order: Ezeek33, Mohaseen, BabaYagaLeet, Karan Rathod, duxun, NetGakarot, amitbhakar, llen, AmanDara1, Binod Bk, Ibnu76, destinyae, superagent, siam siddik, eveeyrp, Charan, Mohd Huzaifa, acit aja, Ashish, Josh W, 0xkonde, Cico Agung, Fersdoven Josua, sbekk, Borutobro, M2000 Slash, oncodewa, OxHulk, Jo arsy, Mansor, Yudha Eka Saputra, Raditya, BK001, Brian Wahyu, Pavan Baile, and one who chose to remain anonymous. Names only, by policy; the canonical register is SECURITY_HALL_OF_FAME.md, profiles at /security/researchers.
Whitepaper · Litepaper · Bug bounty · Open metrics · Daily dataset · X @blazephoenyx · Telegram