English
Español
Português (Brasil)
简体中文
РусскийJoin the network
Run a Brisvia node
A node validates the chain for itself and helps the network stay decentralised. You don't need to mine, and running a node does not earn BRVA — it's how you verify Brisvia independently and keep it healthy. Here are the ways to run one, from the easiest to the advanced.
What a node does
A full node downloads and independently checks every block and transaction against the consensus rules, and relays them to other nodes. Some quick distinctions:
Running a node does not generate BRVA on its own. The node itself needs no payout address, private key or recovery phrase — Brisvia Desktop manages its wallet separately.
Easiest way — Brisvia Desktop
The desktop app bundles a full node, a wallet and a miner in one program. For most people this is all you need.
Running Brisvia Desktop gives you a full validating node. It only becomes a publicly reachable node if TCP port 9342 can reach your computer from the Internet — many home connections sit behind a router, firewall or CGNAT and won't accept incoming connections by default.
Advanced — build and run Brisvia Core
For operators and developers who want a standalone node. Brisvia Core is a fork of Bitcoin Core v30.2; the extra piece is RandomX. There is no prebuilt standalone binary yet, so you build it from source. Full platform build docs live in the repository.
1 · Clone with submodules (RandomX is a pinned submodule)
git clone --recursive https://github.com/brisvia/brisvia.git
cd brisvia2 · Build RandomX, then Brisvia Core
cmake -S src/randomx -B src/randomx/build -DARCH=native
cmake --build src/randomx/build -j"$(nproc)"
cmake -B build
cmake --build build -j"$(nproc)"`-DARCH=native` tunes RandomX for this machine — fine to run here, but the resulting build may not run on other processors.
3 · A minimal config file (named bitcoin.conf, in your data directory)
server=1
listen=1
port=9342
rpcport=9338
rpcbind=127.0.0.1No rpcuser/rpcpassword needed for local use — bitcoin-cli uses the RPC cookie created inside the data directory.
4 · Start the node
./build/bin/bitcoind -chain=brisvia -datadir="$HOME/brisvia-mainnet" -daemon5 · Stop it cleanly (let it close its databases — don't kill it)
./build/bin/bitcoin-cli -chain=brisvia -datadir="$HOME/brisvia-mainnet" stopCheck that it's syncing
./build/bin/bitcoin-cli -chain=brisvia -datadir="$HOME/brisvia-mainnet" getblockchaininfoCheck peers with getconnectioncount (or getpeerinfo for detail). The node finds peers automatically through the fixed seed nodes shipped in the daemon.
Make your node public (optional, helps the network)
A validating node doesn't need this — but accepting incoming connections on TCP 9342 lets you help other nodes. You need two things:
Test from another network (not your own LAN). You're only public once getpeerinfo shows inbound peers. A local listener, outbound connections, or an open PC firewall don't prove it — a router, CGNAT, your ISP, a changing public IP or a separate IPv6 firewall can still block it.
Security
Troubleshooting
Zero peers? Wait a few minutes; confirm networkactive=true in getnetworkinfo; check your system clock; confirm you're running with -chain=brisvia and not a testnet data directory; check debug.log. Use addnode only as a temporary diagnostic — the daemon already ships fixed seeds.
No incoming connections? Check listen=1, the firewall, port forwarding, CGNAT, your public IP, and IPv4 vs IPv6.
RPC not responding? Same -chain and -datadir, the process is running, the cookie exists, and you're using local port 9338. Don't open it to the Internet.
Wrong chain? Mainnet is chain=brisvia, P2P 9342, RPC 9338, genesis aa6bc268…af7baf7. Full parameters on the Integration page.