Join the Network

TAC currently has two active testnet environments:

Network	Chain ID	Status	Version	Notes
Saint Petersburg Testnet	tacchain_2391-1	Active	v0.0.8	Newer testnet with 2s block time
Turin Testnet	tacchain_2390-1	Active	v0.0.7-testnet	Original testnet with 3s block time

In this guide, we’ll walk you through the process of joining either network as a node operator.

TAC Turin is going to be deprecated soon. Please use Saint Petersburg Testnet for your nodes.

Saint Petersburg Testnet (tacchain_2391-1)

Network Details

Chain ID: tacchain_2391-1
Tacchaind version: v0.0.8
Block time: 2s
EVM JSON RPC: https://spb.rpc.tac.build
RPC: https://spb.tendermint.rpc.tac.build
Genesis: https://spb.tendermint-rest.rpc.tac.build/genesis
gRPC: https://spb-grpc.rpc.tac.build
REST API: https://spb.cosmos-api.rpc.tac.build
EVM Explorer: https://spb.explorer.tac.build/
Cosmos Explorer: https://bd-explorer.tac-spb.ankr.com/
Faucet: https://spb.faucet.tac.build/
Staking UI: https://public1.rollup.asphere.xyz/
Peer 1: 9c32b3b959a2427bd2aa064f8c9a8efebdad4c23@206.217.210.164:45130
Peer 2: 04a2152eed9f73dc44779387a870ea6480c41fe7@206.217.210.164:45140
Peer 3: 5aaaf8140262d7416ac53abe4e0bd13b0f582168@23.92.177.41:45110
Peer 4: ddb3e8b8f4d051e914686302dafc2a73adf9b0d2@23.92.177.41:45120

Hardware Requirements

CPU: 8 cores
RAM: 16GB (for RPC nodes) / 32GB (for validator nodes)
Storage: 500GB NVMe SSD

Prerequisites

Go >= 1.23.6
jq
curl

Installation Steps

Install tacchaind v0.0.8

git clone https://github.com/TacBuild/tacchain.git
cd tacchain
git checkout v0.0.8
make install

Initialize network folder

tacchaind init <YOUR_NODE_NAME> --chain-id tacchain_2391-1 --home .testnet

Modify your config.toml

..
timeout_commit = "2s"
..
persistent_peers = "9c32b3b959a2427bd2aa064f8c9a8efebdad4c23@206.217.210.164:45130,04a2152eed9f73dc44779387a870ea6480c41fe7@206.217.210.164:45140,5aaaf8140262d7416ac53abe4e0bd13b0f582168@23.92.177.41:45110,ddb3e8b8f4d051e914686302dafc2a73adf9b0d2@23.92.177.41:45120"
..

Fetch genesis

curl https://raw.githubusercontent.com/TacBuild/tacchain/refs/heads/main/networks/tacchain_2391-1/genesis.json > .testnet/config/genesis.json

Start node

tacchaind start --chain-id tacchain_2391-1 --home .testnet

Using Docker

Setup environment and build Docker image

export TAC_HOME="~/.tacchain"
export VERSION="v0.0.8"

git clone https://github.com/TacBuild/tacchain.git && cd tacchain
git checkout ${VERSION}
docker build -t tacchain:${VERSION} .
mkdir -p $TAC_HOME
cp networks/tacchain_2391-1/{docker-compose.yaml,.env.spb} $TAC_HOME/

Fetch snapshot (when available)

cd $TAC_HOME
wget TBD
lz4 -dc < tac-spb-full-latest.tar.lz4 | tar -xvf -

Start with Docker Compose

docker compose --env-file=.env.spb up -d

Test the node

curl -L localhost:45138 -H "Content-Type: application/json" -d '{"jsonrpc": "2.0","method": "eth_blockNumber","params": [],"id": 1}'

Turin Testnet (tacchain_2390-1)

Network Details

