Status Roadmap
Docs/Build
Build

RPC reference

Public HTTP and WebSocket policy, examples, and error behavior.

RPC reference

The public gateway is intended for read methods and signed raw transactions.

Endpoints

  • HTTP JSON-RPC: https://rpc.orbynnetwork.org
  • WebSocket: wss://rpc.orbynnetwork.org/ws

Read the chain

curl https://rpc.orbynnetwork.org \
  -H 'content-type: application/json' \
  --data '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'

The response should contain 0x15b9e for Chain ID 88990.

Submit a signed transaction

{"jsonrpc":"2.0","method":"eth_sendRawTransaction","params":["0xSIGNED_RAW_TRANSACTION"],"id":1}

The gateway does not accept a private key or an unlocked account. Sign locally, then submit the raw signed bytes.

Policy and errors

  • Sustained HTTP rate: 20 requests per second per IP, with a burst of 40.
  • Maximum request body: 1 MB.
  • WebSocket limit: 5 connections per IP and 100 active subscriptions per connection.
  • 413 means the request body is too large.
  • 429 means the client exceeded a gateway limit.
  • 503 means an upstream service is unavailable.
  • Admin, QBFT, debug, trace, txpool, and permissioning APIs are not public.

Client applications should back off on 429 and 503, avoid polling faster than needed, and keep a status-aware retry policy.