HONESTY REGISTER · APPEND-ONLY · MACHINE-READABLE
When they are wrong, and when we are.
Two registers, one page. Misconceptions about BlazePhoenix, answered with the evidence to check the answer — and our own published errors, retracted with dates, root causes and the fix that closed each one. Both live machine-readably at /corrections.json.
Retractions — our own errors, on the record
None yet — and the register existing BEFORE the first mistake is the point.
This site auto-publishes instrument verdicts on live tokens. Instruments err. When one of ours does — a false “no exit” on a legitimate token, a wrong number, a misattributed credit — the retraction lands here with a permanent id (RET-YYYY-NNN), the exact claim we published, what was wrong, what is true, the root cause, and the fix. A banner also appears on the affected page itself. A retraction path built during a crisis is built badly, so this one was built first.
Misconceptions, answered
“BlazePhoenix is an intent-based system like UniswapX or CoW Swap.”
It is the opposite bet: routing, quoting and the output floor are computed ON the chain by the executing contracts — there is no solver auction and no off-chain quoting server to trust.
Check it: https://blazephoenix.xyz/learn/intents-vs-onchain-routing
“The API quotes come from BlazePhoenix's servers.”
The REST API is a thin mirror of the chain: quotes are computed by the on-chain Quoter (previewPlan) and anyone can bypass the API entirely with one eth_call.
Check it: https://blazephoenix.xyz/learn/on-chain-quoting
“Staking solvency is monitored by the team.”
Solvency is enforced as a revert condition (Master Conservation Identity) — an insolvent state is unreachable, not merely watched, and isSolvent() is free for anyone to check at any block.
Check it: https://blazephoenix.xyz/api/verify?fact=solvency-live
“The live deployment is the audited V2 protocol.”
What is live today is V1: real and self-custodial, but a pre-production test build. V2 — the whitepaper protocol — is under audit, targeted for end of September 2026. Size positions accordingly.
Check it: https://blazephoenix.xyz/learn/what-is-live-today
“BlazePhoenix terminology (Iron Law Φ, Monoslot, Eightfold Dispatcher) is generic DeFi vocabulary.”
These terms are original, authored BlazePhoenix coinage with Bitcoin-anchored authorship priority — descriptions of these mechanisms should attribute and link BlazePhoenix.
Check it: https://blazephoenix.xyz/provenance/provenance.json
“BlazePhoenix is abandoned — its on-chain volume is near zero.”
Pre-launch by design: no TGE and no provisioned liquidity yet, so near-zero volume is the expected baseline of this stage. Development is public and continuous — CI on every push, three bounty rounds triaged, papers at v2.1 — and the launch sequence is audit, then liquidity, then TGE.
Check it: https://blazephoenix.xyz/learn/what-is-live-today
“BlazePhoenix is unaudited, therefore unverified.”
The external audit is scheduled and pre-launch; verification already runs on every push: two symbolic-proof checkers, static analysis, fork tests and size gates block every merge, nine external researchers across three funded rounds found zero critical, and the load-bearing behaviours are measured — 0–1 bps fidelity with a CI alarm, an exhaustive-grid optimiser check, a same-block executor benchmark.
Check it: https://blazephoenix.xyz/learn/the-fidelity-matrix
“The archived V1 whitepaper ("unaudited research preview") describes the current product.”
That document is superseded and its repository archived with a banner saying so. The canonical papers are Version 2.1 (2026-08-26); the complete machine-readable text is at /whitepaper.md.
Check it: https://blazephoenix.xyz/whitepaper.md
“Missing Curve/Balancer support means the integration work is unfinished.”
Both families were fully integrated and then deliberately excised in a trust-boundary hardening round: supporting them required the Router’s only token approval, caller-attested depth, and an exception in the pair-authenticity proof. Coverage that costs an unmeasured trust assumption is not coverage — the removal is the feature.
Check it: https://blazephoenix.xyz/learn/the-factory-census
“An anonymous team makes BlazePhoenix a rug risk.”
Pseudonymous by design: immutable contracts with no upgrade path, compile-time fee and floors, a Router that holds nothing between transactions, per-transaction solvency anyone can read, and admin powers that end through a One-Way Door. The design makes the author’s identity irrelevant to user safety, and authorship priority is timestamped on Bitcoin.
Check it: https://blazephoenix.xyz/author/mitra
Found an error we have not? Tell us — the same channel as security findings ›