Chain ID: tacchain_2390-1
Tacchaind version: v0.0.7-testnet
Block time: 3s
EVM JSON RPC: https://newyork-inap-72-251-230-233.ankr.com:443/tac_tacd_testnet_full_rpc_1
RPC: https://newyork-inap-72-251-230-233.ankr.com/tac_tacd_testnet_full_tendermint_rpc_1
Genesis: https://newyork-inap-72-251-230-233.ankr.com/tac_tacd_testnet_full_tendermint_rpc_1/genesis
gRPC: https://newyork-inap-72-251-230-233.ankr.com/tac_tacd_testnet_full_tendermint_grpc_web_1
REST API: https://newyork-inap-72-251-230-233.ankr.com/tac_tacd_testnet_full_tendermint_rest_1
EVM Explorer: https://turin.explorer.tac.build
Cosmos Explorer: https://turin.bd-explorer.tac.build
Faucet: https://faucet.tac-turin.ankr.com
Peer 1: f8124878e3526a9814c0a5f865820c5ea7eb26f8@72.251.230.233:45130
Peer 2: 4a03d6622a2ad923d79e81951fe651a17faf0be8@107.6.94.246:45130
Peer 3: ea5719fe6587b18ed0fee81f960e23c65c0e0ccc@206.217.210.164:45130
Snapshots:
- Full: http://snapshot.tac-turin.ankr.com/tac-turin-full-latest.tar.lz4
- Archive: http://snapshot.tac-turin.ankr.com/tac-turin-archive-latest.tar.lz4

Hardware Requirements

Same as Saint Petersburg Testnet

Prerequisites

Go >= 1.21 (or 1.23.6 for newer installations)
jq
curl
tar
lz4
wget

Installation Using Snapshots (Recommended)

Install tacchaind v0.0.7-testnet

git clone https://github.com/TacBuild/tacchain.git
cd tacchain
git checkout v0.0.7-testnet
make install

Initialize network folder

tacchaind init <YOUR_NODE_NAME> --chain-id tacchain_2390-1 --home .testnet

Modify your config.toml

..
timeout_commit = "3s"
..
persistent_peers = "f8124878e3526a9814c0a5f865820c5ea7eb26f8@72.251.230.233:45130,4a03d6622a2ad923d79e81951fe651a17faf0be8@107.6.94.246:45130,ea5719fe6587b18ed0fee81f960e23c65c0e0ccc@206.217.210.164:45130"
..

Fetch genesis

curl https://raw.githubusercontent.com/TacBuild/tacchain/refs/heads/main/networks/tacchain_2390-1/genesis.json > .testnet/config/genesis.json

Fetch snapshot

cd .testnet
rm -rf data
wget http://snapshot.tac-turin.ankr.com/tac-turin-full-latest.tar.lz4
lz4 -dc < tac-turin-full-latest.tar.lz4 | tar -xvf -

Start node

tacchaind start --chain-id tacchain_2390-1 --home .testnet

Using Docker

Setup environment and build Docker image

export TAC_HOME="~/.tacchain"
export VERSION="v0.0.7-testnet"

git clone https://github.com/TacBuild/tacchain.git && cd tacchain
git checkout ${VERSION}
docker build -t tacchain:${VERSION} .
mkdir -p $TAC_HOME
cp networks/tacchain_2390-1/{docker-compose.yaml,.env.turin} $TAC_HOME/

Fetch snapshot

cd $TAC_HOME
wget http://snapshot.tac-turin.ankr.com/tac-turin-full-latest.tar.lz4
lz4 -dc < tac-turin-full-latest.tar.lz4 | tar -xvf -

Start with Docker Compose

docker compose --env-file=.env.turin up -d

Test the node

curl -L localhost:45138 -H "Content-Type: application/json" -d '{"jsonrpc": "2.0","method": "eth_blockNumber","params": [],"id": 1}'

Manual Installation (Turin Testnet Only)

For developers who need to understand the chain upgrade history, you can follow this manual process that steps through each version:

Install tacchaind v0.0.1

git clone https://github.com/TacBuild/tacchain.git
cd tacchain
git checkout v0.0.1
make install

Initialize network folder

tacchaind init <YOUR_NODE_NAME> --chain-id tacchain_2390-1 --home .testnet

Modify your config.toml

..
timeout_commit = "3s"
..
persistent_peers = "f8124878e3526a9814c0a5f865820c5ea7eb26f8@72.251.230.233:45130,4a03d6622a2ad923d79e81951fe651a17faf0be8@107.6.94.246:45130,ea5719fe6587b18ed0fee81f960e23c65c0e0ccc@206.217.210.164:45130"
..

Fetch genesis

curl https://raw.githubusercontent.com/TacBuild/tacchain/refs/heads/main/networks/tacchain_2390-1/genesis.json > .testnet/config/genesis.json

Start node with --halt-height flag (v0.0.1)

tacchaind start --chain-id tacchain_2390-1 --home .testnet --halt-height 1727178

