Coverage

99 EVM networks. The hard part isn’t the count.

99 EVM networks · 1,000+ DEXs · 465,000+ pools · 10M+ indexed tokens. [Own claim] Any of these numbers can be matched by running more indexers. What can’t be matched by indexing harder is staying in Enso’s Tier 1 while doing it — see Performance.

Read these not as a coverage count, but as the size of the difficulty setting our integrity claim has to survive. The current network list is published live at docs.nordstern.finance/chains — the registry, not a marketing count.

Non-standard tokens are a consequence, not a feature

Fee-on-transfer, rebasing and taxed tokens are supported because our quote is a real simulated transfer, not a formula that assumes a standard one. We don’t maintain a list of “supported non-standard tokens” — if the simulation succeeds, the token is supported; if it doesn’t, the quote fails at request time instead of at your user’s execution time.

• Fee-on-transfer tokens, where the amount that arrives is not the amount that was sent. A router that assumes standard transfer semantics quotes the wrong number by construction.
• Rebasing tokens, where balances change between quote and settlement for reasons that have nothing to do with the trade.
• New and thin tokens, where a pricing formula extrapolates from too little data and a simulation either works or reverts — no in between.

A router that estimates has to special-case every one of these. A router that simulates doesn’t have to know they’re special.

Where we stop

Solana: not supported. We’re EVM-only today. [Own claim] If your flow needs Solana-native routing — or anything else outside the EVM — we’re not the right provider for that leg. We’d rather say so plainly than let a shadow test discover it.