For network founders
Your network in the shared endpoint
not one more integration for anyone
We spin up nodes for a new network on request and add it to the catalogue. For the wallets, exchanges and services already running on Settla, a new network is not a new provider and not a new key — it is one more segment in the endpoint they already call.
- 4
- networks in production
- 38
- networks in the catalogue
- 1
- endpoint and key for all of them
The listing
A row in the list our customers already read
This is the real catalogue — the same one behind /nodes. Type your network's name and it takes the first row.
Networks in the catalogue 39
- ?Your networkStatuson requestBlock cadence—Latency—
EthereumStatusrunningBlock cadenceevery 12 sLatency18 ms
SolanaStatusrunningBlock cadenceevery 0.4 sLatency16 ms
BitcoinStatusrunningBlock cadenceevery 10 minLatency31 ms
BaseStatuson requestBlock cadenceevery 2 sLatency—
Arbitrum OneStatuson requestBlock cadenceevery 0.25 sLatency—
OptimismStatuson requestBlock cadenceevery 2 sLatency—
The dashes in your row are not a placeholder — they are the rule this catalogue follows. Height and latency are shown only for networks whose nodes we run ourselves, so nothing here is a promise of a service that does not exist yet. Your row fills in the day the node goes up.
One entry in the registry, and the network shows up inthe home pagethe network cataloguethe explorerspublic endpointsthe segment pagesand the footer of every page.
What we take on
The node is our side of the work
A listed network joins the same machinery that carries the ones already running — with one honest exception.
Nodes and their upkeep
Updates, disks, restarts and monitoring are ours. You do not get a server to look after, you get a network that answers.
Routing and headroom
Requests go through the same layer as every other network: the nearest healthy node, and a switch away from one that stops answering.
The same key, the same address
Nobody has to onboard a second provider. Teams already integrated reach the new network with the key they have.
The explorer comes separately
Blocks, transactions and addresses are not wired up together with RPC: today the explorer covers of our 4 networks. We would rather say so now than have you find out on launch day.
Questions
What founders ask first
Bitcoin, Ethereum, Solana, and Tron. The rest of the catalogue — three dozen networks — sits there as planned: their block cadence is public knowledge and we show it, but our own numbers are blank, because we do not run nodes for them.
Because we only show height and latency for networks whose nodes we operate. Filling those cells before the node exists would be a promise of a service that does not. The row fills in the day it goes up — and until then it is honest about what we know.
Not necessarily. The explorer runs on a separate path into the node, and today it covers 3 of our 4 networks. RPC comes first; the explorer follows when its endpoint is ready.
Nothing they have not done already. A team integrated with Settla reaches the new network through the same endpoint and the same key — the chain segment in the address is the only thing that changes.
Infrastructure shouldn't be the thing slowing you down.
Free to start. No credit card required.