Download TKMChain

Current TKMChain release: v1.21.62. Choose a build for your operating system, then verify the release checksums before running a node or miner. Use the Tor-only startup instructions when connecting to mainnet.

Wallet and node

View all TKMChain v1.21.62 release contents

Operators who are preparing a validator should read the validator registration guide before funding an ML-DSA-87 account. It documents the 500,000 TKM bond, burned fee, activation queue, reward split, exit, unbonding, and slashing evidence.

Fast bootstrap

Download the official current-chain archive through Tor, then let gtkm verify and import it in batches. The archive is retained under the node's ~/.tkmchain/gtkm/bootstrap/ directory on Linux (and the equivalent Tkmchain directory on Windows):

Download the official TKMChain bootstrap archive

./build/bin/gtkm bootstrap \
  --url 'https://tkmchain.site/tkm-mainnet.rlp.gz' \
  --sha256 '5ab874b65f31d972b6e70ac2dd4cc4c2ad4bd4e5a4814b4a183c8632cab685c1' \
  --datadir "$HOME/.tkmchain"

Stop any running node before importing. The published SHA-256 is 5ab874b65f31d972b6e70ac2dd4cc4c2ad4bd4e5a4814b4a183c8632cab685c1. For a custom mirror, replace --url and provide its matching --sha256 value.

XMRig miner

Current TKM-compatible XMRig release: v6.26.0-tkm.8. These packages include the TKM pool configuration and are built for the supported CPU targets.

View all XMRig v6.26.0-tkm.8 release contents

The miner connects to the configured TKM pool through Tor. Keep the supplied config.json beside the executable and follow the XMRig mining guide.

Run a Tor-only node

Install Tor for your operating system, start the service, and use an onion hostname in --bootnodes. Keep HTTP and WebSocket RPC bound to loopback unless a separate authenticated reverse proxy is required.

Read the Tor installation guide · Read the node privacy guide

Release source

All release builds are produced by GitHub Actions from signed version tags. Review the release workflow and source repository.

Debian and Ubuntu (APT)

The tkmchain Debian package installs gtkm, the tkmchain command alias, and the Shield3 payout prover when it is included in the release. It supports amd64, arm64, and armhf.

Direct package downloads:

Install the package that matches dpkg --print-architecture:

set -eu

version="${TKM_VERSION:-v1.21.62}"
arch="$(dpkg --print-architecture)"
case "$arch" in amd64|arm64|armhf) ;; *) echo "Unsupported architecture: $arch" >&2; exit 1 ;; esac
package="tkmchain_${version#v}_${arch}.deb"

sudo apt-get update
sudo apt-get install -y ca-certificates curl
curl --fail --location --proto '=https' --tlsv1.2 \
  --output "/tmp/$package" \
  "https://github.com/tkmchain/go-tkmchain/releases/download/${version}/${package}"
sudo apt-get install "/tmp/$package"

For production deployments, download SHA256SUMS from the v1.21.62 release and verify the selected package before installing it. The package does not start a node or install Tor automatically.

Start through Tor

Install and start Tor before launching the node:

sudo apt-get install -y tor
sudo systemctl enable --now tor
systemctl is-active tor

Run gtkm with onion-only P2P, an onion hostname, and an onion bootnode. Keep HTTP and WebSocket RPC on loopback:

gtkm \
  --port 3000 \
  --privacy.onion-only \
  --p2p.tor-socks5=socks5://127.0.0.1:9050 \
  --p2p.onion-hostname='<this-node>.onion' \
  --bootnodes='enode://<peer-key>@<peer>.onion:3000?discport=0' \
  --http --http.addr=127.0.0.1 --http.port=8545 \
  --ws --ws.addr=127.0.0.1 --ws.port=8546

Do not use --nat=extip:<ip>, public RPC bindings, wildcard origins, or 127.0.0.1:9050 as a peer address. Port 9050 is the local Tor SOCKS proxy; TKMChain peers use the onion service's P2P port, normally 3000.

See the full APT installation guide, Tor installation guide, and privacy deployment guide.