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?
| Role | What it does | Public RPC | Runs consensus |
|---|---|---|---|
| Development node | A chain on your laptop, pre-funded accounts | local only | no |
| Public RPC | Serves wallets and dApps over HTTPS/WSS, acts as a bootnode | yes, behind Cloudflare | no |
| Validator | Bonds ORB, stands for election, produces and finalizes blocks; earns era rewards, tips and the fees of the private transactions it includes | never | yes |
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:
| Resource | Minimum | Recommended (production) | High traffic |
|---|---|---|---|
| CPU | 4 cores | 8 cores | 16+ cores |
| RAM | 16 GB | 32–64 GB | 128 GB |
| Storage | 250–500 GB NVMe | 1 TB NVMe | 2 TB+ NVMe |
| Network | 100 Mbps | 1 Gbps | 1 Gbps+ |
| Disk | SSD/NVMe | Fast NVMe | Enterprise 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:
| Role | CPU | RAM | Storage |
|---|---|---|---|
| Development node | 2 cores | 4 GB | 40 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.