VERIFY, DON'T TRUST · ALL CHECKS LIVE & FREE
Is BlazePhoenix safe?
BlazePhoenix is non-custodial, fully on-chain software whose every safety claim on this page carries the command that reproduces it — do not take our word for any of it; run the checks.
The protocol is pre-launch and says so plainly: contracts are deployed and verified, the suite is public, an external audit is scheduled, and the honest advice printed on the swap page itself is to prove the path with a small trade first. What follows is each question people actually ask, answered in one sentence and routed to its live check.
Is it a scam?
The engine is built so a scam ROUTE is unrepresentable — and the protocol publishes the instruments to check itself.
Every number on this site carries its reproduction command; the /verified page re-runs the core claims in YOUR browser against public RPCs.
Does it custody funds?
No. BlazePhoenix is non-custodial: the Router holds nothing at rest and every swap settles under a minimum output you sign yourself.
The contract addresses are public and verified — read the bytecode, not the marketing.
Is the staking solvent?
The staking contract answers for itself: isSolvent() is a public on-chain read, enforced as a revert condition on every state-changing call.
Check it right now, free, no account — the page runs the call from your browser.
Has it been attacked?
Yes — by invitation. The open bounty has produced numbered, credited advisories; every confirmed finding was fixed, documented with its bound, or acknowledged before publication.
The BPX register is public, permanent, and mirrored in OSV format.
Is it audited?
An independent external audit is scheduled; until then the honest answer is the verification pipeline that already gates every merge: symbolic proofs, static analysis, adversarial suites, and the public bounty.
Pre-launch honesty: test with a low amount first — the swap page says so itself.
Who is behind it?
A pseudonymous engineering team with a public, falsifiable record: the whitepaper states measured claims, the repositories carry the code, and the author entity is consistent across every surface.
Judge the measurements, not the biography — every measurement is reproducible.
The standing corrections register
When we get something wrong, the correction is published machine-readably at /corrections.json — a site that never corrects itself is a site that never checked.