NVNM Testnet is now LIVE! For documentation relating to the NVNM Closed Beta L2, visit https://legacy.docs.nvnmchain.io

NVNM Chain
NVNM Chain Docs

Reference

Peers

Trusted peers for NVNM Chain (L1)

This page lists peer information for connecting to NVNM Chain (L1) networks.

Testnet

nvnm-next-testnet-1 (EVM Chain ID 787223) runs reth execution + Commonware Simplex BFT consensus. Peering is configured via reth's --trusted-peers flag with enode:// URLs. See Network Details for RPC/explorer endpoints.

Public Peers (externally reachable)

enode://f5826a55ca7c92dc04e6da41e061b0b684ae0338bcdec81ed3213ae8b251308b6870ddafee5128ba16268bdff78f2eba8bda6518d175ddc0cd36c606d604f526@34.150.20.80:30303
enode://2d91f00d8305eb5faf7a002a260ac0d83b6ac4b1a61de7cbdf4021b4476a03360db071e6842f4d3d176c90d9a12c264d77e6c3792634a09a4f483bbceb5c8d70@34.92.172.118:30303

P2P Port: 30303 (used for both peer connections and discovery)

To run a node that syncs NVNM Chain testnet using these peers:

  1. Download the nvnm-next-testnet-1 chain specification (genesis) file. --chain must point to it. Without it, tempo node defaults to Tempo mainnet and will not join NVNM Chain testnet:
curl -fLo nvnm-testnet.json \
  https://raw.githubusercontent.com/NVNM-Chain/nvnmchain-tempo/f6a03b7b037bb3060e9b86d0b87fc57d702597de/crates/chainspec/src/genesis/nvnm-testnet.json
  1. Generate an ed25519 signing key file. --consensus.signing-key takes a file path, not a hex key:
tempo consensus generate-signing-key --output ./signing.key
  1. Restore the latest snapshot. The testnet's state at block 0 includes data migrated from NVNM Chain L2 that the chain spec does not carry, so a node started from the chain spec alone rejects block 1. Pass the manifest named by the snapshot host's latest.json (about 12 GB to download, 22 GB on disk):
tempo download \
  --chain=./nvnm-testnet.json \
  --minimal \
  --manifest-url=https://download.nvnm.testnet.nvnmchain.io/787223/manifest.json
  1. Start the node with the testnet chain spec, your signing key, the public peers, and --follow:
tempo node \
  --follow=wss://rpc.nvnm.testnet.nvnmchain.io \
  --chain=./nvnm-testnet.json \
  --port=30303 \
  --discovery.port=30303 \
  --consensus.signing-key=./signing.key \
  --trusted-peers=enode://f5826a55ca7c92dc04e6da41e061b0b684ae0338bcdec81ed3213ae8b251308b6870ddafee5128ba16268bdff78f2eba8bda6518d175ddc0cd36c606d604f526@34.150.20.80:30303,enode://2d91f00d8305eb5faf7a002a260ac0d83b6ac4b1a61de7cbdf4021b4476a03360db071e6842f4d3d176c90d9a12c264d77e6c3792634a09a4f483bbceb5c8d70@34.92.172.118:30303
  • --follow syncs certified blocks from the public WebSocket endpoint. Without it, a non-validator node connects to peers but stays at block 0.
  • --trusted-peers connects your node to the execution P2P network, which carries transactions, not blocks.
  • --consensus.signing-key only gives your node a consensus P2P identity. A non-validator node never signs blocks.

Warning

Keep signing.key private — never share it or paste its contents. To encrypt it at rest, pass --secret <passphrase-source> to generate-signing-key and --consensus.secret <path> to tempo node.