Requirements
The screen to open when a chain will not quote. It names the missing piece per chain, distinguishes blocking from merely worth-knowing, and probes the chain instead of trusting your configuration.
/admin/dex/requirements. Every other screen in this addon assumes you already
know which one to open. This one is for when you do not: something will not
quote, or a chain is dark, and you need the diagnosis rather than a hunt.
It reports, for every chain in this build's registry, what that chain still needs before it can serve a swap — plus the chain-independent settings that gate all of them.
Every list route in this addon refuses while the master switch is off. This one does not, deliberately: the master switch being off is one of the things it reports. A diagnostic that goes quiet exactly when you are trying to turn the product on is worse than no diagnostic.
What it checks
- Press Test to talk to the network
Two layers, and they fail differently.
Global
The chain-independent gates. If one of these is wrong, no chain works and there is no point reading the per-chain list underneath:
- The master switch
- Fee policy — a fee configured above what a provider will accept refuses every quote on every chain
- Aggregator activation, and which credentials are missing from the environment
Per chain
Blocked chains are listed first, because you opened this page because something is wrong. For each chain:
| Check | Blocking? | What "missing" means |
|---|---|---|
| Enabled | Yes | The chain is switched off in Chains |
| RPC endpoint | Yes | Nothing resolved — no override set and no fallback available |
| Aggregator coverage | Yes | No active provider quotes this chain |
| Fee recipient | Depends | Missing means swaps work and earn nothing |
| Token account (Solana) | Yes, per mint | See Wallets |
Warnings that are true but not blocking are separated from the blockers. Mixing the two is how a console trains an operator to ignore it.
The probe
- Press Test to talk to the network
The report so far is your configuration. The probe is the chain.
Test talks to the network and comes back with what it actually found. This is the difference between "an RPC URL is set" and "an RPC URL answers" — and those two states look identical on every other screen in the product.
Run it after:
- editing
.envand restarting - adding or changing an RPC provider
- enabling a chain for the first time
- any report of "it worked yesterday"
What it will never show you
No endpoint URL, no API key, no secret. It reports presence and a sanitised host, and nothing else.
That is not caution for its own sake: the common RPC providers embed the API key in the URL path, so a console that displayed "your RPC endpoint" would be displaying a credential to anyone with read access to this screen.
Reading it in order
-
Fix the global block first. A master switch or a fee policy that refuses every quote makes the whole per-chain list misleading.
-
Take the top chain in the list. They are sorted worst-first, so the top row is the one costing you most.
-
Probe before you change anything. The report is what you configured; the probe is what is true. They disagree more often than you would expect, and the disagreement is usually the answer.
-
Re-check the fee status. A chain can be fully unblocked, serve swaps happily, and earn you nothing — that is a separate column and a separate fix. See Fees and revenue.