The admin surfaces
The thirteen Swap consoles in the order you actually use them, what each one answers, and how the five navigation groups are organised.
Thirteen screens in five groups. This page lists them in daily-use order rather than menu order — the first few are setup, the rest you open when something needs an answer.
The groups
| Group | Holds | Opened |
|---|---|---|
| Overview | Quote and execution health | Every day |
| Routing | Providers, Chains, Requirements, Wallets | When something will not quote |
| Listings | Tokens, Pairs | When curating what may be swapped |
| Liquidity | Pools, Positions | Only if you provide liquidity yourself |
| Activity | Swaps, Quotes, Fees | When answering a question about what happened |
| Settings | Everything else | Rarely, and carefully |
Liquidity is its own group rather than a part of Listings for a reason worth stating: it is the one place in this addon where your own money is at stake. Listing a token is a curation decision you can undo with a toggle; seeding a pool is a market position only a signed withdrawal reverses.
1. Overview — /admin/dex
- One row per enabled chain
- Four checks, four possible states each
Per-chain readiness as a checklist, not a dot. For every enabled chain it reports four checks — switched on, fee recipient, aggregator coverage, RPC — and each can be OK, missing, unverified or unknown.
The four-valued states are load-bearing. "Unverified" means configured but never exercised; collapsing it into OK is a console reporting readiness it did not measure, and collapsing it into failed cries wolf on a healthy install.
Open it when: something stopped working and you do not yet know what.
2. Providers — /admin/dex/provider
Aggregator activation, priority, covered chains, and the env var each reads its credential from. Test credentials lives here. See Providers.
3. Chains — /admin/dex/chain
The operator overlay on the built-in chain registry: the switch, the fee recipient, the RPC endpoints, the confirmation depth, and the zero-fee acknowledgement.
Rows are seeded from code — the registry supplies the network definitions the wallet adapter needs — so you cannot create or delete a chain here, only configure one.
The Fee status column answers a different question from Enabled: whether swaps on that chain complete and earn. A chain can be switched on and refuse every quote. See Fees and revenue.
The registry now spans four virtual machines — EVM, Solana, TRON and TON — and the VM decides how a token is held and what an approval means. The two screens below exist because of that.
3a. Requirements — /admin/dex/requirements
The screen to open when you do not know which screen to open. It reports, per chain, exactly what is still missing before a swap can be served, separates blocking problems from warnings, and includes a probe that talks to the chain rather than trusting your configuration.
It answers even while the master switch is off, because that switch is one of the things it reports. See Requirements.
3b. Wallets — /admin/dex/wallet
Where the integrator fee lands on each chain, and whether it can actually land there.
On EVM those are the same question. On Solana they are not: an SPL token lives in a token account, one per mint, and each must exist before anything can arrive — so a valid fee address can collect nothing, silently, until the first sweep. See Wallets.
It holds no keys and cannot: the guards make a custodial wallet impossible in this tree.
4. Tokens — /admin/dex/token
The curated allowlist, with three independent axes that are deliberately not collapsed into one:
| Axis | Question |
|---|---|
status |
Have you switched it on? |
listing |
PENDING, ALLOWLISTED or DENYLISTED — your curation decision. |
riskLevel |
What the screener thinks. |
A token must clear all three. Importing a list creates rows that are PENDING
and disabled, and none of them is quotable — importing never allowlists,
because a token list is somebody else's judgement and this is your catalogue.
On-chain decimals() is read at import and a row that disagrees with the list
is refused rather than imported.
5. Pairs — /admin/dex/pair
The featured markets: which pairs appear in the terminal, in what order, with their chart binding. The statistics columns are refreshed by a sweep and are display-only.
6. Swap history — /admin/dex/swap
Every swap with its on-chain status, transaction hash and explorer link. This is the durable record; the terminal's own panel is the live one, and neither is a fallback for the other.
Statuses are worth knowing apart: DROPPED means the transaction left the mempool without confirming, REPLACED means the user's wallet superseded it, and REVERTED means it mined and failed — the user still paid gas. All seven states, all eight reasons and the reorg window are in Swap history.
7. Quote log — /admin/dex/quote
Quotes served, which provider won each route, and why the others lost. Open it when a user reports a price they did not get, or to see whether a provider is being asked and losing versus never answering.
8. Fee ledger — /admin/dex/fee
Accrued, swept and on-chain, plus the reconciliation between them. See Fees and revenue — this is the screen most likely to be misread, because a large accrued figure with nothing in your profit report is the system working correctly.
8a. Pools and Positions — /admin/dex/pool, /admin/dex/position
Only relevant if you provide liquidity yourself. The pool register carries lifecycle, verification freshness, depth and the calldata to create or seed one; Positions reports net versus holding, the quote-asset ledger, and impermanent loss.
Positions is never booked revenue — see LP positions and Direct pools.
9. Settings — /admin/dex/settings
Master switch, fee policy, quote economics, token safety, compliance and the execution poller. Three settings are Super-Admin-only and are shown read-only here with the door named. See Settings.
There is no screen that moves funds, reverses a swap, or signs anything. There cannot be — the platform holds no key for any of it. The most an admin can do is stop offering new swaps.