Chains
Which chains are live, their slugs, and how to discover new ones programmatically.
Each chain has a slug you put in the URL path. Slugs are stable; we will never rename one on you.
Live list (programmatic)
The table below is a snapshot. The source of truth lives at:
It returns every enabled chain with its slug, display name, native chain
id, architecture, live status and public endpoint. Hit it from CI or your
bootstrap script to discover new chains automatically. Entries with
"comingSoon": true are announced but not routed yet.
Example entry:
Current snapshot
| Slug | Chain | Chain ID | Endpoint | WebSocket |
|---|---|---|---|---|
monad | Monad | 143 | https://infra.originstake.com/monad/evm | no |
pharos | Pharos | 1672 | https://infra.originstake.com/pharos/evm | yes |
story | Story | 1514 | https://infra.originstake.com/story/evm | no |
viction | Viction | 88 | https://infra.originstake.com/viction/evm | yes |
stable | Stable | 988 | https://infra.originstake.com/stable/evm | no |
ethereum | Ethereum | 1 | https://infra.originstake.com/ethereum/evm | no |
tron-mainnet | Tron | 728126428 | https://infra.originstake.com/v1/tron/mainnet/ (see /tron) | n/a |
solana | Solana | mainnet | https://infra.originstake.com/v1/solana/mainnet (see /solana) | yes |
All are mainnets. Archive, debug_* and trace_* availability depends
on the upstream nodes behind each chain; where only some upstreams serve
a method, requests for it are routed to those.
Chain page reference
For deeper detail on any single chain (status, latency, request volume):
Example: https://endpoint.originstake.com/api/public/chains/pharos.
The same data is shown on the public dashboard at
https://endpoint.originstake.com/chain/<slug>.
URL examples per chain
Pharos (EVM, chain id 1672)
A successful eth_chainId returns 0x688 (1672 in hex), confirming you
are on Pharos.
Requesting a new chain
We add chains based on demand. To request one:
- Open the dashboard at endpoint.originstake.com/dashboard.
- Use the Feedback widget, or email us with the chain name and a short note about your use case.
If you are willing to bring your own upstream URL, mention it. That shortcuts our onboarding.