Run an RGN node

Choose your node setup

A regular node independently validates the RGN ledger and FORGE certificates. It does not need a wallet, private approval key, DGB/DOGE daemon or pool database. Linux AMD64 builds are published for v3.0.0.

Option A · Docker

Install Docker Engine using its official installation guide. Run these commands on the host that will own the chain data.

docker pull roguenetwork/rogue-network:3.0.0
docker run -d \
  --name rgn-node \
  --restart unless-stopped \
  --stop-timeout 120 \
  -p 127.0.0.1:18545:18545 \
  -p 30303:30303/tcp \
  -p 30303:30303/udp \
  -v rgn-data:/var/lib/rgn \
  roguenetwork/rogue-network:3.0.0

HTTP RPC is bound to the host loopback interface. Public P2P uses TCP and UDP 30303. The named volume survives container replacement. The image runs as UID/GID 10001; arrange ownership before using a host-directory mount instead.

Verify identity, peers and progress

docker logs --tail 50 rgn-node
docker exec rgn-node python3 /opt/rgn/docker/health.py
curl -s http://127.0.0.1:18545 \
  -H 'Content-Type: application/json' \
  --data '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":1}'
curl -s http://127.0.0.1:18545 \
  -H 'Content-Type: application/json' \
  --data '{"jsonrpc":"2.0","method":"net_peerCount","params":[],"id":1}'
curl -s http://127.0.0.1:18545 \
  -H 'Content-Type: application/json' \
  --data '{"jsonrpc":"2.0","method":"eth_syncing","params":[],"id":1}' 

The health helper checks the exact genesis and full consensus configuration. A fully synchronized node also needs connected peers and a height matching the canonical network. eth_syncing=false at height zero is not evidence of a completed sync.

Option B · Native Linux binary

The released x86-64 executable is dynamically linked and requires glibc 2.34 or newer; Ubuntu 22.04 is the reference runtime. No Go compiler is needed to run it. Python 3 is used by the verification helper.

curl --fail --location --remote-name https://github.com/rogueisles/Rogue-Network/releases/download/v3.0.0/rgn-v3.0.0-linux-amd64.tar.gz
curl --fail --location --remote-name https://github.com/rogueisles/Rogue-Network/releases/download/v3.0.0/SHA256SUMS
sha256sum -c SHA256SUMS
tar -xzf rgn-v3.0.0-linux-amd64.tar.gz
cd rgn-v3.0.0-linux-amd64
sha256sum -c PACKAGE-SHA256SUMS
./egem --datadir "$HOME/.rgn" --networkid 70088 --nousb init ./RGN-mainnet-1100100-genesis.json
./start-node.sh "$HOME/.rgn"

Leave the node command running. In another terminal in the release folder, run python3 ./check-node.py "$HOME/.rgn". Native defaults use P2P 30666 TCP/UDP and HTTP RPC on 127.0.0.1:8545. These differ from the container’s published ports.

Upgrading an existing OGG/RGN node

1. Stop it cleanly.

   Use its existing service manager, confirm the process exited and back up the stopped data, binary and startup settings.

2. Keep the actual data directory.

   Apply the release’s shared genesis/configuration with the node stopped, following NODE-SETUP.txt in the release. Do not substitute an empty directory or reset the chain.

3. Update the existing startup command.

   Point to the new binary while retaining identity, datadir, network ID and chosen ports. Never run two processes against one database.

4. Restart and verify.

   Run check-node.py against that directory; inspect peers and block import. Stop on incompatible genesis/configuration errors instead of forcing a rewind.

Storage and pruning

Plan SSD capacity for a growing chain database. The standard profile uses full sync and normal full-node state garbage collection. That is not a promise of bounded historical block storage, nor a Bitcoin-style prune target. Archive-mode historical state needs separate capacity planning. Do not run an unreviewed offline prune on a production database.

Release identity

The inherited executable name and banner remain egem / 1.0.3-syrius. Identify the release by its commit and verified checksums, not that banner. The shared configuration selects chain 70088 and activation 1,100,100.

Source commit 18367e0aea25899af7fe8d608f0a19fa420740a9 · Network parameters ↗