# Why BlazePhoenix needs to trust less

> Canonical: https://blazephoenix.xyz/learn/why-blazephoenix-trusts-less/
> License: CC BY-NC-ND 4.0 (attribution + link) · © 2026 BlazePhoenix
> Updated: 2026-10-22

Trust less, not more, in plain words: BlazePhoenix finds pools by calculating their addresses instead of keeping a phone book, plans routes inside the contract instead of on a company server, counts what actually arrived before finishing a trade, and writes down the trust that remains as a stated policy with a 48-hour notice.

Every system that moves money trusts something. The question is how much. BlazePhoenix follows one rule: trust less, not more. The goal is not a longer list of things the system relies on, but needing fewer of them to work.

Four habits put that rule into practice. Each one is in the contracts of the 2.0.0 generation, which launches on 15 December 2026 and is not deployed yet.

## 1. Finding pools by calculation, not by a phone book

Imagine a town where every house number follows from the street plan. You do not need a phone book that someone could edit; you can work the number out yourself. Many exchanges create their pools in a way that makes the address computable from the factory and the two tokens (a method called CREATE2), and BlazePhoenix computes it the same way. For BlazePhoenix, an address of this kind is a calculation from the factory, the two tokens and the creation code.

BlazePhoenix also keeps a registry, like a list of shops you visited recently. It is a shortcut to save effort, not the truth: it replaces the search when at least three curated entries for the pair were busy within the last hour. Otherwise the contract searches again.

## 2. Planning the route inside the contract

Many apps ask a company server for the best route and then ask you to trust the answer. BlazePhoenix's route planner, the Solver, is a contract. Your wallet or app asks it with a read-only call to the chain, so the plan comes from public code, not from someone's server.

## 3. Counting the change at the till

A careful shopper counts the change instead of trusting the receipt. The Router does the same: it measures how many tokens actually arrived, at each step and at the end, and compares that with two limits. One is the minimum you set. The other comes from its own price reading inside the same transaction. The minimum you send can make the check stricter, never looser. If a limit is missed, the whole trade is undone.

## 4. Saying out loud where trust remains

Some venues need a special adapter, and some Uniswap V4 pools run extra code called hooks. Here BlazePhoenix does keep a trust policy, and it says so. It works like a guest list with notice: a new adapter is announced, waits 48 hours, and is accepted after that, while a misbehaving one can be removed at once. On the automatic route, hooks that are not on the list are not offered.

So the search removes hand-kept address lists, but admitting certain venues is still a declared decision, with a waiting period anyone can watch.

## What this does not mean

It does not mean any exchange works automatically. A new kind of exchange still needs an adapter and configuration before BlazePhoenix can use it. And trusting less is not the same as trusting nothing: the remaining trust is written down, so you can check it.

The advanced version of this article names each function and constant, and two more explain the gated venues in detail.

**Verify it yourself:** git clone https://github.com/blazephoenixxyz-crypto/Blaze-Phoenix-Dex && cd Blaze-Phoenix-Dex && grep -n 'MIN_FRESH_VENUES\|DISCOVERY_TTL_SECONDS' src/BlazePhoenixSolver.sol && grep -n 'ADAPTER_DELAY' src/BlazePhoenixGate.sol

Related: https://blazephoenix.xyz/learn/trust-minimised-routing/ · https://blazephoenix.xyz/learn/gated-pools-permissioned-venues/ · https://blazephoenix.xyz/learn/gate-vitality-adapter-depth/ · https://blazephoenix.xyz/learn/custody-explained/ · https://blazephoenix.xyz/learn/how-to-read-a-quote/