This flag will automatically stop your node at block height 1727178, then we need to update our binary before proceeding.

Update binary to v0.0.2 (EIP712 support)

git checkout v0.0.2
make install

Start node with --halt-height flag (v0.0.2)

tacchaind start --chain-id tacchain_2390-1 --home .testnet --halt-height 2259069

Update binary to v0.0.4 (mcopy support)

git checkout v0.0.4
make install

Start node with --halt-height flag (v0.0.4)

tacchaind start --chain-id tacchain_2390-1 --home .testnet --halt-height 3192449

Update binary to v0.0.5 (DefaultPowerReduction changes)

git checkout v0.0.5
make install

Start node without --halt-height flag (v0.0.5)

tacchaind start --chain-id tacchain_2390-1 --home .testnet

Wait for your node to hit height 3408172, at which point you’ll see a consensus error indicating you need to upgrade.

Update binary to v0.0.6-testnet

git checkout v0.0.6-testnet
make install

Start node with final version

tacchaind start --chain-id tacchain_2390-1 --home .testnet

Becoming a Validator

Once your node is fully synced, you can register as a validator:

Fund your account

Use the respective testnet faucet:

Saint Petersburg: https://spb.faucet.tac.build/
Turin: https://faucet.tac-turin.ankr.com

Import your private key

tacchaind --home .testnet keys unsafe-import-eth-key validator <PRIVATE_KEY> --keyring-backend test

Create validator transaction

For Saint Petersburg Testnet:

echo "{\"pubkey\":$(tacchaind --home .testnet tendermint show-validator),\"amount\":\"1000000000000000000utac\",\"moniker\":\"<YOUR_NODE_NAME>\",\"identity\":null,\"website\":null,\"security\":null,\"details\":null,\"commission-rate\":\"0.1\",\"commission-max-rate\":\"0.2\",\"commission-max-change-rate\":\"0.01\",\"min-self-delegation\":\"1\"}" > validatortx.json

tacchaind --home .testnet tx staking create-validator validatortx.json --from validator --keyring-backend test -y

For Turin Testnet (note the different amount):

echo "{\"pubkey\":$(tacchaind --home .testnet tendermint show-validator),\"amount\":\"1000000000utac\",\"moniker\":\"<YOUR_NODE_NAME>\",\"identity\":null,\"website\":null,\"security\":null,\"details\":null,\"commission-rate\":\"0.1\",\"commission-max-rate\":\"0.2\",\"commission-max-change-rate\":\"0.01\",\"min-self-delegation\":\"1\"}" > validatortx.json

tacchaind --home .testnet tx staking create-validator validatortx.json --from validator --keyring-backend test -y

Delegate more tokens (optional)

tacchaind --home .testnet tx staking delegate $(tacchaind --home .testnet q staking validators --output json | jq -r '.validators[] | select(.description.moniker == "<YOUR_NODE_NAME>") | .operator_address') 1000000000000000000utac --keyring-backend test --from validator -y

Participating in governance (optional)

# list all proposals on chain
tacchaind q gov proposals

# once you have identified the proposal (need `proposal_id`) you can place your vote
# In the following example we vote with 'yes', alternatively you can vote with 'no'
tacchaind tx gov vote <PROPOSAL_ID> yes --from validator

Sentry Node Architecture

For improved security, validators should implement a sentry node architecture:

Saint Petersburg Testnet Setup

Initialize a new config folder for the sentry node

tacchaind init <sentry_node_moniker> --chain-id tacchaind_2391-1 --default-denom utac

This will initialize config folder in $HOME/.tacchaind

Make sure you have replaced your genesis file with the one for Tac Saint Petersburg Testnet:

curl https://raw.githubusercontent.com/TacBuild/tacchain/refs/heads/main/networks/tacchain_2391-1/genesis.json > .testnet/config/genesis.json

Update config.toml for sentry node

..
timeout_commit = "2s"
..
persistent_peers = "9c32b3b959a2427bd2aa064f8c9a8efebdad4c23@206.217.210.164:45130,04a2152eed9f73dc44779387a870ea6480c41fe7@206.217.210.164:45140,5aaaf8140262d7416ac53abe4e0bd13b0f582168@23.92.177.41:45110,ddb3e8b8f4d051e914686302dafc2a73adf9b0d2@23.92.177.41:45120"
..
private_peer_ids = "<VALIDATOR_PEER_ID>@<VALIDATOR_IP:PORT>"
..

