Skip to main content
Chain definitions are JSON files embedded into the binary at build time. The table below reflects those definitions, the same data GET /blockchains returns.
Lisk has no DEX configured, so it appears in the catalogue but cannot be quoted against. Adding one is a chain-definition change. See Adding a chain.

Tokens are a starting set, not a limit

The token counts above are what ships in each chain definition. They are the list the seeder walks when it queries the v2 and v3 factories for real pools, so they determine which pairs get discovered. Widening a chain’s coverage means adding tokens to its definition and re-seeding.

Getting the live picture

The table is the shipped configuration. What can actually be quoted depends on what the seeder found when it ran:
On a self-hosted instance, each chain needs its own <CHAIN>_RPC_URL. A chain with no reachable endpoint gets skipped during seeding with a non-fatal warning, and ends up with no pools. See Configuration.