Skip to content

Latest commit

 

History

History
300 lines (220 loc) · 10.8 KB

mine-mainnet-stacks-tokens.md

File metadata and controls

300 lines (220 loc) · 10.8 KB
Raw

Mine Mainnet Stacks Tokens

Introduction

For more on the technical details of mining, please review the mining guide.

The following is an abridged version of the walkthrough here, written for a Linux system. If you're on Windows or MacOS, there will be some slight modifications needed (PR's welcome!).

If you're interested in mining on the Stacks mainnet, you can find instructions on how to do that here:

Running a Bitcoin Mainnet Full Node

To participate as a miner on mainnet, you must have access to a mainnet bitcoin node with a wallet (and the wallet's private key). One way to accomplish this is to run bitcoin locally.

First, download a bitcoin binary, or build from source (there may be some extra requirements to building, defined here).

If you want to learn more about the technical details of mining, please review the mining guide:

{% hint style="info" %} Tip: It is recommended to use a persistent location for the chainstate, in the steps below we're using /bitcoin. {% endhint %}

Update the Bitcoin Configuration File

Next, update the bitcoin configuration:

  • Optional, but recommended: Use a persistent directory to store the Bitcoin chainstate, i.e. datadir=/bitcoin.
  • Optional, but recommended: Update the rpcallowip value to only allow 127.0.0.1, or the stacks miner IPv4.
  • Modify the rpcuser and rpcpassword values from the defaults below.
  • Store the following configuration somewhere on your filesystem (ex: $HOME/bitcoin.conf).
server=1
disablewallet=0
datadir=/bitcoin
rpcuser=btcuser
rpcpassword=btcpass
rpcallowip=0.0.0.0/0
bind=0.0.0.0:8333
rpcbind=0.0.0.0:8332
dbcache=512
banscore=1
rpcthreads=256
rpcworkqueue=256
rpctimeout=100
txindex=1

Start Bitcoin

Finally, start bitcoind as follows (adjust the conf path to where it was created in the previous step, i.e. $HOME/bitcoin.conf):

bitcoind -conf=$HOME/bitcoin.conf

{% hint style="info" %} Note: It will take a few hours for the node to synchronize with Bitcoin Mainnet. {% endhint %}

While it's syncing, you can track the progress with bitcoin-cli or the logfile (will be located where the chainstate is stored, i.e. /bitcoin/debug.log):

$ bitcoin-cli \
 -rpcconnect=127.0.0.1 \
 -rpcport=8332 \
 -rpcuser=btcuser \
 -rpcpassword=btcpass \
getblockchaininfo | jq .blocks
836745

Running a Stacks Blockchain miner

First, download the latest tagged stacks blockchain binary, or build from source (there may be some extra requirements to building, defined here).

{% hint style="info" %} Tip: It is recommended to use a persistent location for the chainstate, in the steps below we're using /stacks-blockchain. {% endhint %}

Generate a keychain

First, a keychain needs to be generated. With this keychain, we'll purchase some BTC from a cryptocurrency exchange, and then use that BTC to start mining.

To create a keychain, the simplest way is to use the stacks-cli with the make_keychain command.

npx @stacks/cli make_keychain 2>/dev/null | jq -r

After this runs, you should see some JSON printed to the screen that looks like this:

{
  "mnemonic": "spare decade dog ghost luxury churn flat lizard inch nephew nut drop huge divert mother soccer father zebra resist later twin vocal slender detail",
  "keyInfo": {
    "privateKey": "ooxeemeitar4ahw0ca8anu4thae7aephahshae1pahtae5oocahthahho4ahn7eici",
    "address": "SPTXOG3AIHOHNAEH5AU6IEX9OOTOH8SEIWEI5IJ9",
    "btcAddress": "Ook6goo1Jee5ZuPualeiqu9RiN8wooshoo",
    "wif": "rohCie2ein2chaed9kaiyoo6zo1aeQu1yae4phooShov2oosh4ox",
    "index": 0
  }
}

{% hint style="danger" %} Do not lose this information - we'll need to use the privateKey, btcAddress and wif fields in later steps. {% endhint %}

The above wif (Kyk49jsPGen5C1ThhyJJH4CndLk8yLESuQJVGsbbTV3FFF9CRTJG) will then need to be imported into the bitcoin mainnet network.

Next, a bitcoin wallet is created:

bitcoin-cli \
  -rpcconnect=127.0.0.1 \
  -rpcport=8332 \
  -rpcuser=btcuser \
  -rpcpassword=btcpass \
  createwallet \
  wallet_name="miner" \
  disable_private_keys=false \
  blank=false \
  passphrase="" \
  avoid_reuse=false \
  descriptors=false \
  load_on_startup=true

Now, import your wif (bitcoin private key) inside the newly created wallet.

{% hint style="info" %} Note: Be sure to replace <wif from JSON above> with the wif value in the Generate a keychain step. {% endhint %}

bitcoin-cli \
  -rpcport=8332 \
  -rpcuser=btcuser \
  -rpcpassword=btcpassword \
  importprivkey <wif from JSON above>

{% hint style="info" %} Note: The import may take a while, because a wallet rescan is triggered. After the import has completed successfully, you can check that the address is imported with getaddressinfo. {% endhint %}

bitcoin-cli \
  -rpcconnect=127.0.0.1 \
  -rpcport=8332 \
  -rpcuser=btcuser \
  -rpcpassword=btcpass \
  getaddressinfo <btcAddress from JSON above>

Once imported, we need to get some BTC to that address. You should be able to transfer BTC to this address using a cryptocurrency exchange such as Coinbase, Binance, or Kraken.

Update the Stacks Blockchain Configuration File

Now, we need to configure our node to use this Bitcoin keychain. Copy the sample mainnet miner config to your local machine in a memorable location like $HOME/mainnet-miner-conf.toml.

Next, update the stacks configuration:

  • Optional, but recommended: Use a persistent directory to store the Stacks chainstate, i.e. working_dir = "/stacks-blockchain"
  • From the make_keychain step, modify the seed value with privatekey
  • Store the following configuration somewhere on your filesystem (ex: $HOME/mainnet-miner-conf.toml)
[node]
working_dir = "/stacks-blockchain"
rpc_bind = "0.0.0.0:20443"
p2p_bind = "0.0.0.0:20444"
seed = "<privateKey from JSON above>"
miner = true
bootstrap_node = "02196f005965cebe6ddc3901b7b1cc1aa7a88f305bb8c5893456b8f9a605923893@seed.mainnet.hiro.so:20444,02539449ad94e6e6392d8c1deb2b4e61f80ae2a18964349bc14336d8b903c46a8c@cet.stacksnodes.org:20444,02ececc8ce79b8adf813f13a0255f8ae58d4357309ba0cedd523d9f1a306fcfb79@sgt.stacksnodes.org:20444,0303144ba518fe7a0fb56a8a7d488f950307a4330f146e1e1458fc63fb33defe96@est.stacksnodes.org:20444"
mine_microblocks = false

[burnchain]
wallet_name = "miner"
chain = "bitcoin"
mode = "mainnet"
peer_host = "127.0.0.1"
username = "<bitcoin config rpcuser>"
password = "<bitcoin config rpcpassword>"
rpc_port = 8332
peer_port = 8333
satoshis_per_byte = 100
burn_fee_cap = 20000

Start the Stacks Blockchain

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

stacks-node start --config $HOME/mainnet-miner-conf.toml

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

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:

STACKS_LOG_DEBUG=1 stacks-node start --config $HOME/mainnet-miner-conf.toml

Optional: Running a Stacks Blockchain miner with Docker

Alternatively, you can run a Stacks mainnet miner with Docker.

{% hint style="warning" %} Ensure you have Docker installed. {% endhint %}

Generate a Keychain and Get Some Tokens

Generate a keychain:

docker run -i node:20-alpine npx @stacks/cli make_keychain 2>/dev/null | jq -r

We need to get some BTC to that address. You should be able to transfer BTC to this address using a cryptocurrency exchange such as Coinbase, Binance, or Kraken.

Update Stacks Blockchain Docker Configuration File

Use the steps outlined above to create the configuration file.

Start the Stacks Blockchain miner with Docker

{% hint style="info" %} Info: The ENV VARS RUST_BACKTRACE and STACKS_LOG_DEBUG are optional. If removed, debug logs will be disabled. {% endhint %}

docker run -d \
  --name stacks_miner \
  --rm \
  --network host \
  -e RUST_BACKTRACE="full" \
  -e STACKS_LOG_DEBUG="1" \
  -v "$HOME/mainnet-miner-conf.toml:/src/stacks-node/mainnet-miner-conf.toml" \
  -v "/stacks-blockchain:/stacks-blockchain" \
  -p 20443:20443 \
  -p 20444:20444 \
  blockstack/stacks-blockchain:latest \
/bin/stacks-node start --config /src/stacks-node/mainnet-miner-conf.toml

You can review the node logs with this command:

docker logs -f stacks_miner

Optional: Running in Kubernetes with Helm

In addition, you're also able to run a Stacks miner in a Kubernetes cluster using the stacks-blockchain Helm chart.

Ensure you have the following prerequisites installed:

Generate keychain and get some tokens

Use the steps outlined above

Install the chart and run the miner

To install the chart with the release name my-release and run the node as a miner:

minikube start # Only run this if standing up a local Kubernetes cluster
helm repo add blockstack https://charts.blockstack.xyz
helm install my-release blockstack/stacks-blockchain \
  --set config.node.miner=true \
  --set config.node.seed="your-privateKey-from-generate-keychain-step" \
  --set config.burnchain.mode="mainnet"

You can review the node logs with this command:

kubectl logs -l app.kubernetes.io/name=stacks-blockchain

For more information on the Helm chart and configuration options, please refer to the chart's homepage.