Developers & node operators

Run a full node

A node needs nothing special: the chain is 24,092 mostly empty blocks, and the seed nodes themselves are 1 GB virtual machines. Put this in vivuscoin.conf in the data directory before the first start.

# Peers: the two seed nodes (port 8168 is the default)
addnode=seed1.vivuscoin.com
addnode=seed2.vivuscoin.com
listen=1

# Required while the chain is paused. The last block is from 2021-09-22;
# without this a node treats its own tip as stale, stays in "initial block
# download" and refuses to serve blocks to anyone. Value is seconds; any
# number larger than the age of the last block works (this one is 10 years).
maxtipage=999999999

# On a public server: no wallet, RPC on localhost only
disablewallet=1
server=1
rpcbind=127.0.0.1
rpcallowip=127.0.0.1

Start vivuscoind (or the GUI) and wait for getblockchaininfo to report "blocks": 24092 with the best block hash from the table below. A wallet that shows 24,092 is fully synced; there is no later block to wait for.

Build from source

The tree builds like Bitcoin Core 0.17: autotools, with the depends system supplying Boost, libevent, BerkeleyDB 4.8 and Qt so the result does not depend on whatever your distribution ships. The repository’s doc/build-unix.md, doc/build-osx.md and doc/build-windows.md are the authoritative instructions; the outline below is the Linux path.

git clone https://github.com/vivuscoin/vivuscoin.git
cd vivuscoin
make -C depends -j"$(nproc)"                 # builds the libraries once; slow the first time
./autogen.sh
CONFIG_SITE="$PWD/depends/x86_64-pc-linux-gnu/share/config.site" ./configure
make -j"$(nproc)"
sha256sum src/vivuscoind src/vivuscoin-cli src/qt/vivuscoin-qt

• Windows is cross-compiled from Linux: make -C depends HOST=x86_64-w64-mingw32, then configure with that host’s config.site. The installer is produced by make deploy.
• macOS builds natively with the Homebrew packages listed in doc/build-osx.md. The 2021 image is unsigned and so will be the v1.1 image unless a signing identity is obtained; Gatekeeper is bypassed by right-clicking the app and choosing Open.
• Reproducibility. Release builds are made as reproducible as practical from one tagged commit, and the SHA-256 of every artifact is published with the release. If you build the same tag and get a different hash, say so on GitHub.
• Which branch. Build master to run what the network runs today. The v1.1 branch is under validation; do not run it on mainnet until it is released, and never against a data directory you care about without a backup.

Status data for integrators

If you only need the headline numbers, you do not need a node. The status script on seed1 writes /status/status.json every five minutes from the RPC calls above; the live tiles on this site read it. It is served same-origin with Cache-Control: max-age=300; there is no CORS header, so fetch it server-side or proxy it.

{"height":24092,"headers":24092,"last_block_time":"2021-09-22T21:16:00Z","difficulty":132.64,
 "best_hash":"000000000040a3597214ba978bdf6e853eb9d84c8abe39bcd90d57bc8c3a01fb",
 "chain_tips":1,"peers":1,"seed2_height":24092,"version":"/Parvus:1.0.0.11/",
 "updated":"2026-09-23T06:17:00Z"}