Nodes & Validators

All Validators are required to have a valid stake of 35.000 ONI Token to participate as a full node

Types of Nodes

• Read node: A read node can sync the latest events from the blockchain. A read node is usually run locally, unless you expose it to the outside.

• Validator node: A validator node can issue new transactions and confirm blocks with the other validators. Transactions and blocks are propagated to other peers in the network. Users can submit transactions to their own validators, or they can submit transactions to a read node or API node, and then the transactions are propagated across the network.

• RPC or API node: An API or RPC node is functionally similar to a read node, but is public and acts as the main gateway to the blockchain network. Unlike a read node, an also API node contains all the history of the ledger.

• Archive node: An archive node is an API node, which stores a full archive of the network.

A Remote Procedure Call, or RPC, is a lightweight software communication protocol, which allows a program (the client), to communicate with a remote program (the server) hosted on a different network without needing details about the server’s network.

Node requirements

For better performance and uptime, we recommend similar or better specs:

AWS EC2 m5.xlarge with 4 vCPUs (3.1 GHz), SSD (gp2) storage.

• CPU > 3.0 GHz

• SSD (or NVMe SSD) (NB: AWS gp2 has upto 16000 IOPS)

• Network bandwidth: 1 Gbps (NB: m5.xlarge has upto 10 Gbps)

• Storage: depending on the types of your nodes.