Join our community of builders on Discord!

Run a Testnet Node

Running your own testnet node gives you an unrestricted private RPC endpoint, lower latency, and the ability to participate in the Proof of Intelligence (PoI) consensus mechanism.
[!NOTE] Running a node is optional for most developers.
The public RPC endpoint is sufficient for contract deployment and testing.
Run a node if you need higher throughput, lower latency, or want to test validator operations.

Prerequisites

RequirementMinimumRecommended
CPU4 cores8+ cores
RAM8 GB16 GB
Disk50 GB SSD100 GB NVMe SSD
Network25 Mbps100 Mbps
OSUbuntu 22.04+Ubuntu 24.04 LTS
Go1.21+1.22+

1. Install from Source

Clone the Repository

CodeBASH

Build the Binary

CodeBASH
The binary will be available at
CodeHTML
.

Verify the Installation

CodeBASH

2. Install via Docker

For a containerized setup:
CodeBASH
Verify:
CodeBASH

3. Initialize the Node

Download the Genesis File

CodeBASH

Initialize the Data Directory

CodeBASH

4. Start the Node

Full Node (Sync Only)

CodeBASH

Docker

CodeBASH

Verify Sync Status

Once the node is running, check that it's syncing:
CodeBASH
A response of
CodeHTML
means your node is fully synced.
[!TIP] Initial sync may take 30 minutes to a few hours depending on your connection speed and disk performance.

5. Run as a Validator (Optional)

To participate in Proof of Intelligence consensus on the testnet:

Generate a Validator Key

CodeBASH
This generates a validator keypair in
CodeHTML
. Back up the generated key files securely.

Stake Testnet LCAI

Validators must stake a minimum of 10 LCAI on the testnet. Stake via the CLI:
CodeBASH
Or stake via the Validator Dashboard.

Start the Node with Validator Mode

CodeBASH
Validator keys grant control over staked funds. Store them securely and never share them. On testnet this is low-risk, but practice good key hygiene for mainnet readiness.

6. Monitor Your Node

Logs

CodeBASH

Metrics

If running with the
CodeHTML
flag, Prometheus metrics are available at
CodeHTML
. A sample Grafana dashboard is available in the repository.

Peer Count

CodeBASH
A healthy node should have 5+ peers.

7. Systemd Service (Production Setup)

For persistent operation, create a systemd service:
CodeINI
Enable and start:
CodeBASH

Troubleshooting

IssueSolution
Node not finding peersVerify bootnodes are correct and port
CodeHTML
is open (TCP/UDP).
Sync stalledRestart the node. If persistent, clear the data directory and re-sync.
RPC not respondingCheck that
CodeHTML
is set correctly and port
CodeHTML
is not blocked.
High disk usageEnable pruning with
CodeHTML
or
CodeHTML
.
Validator not producingEnsure your stake transaction is confirmed and the node is fully synced.
Last updated: February 2026