R5 Network
WebsiteR5 LabsGitHub
  • Getting Started
    • Hello & Welcome!
  • About R5
    • Overview
    • R5 Components
    • Consensus Mechanism
    • zkNet (Privacy)
  • R5 Coin
  • R5 Tokenomics
  • Tutorials & Guides
    • Connect & Use R5
      • R5 Desktop Wallet
      • MetaMask
      • Rabby Wallet
      • Coinbase Wallet
    • zkNet Web Wallet
    • R5 Desktop Wallet
      • Interface Overview
      • Send a Transaction
      • Receive a Transaction
      • Backup Your Wallet
      • Retrieve Your Private Key
    • How To: Deploy a Node
    • How To: Mine R5
    • How To: GPU Mine R5
    • How To: Build R5 From Source
    • How To: Connect Nodes Over LAN
  • For Developers
    • R5 SDK
      • R5 Relayer
      • R5 Console
      • JS Console
      • CLI Wallet
      • SCdev
      • SSL Proxy
    • Hardware Requirements
    • R5 Testnet
    • R5 Devnet
    • Local Networks
    • RPC API
      • admin
      • debug
      • ethash
      • miner
      • net
      • r5 (eth)
      • rpc
      • txpool
      • web3
    • R5 Analytics API
    • zkNet API
    • Node Configuration
    • Ethash-R5
    • Smart Contracts
    • Wrapped R5 (Native)
    • Tokens & NFTs
  • Bug Bounty Program
  • Resources
    • Website
    • R5 Labs
    • R5 Core Repository
Powered by GitBook
On this page
  • Start Your Master Node
  • Get Your `enode` Address
  • Add Your `enode` To Your Configuration File
  • Start Your Additional Nodes
  1. Tutorials & Guides

How To: Connect Nodes Over LAN

PreviousHow To: Build R5 From SourceNextR5 SDK

Last updated 24 days ago

Difficulty Level: Professional


If you have a mining farm or any setup that requires multiple nodes to connect to the network, you can optimise connection speeds and efficiency by synchronising your nodes over LAN. The concept is simple:

You will first connect to the network and sync your master node; you will use your master node to synchronise all your other machines.

Start Your Master Node

First, start your master node, connect and sync to the network. For more instructions on how to deploy your node, you can check the tutorial below.

Get Your `enode` Address

Once running, access your node via the JS Console using the terminal:

./r5 --jsconsole

Once in, use the command below to display your node information:

admin.nodeInfo

You should see a screen similar to this, and the red marking indicates where you will be able to identify your master node's enode address:

Copy your enode address and save it somewhere for later usage, replacing the 127.0.0.1 with your actual LAN IP address, for example 192.168.100.33 .

Make sure your master node's port 30337 is open for inbound and outbout connections, otherwise, other nodes won't be able to connect to it.

Add Your `enode` To Your Configuration File

Access your node configuration file (for example, inside /config/mainnet.config if you're on the mainnet), and add your master node's enode address to the list of static nodes:

Make sure you follow the same syntax as the other static nodes, making sure your enode address is wrapped in " and that you add a comma , at the end.

Start Your Additional Nodes

Making sure that your additional nodes have the new configuration file inside their /config folder, you can just start them normally, and they should use your LAN master node to sync to the network.

A checklist for everything to work:

  • Port 30337 needs to be open in all nodes.

  • You must replace 127.0.0.1 with your actual IP address.

  • You must ensure that all nodes have the updated config file.

How To: Deploy a Node