System Configuration
Requirements
These are the minimum requirements to run a Rapid node. On systems with lower configurations , the node may lag behind the network .
| Network | CPU Cores | RAM | Disk |
|---|---|---|---|
rapid_9009-2 | 8 Cores / 8 threads | 16 GB | 1 TB NVMe |
rapid_1973-1 | 8 Cores / 8 threads | 32 GB | 2 TB NVMe |
Node Ports
26656: The Peer-to-Peer (P2P) protocol enables nodes within a network to communicate directly with each other. This facilitates data and block exchange among nodes in blockchain networks.The default port is one of the specific ports through which nodes communicate with each other. This port serves as the point where data and block exchange takes place between nodes.
Validator nodes play a special role in ensuring the reliability and integrity of the network. The configuration option called "persistent_peers" allows these validator nodes to establish continuous connections with specific other nodes. This enhances the stability of the network and enables faster data exchange between these designated nodes.
26657: This port is used for the Tendermint API server. Nodes can utilize this port to query information about the network and retrieve various statistics.26658: This port is the listening port for the Tendermint RPC server. RPC (Remote Procedure Call) facilitates transaction and data exchange between different nodes. Through requests made on this port, network information can be queried.26660: This port is the listening port for the gRPC (General Remote Procedure Call) server. gRPC enables efficient transaction calls between different nodes. Access to various services can be achieved through this port.
Additional Ports :
6060: This port is dedicated to the Prometheus data collection and monitoring system. Nodes can use this port to gather and monitor performance data.9090: This port is the listening port for the Prometheus data collection and monitoring server. Performance data from the network can be collected and queried through this port.9091: This port is the listening port for the gRPC error service server. It can be used to track and report error conditions.1317: This port is used for APIs of Cosmos SDK application chains. Application chains can use this port to facilitate data exchange between dApps and clients. Through this port, you can access application chain-specific functionality.8545: This port is used for Ethereum Virtual Machine (EVM) JSON-RPC communication. It allows external applications to interact with the EVM on an Ethereum-based network.
All of these ports can be edited via their respective config files.
Last updated