Skip to main content
Run a Tavchain Testnet full node using the prebuilt image and the configuration in safeney/Tavchain. The image includes the client and current network files. You do not need a wallet, stake or local image build. For Windows or Linux ARM64, use native binaries. For wallet or application access, use public RPC.

Requirements

Use Linux x86-64 with Git, Docker Engine, Compose v2, persistent SSD storage, reliable outbound internet and accurate time. Storage grows with chain history. Docker Desktop, WSL and ARM hosts are outside this image’s tested platforms. Tavchain Testnet is unaudited; Test TAV has no monetary value.

Start a full node

Run these commands for a new node:
Compose downloads the published image. The first command initializes a fresh node identity in persistent Docker storage; the second starts the node. Run initialization only once. If it fails, keep the volume and inspect the error before continuing. Never mount an existing validator home. The repository’s Compose file pins the accepted image by digest. Genesis and peer defaults are included, so you do not need to download or edit them separately.

Check synchronization

From the same directory:
Wait for the node to catch up. To inspect native status:
Expect network tavchaintestnet_771002-1, advancing block heights and sync_info.catching_up: false after synchronization. Zero voting power is normal for this non-validator node. For peer checks and fixed-height block comparisons, follow Monitor a node.

Stop and resume

Keep the same project and data volume. The node resumes its existing identity and history. Do not initialize again, remove its volume or start two processes against the same data.
Host RPC mappings bind to 127.0.0.1: native RPC 29657, EVM HTTP 29645 and EVM WebSocket 29646. No P2P host port is published; the node connects outbound to the configured peers.Compose uses unless-stopped while Docker is running. Host Docker startup is configured separately. The five-minute stop grace allows database shutdown after a stop request.Ordinary docker compose -f compose.registry.yaml down removes containers and the network while retaining data. Do not add --volumes or prune the node’s volume.

Other installation options

The signed Docker archive remains available for local image builds. Follow its included README for that workflow; its compose.yaml differs from the prebuilt-image compose.registry.yaml. For direct executable installation, use native binaries. Read Upgrades and recovery before changing a retained node’s client or image. Use Troubleshooting for startup and sync failures and Network files and ports for reference configuration. Contact support@safeney.com for help.