Requirements for Deploying a Regular Node in the ISBE Network
This document details the minimum requirements for deploying a Hyperledger Besu regular node within the ISBE network.
It is aimed at use case participants who need to operate their own node for reading, writing, or deploying smart contracts.
1. Hardware Requirements
Regular nodes do not execute IBFT consensus, so their needs are moderate.
Recommended requirements:
| Resource | Recommended | Minimum |
|---|---|---|
| vCPU | 2 | 1 |
| RAM | 4 GB | 2 GB |
| SSD | 40 GB | 20 GB |
| Network | 100 Mbps | 10 Mbps |
For use cases with a high volume of data/events, it is recommended to increase:
- 4 vCPU
- 8 GB RAM
- 80+ GB SSD
2. Operating System
A modern Linux environment is recommended:
- Ubuntu 20.04 / 22.04 LTS
- Debian 11+
- Rocky / AlmaLinux 8+
It must be a stable system with active security updates.
3. Software Dependencies
To run Besu in containers:
- Docker ≥ 20.10
- Docker Compose ≥ 2.x
curl,git, and base administration tools
Quick check:
docker --version
docker compose version
If the node will not be run in Docker (not recommended), the following will be needed:
- JDK 17+
- Besu binaries compatible with ISBE
4. Network Requirements
For a regular node to join ISBE's P2P, the following ports must be enabled:
| Port | Protocol | Use |
|---|---|---|
| 30303 | TCP | P2P Communication |
| 30303 | UDP | Discovery (optional, depends on environment) |
| 8545 | TCP | HTTP RPC (if exposed) |
| 8546 | TCP | WebSocket RPC (if exposed) |
Mandatory Requirements
- Port 30303/tcp must be accessible from the Internet.
- The node's public IP must match the one sent for permissioning.
- There must be no internal firewall blocking P2P traffic.
Security Recommendations
- Limit RPC access (8545/8546) to trusted IPs.
- Use firewall rules at the server or cloud provider layer.
- Do not expose RPC without authentication in sensitive environments.
5. Information Needed Before Installation
The participant must define:
- Node Name:
<Node_Name> - Public IP:
<NODE_IP> - Data-path directory
- Technical contact for the node
- Target ISBE environment: dev / pre / pro
This data will then be used in the docker-compose.yml file and in the permissioning request.
6. Pre-deployment Best Practices
- Use a dedicated server exclusively for the node (do not mix with other applications).
- Configure periodic backups of the data directory.
- Disable SSH access by password; use public keys.
- Keep Docker updated.
- Avoid slow disk mounts (never use NFS for the data-path).
7. Summary
| Category | Requirements |
|---|---|
| Hardware | 2 vCPU, 4 GB RAM, 40 GB SSD |
| OS | Updated 64-bit Linux |
| Software | Docker + Docker Compose |
| Network | 30303/tcp open to the Internet |
| Pre-info | <Node_Name>, <NODE_IP>, environment |
With these requirements, the node will be ready to proceed with the installation described in instalación-nodo-regular.md.