The private_peer_ids field is used to specify peers that will not be gossiped to the outside world, in our case the validator node we want it to represent.

Update config.toml for validator node

..
persistent_peers = "<SENTRY_NODE_ID>@<SENTRY_NODE_IP:PORT>"
..
pex = false
..

Using the sentry node setup, your validator node will be represented by your sentry node, therefore it no longer has to be connected with other peers. Replace persistent_peers so it points to your sentry node, this way it can no longer be accessed by the outer world. Also disable the pex field.

Restart nodes

Restart your validator node and start the sentry node.

Turin Testnet Setup

Initialize a new config folder for the sentry node

tacchaind init <sentry_node_moniker> --chain-id tacchaind_2390-1 --default-denom utac

This will initialize config folder in $HOME/.tacchaind

Make sure you have replaced your genesis file with the one for Tac Turin Testnet:

curl https://raw.githubusercontent.com/TacBuild/tacchain/refs/heads/main/networks/tacchain_2390-1/genesis.json > .testnet/config/genesis.json

Update config.toml for sentry node

..
timeout_commit = "3s"
..
persistent_peers = "f8124878e3526a9814c0a5f865820c5ea7eb26f8@72.251.230.233:45130,4a03d6622a2ad923d79e81951fe651a17faf0be8@107.6.94.246:45130,ea5719fe6587b18ed0fee81f960e23c65c0e0ccc@206.217.210.164:45130"
..
private_peer_ids = "<VALIDATOR_PEER_ID>@<VALIDATOR_IP:PORT>"
..

Update config.toml for validator node

..
persistent_peers = "<SENTRY_NODE_ID>@<SENTRY_NODE_IP:PORT>"
..
pex = false
..

Restart nodes

Restart your validator node and start the sentry node.

Need Help?

If you need testnet tokens, use the appropriate faucet:

Saint Petersburg: https://spb.faucet.tac.build/
Turin: https://faucet.tac-turin.ankr.com

If your validator isn’t in the active set, you need:

At least 1 voting power
More delegation than the current lowest validator (if the max validator limit is reached)

For any other questions, please reach out to the TAC team through our community channels.

Frequently Asked Questions

1. I need some funds on the testnet, how can I get them?

You can request testnet tokens from the faucet available at:

Saint Petersburg: https://spb.faucet.tac.build/
Turin: https://faucet.tac-turin.ankr.com/

Please note that the Turin faucet currently dispenses up to 10 TAC per day per address.

2. I have completed the guide to join as a validator, but my node is not in the active validator set?

In order to be included in the active validator set, your validator must have at least 1 voting power, or if the maximum validators limit has been reached your validator must have a greater amount of TAC delegated to them than the validator with the lowest amount delegated.

Get Started

Core Concepts

Contribute

Network Information

Join the Network

Saint Petersburg Testnet (tacchain_2391-1)

Network Details

Hardware Requirements

Prerequisites

Installation Steps

Using Docker

Turin Testnet (tacchain_2390-1)

Network Details

Hardware Requirements

Prerequisites

Installation Using Snapshots (Recommended)

Using Docker

Manual Installation (Turin Testnet Only)

Becoming a Validator

Sentry Node Architecture

Saint Petersburg Testnet Setup

Turin Testnet Setup

Need Help?

Frequently Asked Questions

Get Started

Core Concepts

Contribute

Network Information

​Saint Petersburg Testnet (tacchain_2391-1)

​Network Details

​Hardware Requirements

​Prerequisites

​Installation Steps

​Using Docker

​Turin Testnet (tacchain_2390-1)

​Network Details

​Hardware Requirements

​Prerequisites

​Installation Using Snapshots (Recommended)

​Using Docker

​Manual Installation (Turin Testnet Only)

​Becoming a Validator

​Sentry Node Architecture

​Saint Petersburg Testnet Setup

​Turin Testnet Setup

​Need Help?

​Frequently Asked Questions

Saint Petersburg Testnet (tacchain_2391-1)

Network Details

Hardware Requirements

Prerequisites

Installation Steps

Using Docker

Turin Testnet (tacchain_2390-1)

Network Details

Hardware Requirements

Prerequisites

Installation Using Snapshots (Recommended)

Using Docker

Manual Installation (Turin Testnet Only)

Becoming a Validator

Sentry Node Architecture

Saint Petersburg Testnet Setup

Turin Testnet Setup

Need Help?

Frequently Asked Questions