TRUST AND VERIFICATION · EVERY LINE LINKED
Trust and verification
BlazePhoenix is an on-chain DEX aggregator with verified contracts, public source code, public CI, a public bug bounty with credited researchers and a whitepaper with a DOI. Each fact below links to the place where you can confirm it yourself.
Like any DeFi protocol, BlazePhoenix carries smart-contract risk. It is mitigated in the open: the swap is non-custodial and reverts unless the amount delivered to you meets the minimum you signed, the code runs through public tests and formal tools in CI, and the bounty invites anyone to break it. The protocol is pre-launch; the audit status is stated below as the repository states it.
Contracts you can read
The Base contracts (Router, Quoter, Staking and the BZPX token) are source-verified on Sourcify with an exact match.
The Ethereum Router and Quoter are source-verified and named BlazePhoenixRouter and BlazePhoenixQuoter on the explorer.
The Optimism Router and Quoter are source-verified on the Optimism explorer.
Every deployed address, per chain and version, is published machine-readably; the /verified page re-checks the code at each address from your browser.
Code and process in public
The contract source is public, under the Business Source License 1.1, which converts to GPL-2.0-or-later on 2030-06-01.
Every push runs public GitHub Actions workflows, including formal tools (Certora Prover, Halmos) and the full test suite.
The SDK, the MCP server and the HTTP API are public repositories as well.
The public repository history starts on 2026-08-12; a daily public dataset of live on-chain checks runs from 2026-08-17.
Security research
A public bug bounty is open; researchers are credited by name, and fixed findings are published as numbered advisories.
The repository publishes a security policy, and the site publishes an RFC 9116 security.txt; the contact is contact@blazephoenix.xyz.
Audit status, as the repository states it: an independent external audit is scheduled before launch.
Authorship and provenance
The technical whitepaper (v2.3, 2026-09-24) has a permanent DOI on Zenodo: 10.5281/zenodo.23084091.
The papers and the corpus carry OpenTimestamps proofs anchored in Bitcoin, verifiable with ots verify.
Official channels are listed on one page; any other domain or address is not BlazePhoenix.
Checks you can run now
The staking contract exposes isSolvent(), a public on-chain read anyone can call at any block.
One script reproduces the site's live claims with curl and jq, or directly against the chain with Foundry.
Where to go next
Swap in the app, integrate with the @blazephoenix/sdk or connect an agent to the MCP server. Answers to the common safety questions: Is BlazePhoenix safe? Models and agents: /reading-guide.md.