Skip to content
AnnouncementSomnia Oracle settles event contracts onchain, in minutes, with receipts.

Dedicated RPC

Reserved RPC capacity for systems that act on every block.

Somnia Dedicated RPC will place nodes reserved for your organisation’s traffic next to the Somnia network, in the regions where markets run. Your systems will no longer share rate limits with the rest of the network, and every request will take a direct path to the chain.

Join the waitlist
Request pathYour serverSomniaDedicated nodeHTTPS · WSSColocated
realtime_sendRawTransactionIllustrative
Request
curl https://acme.rpc.somnia.network \ -d '{"jsonrpc":"2.0","id":1, "method":"realtime_sendRawTransaction", "params":["0x02f8…c1"]}'
Response
{ "jsonrpc": "2.0", "id": 1, "result": { "status": "0x1", "blockNumber": "0x1a8b…", "transactionHash": "0x8f2c…41d9" } }
Region
Global
Round trip
TBC
Returns
Mined receipt
Chain ID
5031
Somnia mainnet
Block time
100 ms
Ten blocks a second
Finality
Sub-second
Per docs.somnia.network
Public RPC
Shared endpoint
api.infra.mainnet.somnia.network

Network facts from docs.somnia.network (Network Info, JSON-RPC API), October 2026.

Public endpoints get you started. Dedicated nodes keep you fast.

Somnia’s public RPC is shared by every wallet, bot and indexer on the network. When your systems quote, index or settle on every block, you want capacity nobody else can use.

Shared endpoint

Suited to testing, wallets and light reads. Listed in the docs alongside PublicNode, Stakely and Validation Cloud.

Capacity
Shared with everyone on the network
Rate limits
Public limits apply
Placement
One global endpoint
Access
Open to anyone
Streams
WebSocket at /ws
Upkeep
You or a provider
https://api.infra.mainnet.somnia.network

Your own nodes

For teams whose systems read and write on every block and cannot share a request queue with other traffic.

Capacity
Reserved for your organisation
Rate limits
Sized to your workload; plans TBC
Placement
Global first, then Regional Subchains as they launch
Access
Private endpoints and IP allow-lists
Streams
Subscriptions to blocks, logs and order events
Upkeep
Will be managed and upgraded with every network release
Join the waitlist

Monitor every request in Somnia Explorer.

Requests, latency and capacity will appear alongside the rest of your Somnia account. Teams will be able to copy endpoints, manage the allow-list and review which methods their systems call most.

Dedicated RPCacme-markets

Illustrative data

Overview

acme-markets · Global · 2 dedicated nodes

Healthy
Requests · 24 h
18,402,316
HTTPS and WebSocket
Capacity used
42%
Of reserved throughput
Median latency
TBC
Measured per region
Open subscriptions
126
Blocks, logs, events

Requests per minute

1 h6 h24 h

03:0005:0007:00Now

Top methods

Share of requests

  • eth_call46%
  • eth_getLogs21%
  • realtime_sendRawTransaction18%
  • eth_subscribe9%
  • Other6%

Endpoints

HTTPS
https://acme.rpc.somnia.network
WSS
wss://acme.rpc.somnia.network/ws
Chain
5031 · Somnia mainnet
Copy endpointRotate key

IP allow-list

3 addresses

  • 203.0.113.10Allowed
  • 203.0.113.11Allowed
  • 198.51.100.24Allowed

+ Add address

Console layout, names and figures are illustrative; final console scope TBC. IPs use documentation ranges.

What you get with a dedicated RPC

Somnia will provision, monitor and upgrade the nodes with every network release, so your team builds against an endpoint rather than operating one.

  • Private endpoints

    HTTPS and WebSocket endpoints reserved for your organisation.

  • Regional placement

    Nodes in the regions where markets run, starting globally and adding Regional Subchains as they launch.

  • WebSocket subscriptions

    Blocks, logs and order events delivered as they occur.

  • Realtime submission

    Submit a transaction with realtime_sendRawTransaction and receive the mined receipt in a single round trip.

  • IP allow-lists

    Endpoints will accept traffic only from addresses you approve.

  • Usage in Somnia Explorer

    Requests, latency and capacity, reported alongside the rest of your Somnia account.

  • Archive and trace methodsTBCFull history and debug tracing on dedicated nodes.
  • Uptime commitmentTBCService levels and support hours per plan.
  • Capacity tiersTBCThroughput, connections and pricing per region.

