Skip to main content

Running a Node

Four roles, and picking the right one is most of the decision. They differ in what they serve, not in the software — every role runs the same ghcr.io/orbinum/node image.


Which node do you want?​

RoleWhat it doesPublic RPCRuns consensus
Development nodeA chain on your laptop, pre-funded accountslocal onlyno
Public RPCServes wallets and dApps over HTTPS/WSS, acts as a bootnodeyes, behind Cloudflareno
ValidatorBonds ORB, stands for election, produces and finalizes blocks; earns era rewards, tips and the fees of the private transactions it includesneveryes

If you are evaluating Orbinum, start with the development node — it needs no credentials and no open ports. If you want to support the network, the validator path is its own section.


Sizing​

The public RPC and the validator share one hardware table, in three tiers:

ResourceMinimumRecommended (production)High traffic
CPU4 cores8 cores16+ cores
RAM16 GB32–64 GB128 GB
Storage250–500 GB NVMe1 TB NVMe2 TB+ NVMe
Network100 Mbps1 Gbps1 Gbps+
DiskSSD/NVMeFast NVMeEnterprise NVMe

Minimum runs the node; recommended is what a production node should run; high traffic is for a public RPC under heavy load, or for headroom as shielded activity grows.

The development node has its own sizing:

RoleCPURAMStorage
Development node2 cores4 GB40 GB SSD

Validator Requirements carries the network, OS, hosting-provider and required-services rules, which apply only to that role.

A validator wants dedicated cores, not shared or burstable vCPUs; see Validator Requirements.


Docker, the node-deploy checkout and the ports each role opens are in Installation.