BlazePhoenix-Dex — Verification Report, September 2026

Q: 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

Q: 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.

Q: 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.

Q: 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.

Q: 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.

Q: 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.

Q: 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.

BlazePhoenix

Verification Report September 2026

BlazePhoenix · measured 2026-09-05 · release settings · full text (markdown) · canonical copy in the repository

Scope: the Version 2 tree, which is not deployed. Every figure below was measured on the V2 repository on the project’s CI hardware with release settings. The deployed generation is V1, pinned by codehash on every network so the two are never conflated. The report is Metrological Design applied to the apparatus itself: a number is printed only beside the denominator it was measured against, a floor is called a floor, and what an instrument cannot see is stated.

Abstract

Every instrument of the BlazePhoenix-Dex verification apparatus, measured on one tree on 2026-09-05 and printed beside the denominator it was measured against. The suite: 1,478 declared test functions across 218 files; 1,319 passed, 0 failed, 1 skipped on the release profile with the fork suites excluded; 119 of 119 on live liquidity across five chains; 40 stateful invariants in 14 campaigns. The instruments: a curated mutation guard of 203 mutants, all killed, each paired with the named test that kills it; mutants aimed at the stateful invariants, with the survivors published; regime covering arrays of strength 2 (63 rows, all 258 pairs) and strength 3 (168 rows, all 1,636 triples) under one assertion; a hostile-venue matrix of ten pathologies across two doors, 20 of 20 with no third outcome; canonical oracles exact to the wei on the constant-product curve, within 4 wei on the stable curve and within one ulp of the square-root price on concentrated liquidity; fourteen metamorphic relations; N-version testing of the quote maths compiled at three optimiser settings; the detection rate of every fee mutant under twenty seeds with a Wilson 95 % interval; and how a quote ages — 240 samples of drift and delay on mocks, then live Base. Section 7 states what none of this establishes.

The figures, with their denominators

1,319 · 0 · 1: passed, failed, skipped — release profile, fork suites excluded (1,320 tests)
119 of 119: on live liquidity: 39 fork suites, five chains
203 of 203: curated mutants killed, each by its named test
168 rows: strength-3 covering array: all 1,636 value triples of the regime factors
20 of 20: hostile-venue matrix: ten pathologies × two doors, no third outcome
1 ulp: the concentrated-liquidity oracle against the venue’s own square-root price
20 / 20 seeds: every fee mutant seen by the fuzz seals and the widened Router campaign, Wilson 95 % [0.84, 1.00]
240 samples: a quote executed 0–10 s later under 0–300 bps of adverse drift: settled, refused by the floor, never a third way

Each figure is recomputed from a clean checkout by a named command; the commands are listed in §8 of the report.

What it does not establish

No probability of correctness — testing cannot produce one and none is stated. Mutation adequacy is adequacy against a hand-curated register, so a saturated score is a floor. Threat and regime coverage are floors on what has been named; the drift and delay distributions are over mocks, and live Base gives reach rather than a distribution. These limits are §7 of the report, stated in the same voice as the results.

Companion and context

The swap side alone — quotes, fees, floors, settlements and refusals, on mocks and on live Base — is the Swap Tests report. The protocol the apparatus measures is specified in the aggregator whitepaper; the audit status is stated exactly at /is-blazephoenix-audited.

Cite this document

Mitra. (2026). BlazePhoenix-Dex — Verification Report (September 2026). BlazePhoenix. https://blazephoenix.xyz/verification-report-2026-09.md

@techreport{blazephoenix_verification_report_2026,
  author       = {Mitra},
  title        = {BlazePhoenix-Dex — Verification Report, September 2026},
  institution  = {BlazePhoenix},
  year         = {2026},
  month        = {09},
  note         = {Text CC BY 4.0. Machine-readable text: https://blazephoenix.xyz/verification-report-2026-09.md}
  url          = {https://blazephoenix.xyz/research/verification-report/}
}

DOI: assigned on Zenodo registration — until then cite the URL above; the version and date identify the text. · Machine-readable text: /verification-report-2026-09.md

Questions, a partnership or a bug to report? Contact us or email contact@blazephoenix.xyz