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 |
| Indexer archive | Full history for an explorer or indexer, on the same host | no — loopback only | no |
| Validator | Produces and finalizes blocks, relays private transactions | 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
| Role | CPU | RAM | Storage |
|---|---|---|---|
| Development node | 2 cores | 4 GB | 40 GB SSD |
| Public RPC | 4 cores | 8 GB | 500 GB NVMe |
| Indexer archive | 4 cores | 8 GB | 2+ TB NVMe |
| Validator | 16 dedicated cores | 32 GB | 1 TB NVMe |
Recommended tiers for every role. Validator Requirements carries the network, OS, hosting-provider and required-services rules, which apply only to that role.
The indexer archive is a storage decision, not a compute one. Archive mode keeps every historical state, and that grows without bound. It is the only role where the disk is the constraint.
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.