Running a Testnet Node

The Stacks 2.0 testnet is currently in development. As part of the testnet, you can run a node and connect it to a public network. This guide will walk you through downloading and running your own node in the testnet network.


Note: If you use Linux, you may need to manually install libssl-dev and other packages. In your command line, run the following to get all packages:

sudo apt-get install build-essential cmake libssl-dev pkg-config

Ensure that you have Rust installed. If you are using macOS, Linux, or another Unix-like OS, run the following. If you are on a different OS, follow the official Rust installation guide.

curl --proto '=https' --tlsv1.2 -sSf | sh

If Rust is already installed, you might see this prompt. Select ‘Proceed with Installation’ to make sure you have the latest version installed.

rustup prompt

In case you just installed Rust, you will be prompted to run the following command to make the cargo command available:

source $HOME/.cargo/env

Download and install the stacks-blockchain repository

Next, clone this repository:

git clone

cd stacks-blockchain

Install the Stacks node by running:

cargo install --path ./testnet/stacks-node

Run your node

You’re all set to run a node that connects to the testnet network.

Back in the command line, run:

stacks-node argon

The first time you run this, you’ll see some logs indicating that the Rust code is being compiled. Once that’s done, you should see some logs that look something like the this:

INFO [1588108047.585] [src/chainstate/stacks/index/] First-ever block 0f9188f13cb7b2c71f2a335e3a4fc328bf5beb436012afca590b1a11466e2206

Awesome! Your node is now connected to the testnet network. Your node will receive new blocks when they are produced, and you can use your node’s RPC API to send transactions, fetch information for contracts and accounts, and more.

Running a miner

Once you’ve followed the above steps to run a node, it’s only a few more steps to run a proof-of-burn miner on the testnet.

First, we need to generate a keychain. With this keychain, we’ll get some testnet BTC from a faucet, and then use that BTC to start mining.

To get a keychain, the simplest way is to use the blockstack-cli. We’ll use the make_keychain command, and pass -t to indicate that we want a testnet keychain.

npx blockstack-cli@1.1.0-beta.1 make_keychain -t

After this runs, you’ll probably see some installation logs, and at the end you should see some JSON that looks like this:

  "mnemonic": "exhaust spin topic distance hole december impulse gate century absent breeze ostrich armed clerk oak peace want scrap auction sniff cradle siren blur blur",
  "keyInfo": {
    "privateKey": "2033269b55026ff2eddaf06d2e56938f7fd8e9d697af8fe0f857bb5962894d5801",
    "btcAddress": "mkRYR7KkPB1wjxNjVz3HByqAvVz8c4B6ND",
    "index": 0

We need to get some testnet BTC to that address. Grab the btcAddress field, and head over to the Stacks testnet website. In the BTC faucet section, past in your btcAddress, and submit. You’ll be sent 0.5 testnet BTC to that address. Don’t lose this information - we’ll need to use the privateKey field later on.

Now, we need to configure out node to use this Bitcoin keychain. In the stacks-blockchain folder, create a new file called testnet/stacks-node/conf/testnet-miner-conf.toml.

Paste in the following configuration:

rpc_bind = ""
p2p_bind = ""
bootstrap_node = ""
# Enter your private key here!
seed = "replace-with-your-private-key"
miner = true

chain = "bitcoin"
mode = "argon"
peer_host = ""
rpc_port = 18443
peer_port = 18444

amount = 10000000000000000
amount = 10000000000000000
amount = 10000000000000000
amount = 10000000000000000

Now, grab your privateKey from earlier, when you ran the make_keychain command. Replace the seed field with your private key. Save and close this configuration file.

To run your miner, run this in the command line:

stacks-node start --config=./testnet/stacks-node/conf/testnet-miner-conf.toml

Your node should start. It will take some time to sync, and then your miner will be running!

Creating an optimized binary

The steps above are great for trying to run a node temporarily. If you want to host a node on a server somewhere, you might want to generate an optimized binary. To do so, use the same configuration as above, but run:

cd testnet/stacks-node
cargo build --release --bin stacks-node

The above code will compile an optimized binary. To use it, run:

cd ../..
./target/release/stacks-node start --config=./testnet/conf/argon-follower-conf.toml

Enable debug logging

In case you are running into issues or would like to see verbose logging, you can run your node with debug logging enabled. In the command line, run:

BLOCKSTACK_DEBUG=1 stacks-node argon