Placed where the markets run.

Nodes will run alongside the Somnia network, starting with the global chain and adding Regional Subchains as they launch, so reads and writes travel the shortest available path to the chain.

How Regional Subchains work
  1. GlobalAt launchStatusLive
    1. Private endpoint
    2. Node · Global
    3. Global L1
  2. TokyoAs the subchain launchesStatusTestnet
    1. Private endpoint
    2. Node · Tokyo
    3. Tokyo Subchain
  3. New YorkBeing exploredStatusBeing explored
    1. Private endpoint
    2. Node · New York
    3. New York Subchain

Region order from the live Dedicated RPC page. The launch date for Tokyo, and round-trip times per region, are TBC.

From waitlist to your own endpoint.

Onboarding will take four steps and requires no hardware on your side. Existing code will continue to work; only the RPC URL will change.

  1. 01

    Choose

    Select the region and capacity your systems require: Global first, then Regional Subchains as they launch.

  2. 02

    Provision

    Somnia will provision dedicated nodes alongside the network in that region, reserved for your organisation.

  3. 03

    Connect

    Your team will receive private HTTPS and WebSocket endpoints, restricted to your IP addresses.

  4. 04

    Monitor

    Track requests, latency and usage in Somnia Explorer, and add capacity as volume grows.

Illustrative
// Swap the URL. Chain ID stays 5031.
import { createPublicClient, webSocket } from 'viem'
import { somnia } from './chains'
const client = createPublicClient({
chain: somnia,
transport: webSocket('wss://acme.rpc.somnia.network/ws'),
})
// New block on your own node
client.watchBlocks({
onBlock: (block) => requote(block),
})
Not connectedBlock 460,667,184

Built for systems that need to run on every block.

On a shared endpoint, your requests compete with every wallet, bot and indexer on the network. Dedicated RPC gives quoting, indexing and settlement systems their own nodes, right next to the chain.

  1. 01

    Market makers

    Quote without competing for a shared endpoint

    Market makers will have capacity sized to their quoting loop for quotes, cancels and fills, rather than a public rate limit.

    • Reserved capacity for quoting loops
    • Order events streamed over WebSocket
    • Placement in the region you trade
  2. 02

    Venues and wallets

    Serve users from reserved infrastructure

    Venues, wallets and applications will route their users’ traffic through nodes reserved for them, so activity elsewhere on the network does not compete with their front end.

    • Front-end reads on reserved capacity
    • Private endpoints per environment
    • Works with Somnia Venues
  3. 03

    Data and indexing

    Backfill and stream without public limits

    Indexers, analytics firms and data providers will read the chain at block pace, without public rate limits.

    • Log queries without public limits
    • Block and log streams over WebSocket
    • Archive access TBC
  4. 04

    AI agents

    Act on every block

    Agents that monitor state and submit transactions in a loop will have a reserved endpoint, and each write will return its receipt in the same call.

    • realtime_sendRawTransaction
    • Subscriptions instead of polling
    • Pairs with Somnia Agents

Frequently asked questions.

For anything not covered here, contact the team. Every waitlist note is read.

Read the docs
When will Dedicated RPC be available?

Dedicated RPC is not yet available. Join the waitlist and the team will contact you when capacity opens in your region. Launch date TBC.

Dedicated RPC in the docs
How is it different from the public RPC?

The public endpoint at api.infra.mainnet.somnia.network is shared by all network users. Dedicated nodes will serve only your traffic, in the region you choose, behind your own allow-list.

RPCs in the docs
Do I need to change my code?

Only the RPC URL changes. Foundry, Hardhat, viem and ethers will work as they do today, and the chain ID remains 5031.

Which methods are supported?

Standard Ethereum JSON-RPC, WebSocket subscriptions and Somnia’s realtime_sendRawTransaction will be supported. Archive and trace methods are TBC.

The JSON-RPC API in the docs
How is it priced?

Pricing is TBC. Gas applies to every transaction you send, as it does on any Somnia endpoint.

Reserve dedicated capacity in your region.

Join the waitlist to hold capacity when Dedicated RPC opens, or speak with the team about your latency requirements.

Talk to an expert