Update Versions (#1687)

* feat: update node and signer versions to latest

* update versions to latest used as of jan 16

.gitbook/includes/note-for-existing-signersth....md

@@ -26,7 +26,7 @@ The output will specify which configuration key caused the panic (there may be m
 
 ```
 $ stacks-node check-config --config ./Config.toml
-INFO [1729707354.217841] [testnet/stacks-node/src/main.rs:285] [main] stacks-node 3.0.0.0.0 (release/3.0.0.0.0:dd1ebe6, release build, linux [x86_64])
+INFO [1737057614.446096] [testnet/stacks-node/src/main.rs:278] [main] stacks-node 3.1.0.0.3 (release/3.1.0.0.3:906a8cc, release build, linux [x86_64])
 INFO [1729707265.671604] [testnet/stacks-node/src/main.rs:318] [main] Loading config at path ./Config.toml
 WARN [1729707265.671992] [testnet/stacks-node/src/main.rs:325] [main] Invalid config file: Invalid toml: unknown field `foo`, expected one of `name`, `seed`, `deny_nodes`, `working_dir`, `rpc_bind`, `p2p_bind`, `p2p_address`, `data_url`, `bootstrap_node`, `local_peer_seed`, `miner`, `stacker`, `mock_mining`, `mock_mining_output_dir`, `mine_microblocks`, `microblock_frequency`, `max_microblocks`, `wait_time_for_microblocks`, `wait_time_for_blocks`, `next_initiative_delay`, `prometheus_bind`, `marf_cache_strategy`, `marf_defer_hashing`, `pox_sync_sample_secs`, `use_test_genesis_chainstate`, `always_use_affirmation_maps`, `require_affirmed_anchor_blocks`, `chain_liveness_poll_time_secs`, `stacker_dbs`, `fault_injection_block_push_fail_probability` for key `node` at line 20 column 1
 ```
@@ -40,6 +40,6 @@ Note that in the Stacks node config file, the `block_proposal_token` field has b
 For quick reference, here are the current latest versions you'll want to be running as a signer. If you don't yet have your signer up and running, this guide will walk you through that.
 
 * [Binaries](https://github.com/stacks-network/stacks-core/releases/latest)
-* Signer Docker Image - [3.0.0.0.0.0](https://hub.docker.com/layers/blockstack/stacks-signer/3.0.0.0.0.0/images/sha256-5406912473befe62ce21f1630908b01960bae29b7bef306fd5669037ac8e112b?context=explore)
-* Stacks Node Docker Image - [3.0.0.0.0](https://hub.docker.com/layers/blockstack/stacks-core/3.0.0.0.0/images/sha256-7e0ce69dff7198ce0dd0f44676f065abd6f834ed6d9a396856a36fd422ba6134?context=explore)
+* Signer Docker Image - [3.1.0.0.3.0](https://hub.docker.com/layers/blockstack/stacks-signer/3.1.0.0.3.0/images/sha256-d250b45bd9df406f9e63d995d2176609a631aad3b191d4f66a925be9cb170af0)
+* Stacks Node Docker Image - [3.1.0.0.3](https://hub.docker.com/layers/blockstack/stacks-core/3.1.0.0.3/images/sha256-8ac612356f4bb60f69ddb81676778907b484c0ab43951b91c3476a6cd41476a1)
 {% endhint %}

guides-and-tutorials/running-a-signer/README.md

@@ -134,7 +134,7 @@ Note that at the moment the signer should only be run on testnet using these ins
 
 #### Running the Signer with Docker
 
-You can run the signer as a Docker container using the [`blockstack/stacks-signer:3.1.0.0.0.0`](https://hub.docker.com/layers/blockstack/stacks-signer/3.1.0.0.0.0/images/sha256-bd0d116a324d621cc1dad2a16e46f773d2d34bdc70479bfb8c46feae054519df?context=explore) image.
+You can run the signer as a Docker container using the [`blockstack/stacks-signer:3.1.0.0.3.0`](https://hub.docker.com/layers/blockstack/stacks-signer/3.1.0.0.3.0/images/sha256-d250b45bd9df406f9e63d995d2176609a631aad3b191d4f66a925be9cb170af0) image.
 
 When running the Docker container, you’ll need to ensure a few things:
 
@@ -148,7 +148,7 @@ Be sure to replace the `STX_SIGNER_PATH` with the correct path to your config fi
 
 ```bash
 IMG="blockstack/stacks-signer"
-VER="3.1.0.0.0.0"
+VER="3.1.0.0.3.0"
 STX_SIGNER_PATH="./"
 STX_SIGNER_DATA="$STX_SIGNER_PATH/data"
 STX_SIGNER_CONFIG="$STX_SIGNER_PATH/signer-config.toml"
@@ -174,7 +174,7 @@ For example, if you are running on M1 Mac, you would add `--platform=linux/amd64
 Or, with a custom Dockerfile:
 
 ```docker
-FROM blockstack/stacks-signer:3.1.0.0.0.0
+FROM blockstack/stacks-signer:3.1.0.0.3.0
 COPY signer-config.toml /config.toml
 EXPOSE 30000
 CMD ["stacks-signer", "run", "--config", "/config.toml"]
@@ -273,7 +273,7 @@ For example:
 
 #### Run a Stacks Node with Docker
 
-You can run the Stacks node as a Docker container using the `blockstack/stacks-core` image, currently on [version 3.1.0.0.0](https://hub.docker.com/layers/blockstack/stacks-core/3.1.0.0.0/images/sha256-85cd9a9da3c1dd44cd17ec25928acf461480d28002405abecbf559a8af17214d?context=explore). When running the Docker container, you’ll need to ensure a few things:
+You can run the Stacks node as a Docker container using the `blockstack/stacks-core` image, currently on [version 3.1.0.0.3](https://hub.docker.com/layers/blockstack/stacks-core/3.1.0.0.3/images/sha256-8ac612356f4bb60f69ddb81676778907b484c0ab43951b91c3476a6cd41476a1). When running the Docker container, you’ll need to ensure a few things:
 
 * The port configured for `p2p_bind` must be exposed to the internet
 * The port configured for `rpc_bind` must be accessible by your signer
@@ -284,7 +284,7 @@ An example for running the node’s Docker image with docker run is below. Be su
 
 ```bash
 IMG="blockstack/stacks-core"
-VER="3.1.0.0.0"
+VER="3.1.0.0.3"
 STX_NODE_CONFIG="./node-config.toml"
 
 docker run -d \
@@ -302,7 +302,7 @@ docker run -d \
 Or, using a custom Dockerfile:
 
 ```docker
-FROM blockstack/stacks-core:3.1.0.0.0
+FROM blockstack/stacks-core:3.1.0.0.3
 COPY node-config.toml /config.toml
 EXPOSE 20444
 EXPOSE 20443

guides-and-tutorials/running-a-signer/signer-quickstart.md

@@ -3,14 +3,14 @@
 {% hint style="info" %}
 ### **Current Signer and Stacks Node Versions**
 
-**Signer - 3.1.0.0.0.0**
+**Signer - 3.1.0.0.3.0**
 
-* [Docker Image](https://hub.docker.com/layers/blockstack/stacks-signer/3.1.0.0.0.0/images/sha256-bd0d116a324d621cc1dad2a16e46f773d2d34bdc70479bfb8c46feae054519df?context=explore)
-* [GitHub Release](https://github.com/stacks-network/stacks-core/releases/tag/signer-3.1.0.0.0.0)
+* [Docker Image](https://hub.docker.com/layers/blockstack/stacks-signer/3.1.0.0.3.0/images/sha256-d250b45bd9df406f9e63d995d2176609a631aad3b191d4f66a925be9cb170af0)
+* [GitHub Release](https://github.com/stacks-network/stacks-core/releases/tag/signer-3.1.0.0.3.0)
 
-**Stacks Node - 3.1.0.0.0**
+**Stacks Node - 3.1.0.0.3**
 
-* [Docker Image](https://hub.docker.com/layers/blockstack/stacks-core/3.1.0.0.0/images/sha256-85cd9a9da3c1dd44cd17ec25928acf461480d28002405abecbf559a8af17214d?context=explore)
+* [Docker Image](https://hub.docker.com/layers/blockstack/stacks-core/3.1.0.0.3/images/sha256-8ac612356f4bb60f69ddb81676778907b484c0ab43951b91c3476a6cd41476a1)
 * [GitHub Release](https://github.com/stacks-network/stacks-core/releases/latest)
 {% endhint %}
 
@@ -83,7 +83,7 @@ From this file, you'll need the `privateKey` value.
 
 ### Download the stacks-signer binary
 
-Official binaries are available from the [Stacks Core releases page on Github](https://github.com/stacks-network/stacks-core/releases). Each release includes pre-built binaries. Download the [latest signer release ZIP file](https://github.com/stacks-network/stacks-core/releases/tag/signer-3.0.0.0.1.0) for your server’s architecture and decompress it. Inside of that folder is a `stacks-signer` binary.
+Official binaries are available from the [Stacks Core releases page on Github](https://github.com/stacks-network/stacks-core/releases). Each release includes pre-built binaries. Download the [latest signer release ZIP file](https://github.com/stacks-network/stacks-core/releases/tag/signer-3.1.0.0.3.0) for your server’s architecture and decompress it. Inside of that folder is a `stacks-signer` binary.
 
 Assuming a `Linux x64 glibc` machine, the commands to download and uncompress the signer binary look like this:
 
@@ -92,7 +92,7 @@ Assuming a `Linux x64 glibc` machine, the commands to download and uncompress th
 cd ~/stacks-signer
 
 # Download the signer binary zip
-wget https://github.com/stacks-network/stacks-core/releases/download/signer-3.1.0.0.0.0/linux-glibc-x64.zip
+wget https://github.com/stacks-network/stacks-core/releases/download/signer-3.1.0.0.3.0/linux-glibc-x64.zip
 
 # Unzip the signer binary archive
 unzip linux-glibc-x64.zip
@@ -154,7 +154,7 @@ To ensure the signer has been set up correctly, you can run the following comman
 ~/stacks-signer/stacks-signer --version
 
 # Output:
-stacks-signer stacks-signer 3.1.0.0.0.0 (release/3.1.0.0.0.0:dd1ebe6, release build, linux [x86_64])
+stacks-signer stacks-signer signer-3.1.0.0.3.0 (release/signer-3.1.0.0.3.0:309b8d5, release build, linux [x86_64])
 
 # Verify the config file
 ~/stacks-signer/stacks-signer check-config -c ~/stacks-signer/signer-config.toml 
@@ -189,7 +189,7 @@ We have created guides for running both a [full Bitcoin node](../nodes-and-miner
 
 ### Download the stacks-node binary
 
-Official binaries are available from the [Stacks Core releases page on Github](https://github.com/stacks-network/stacks-core/releases). Each release includes pre-built binaries. Download the [latest node release ZIP file](https://github.com/stacks-network/stacks-core/releases/tag/3.0.0.0.0) for your server’s architecture and decompress it. Inside of that folder is a `stacks-node` binary.
+Official binaries are available from the [Stacks Core releases page on Github](https://github.com/stacks-network/stacks-core/releases). Each release includes pre-built binaries. Download the [latest node release ZIP file](https://github.com/stacks-network/stacks-core/releases/tag/3.1.0.0.3) for your server’s architecture and decompress it. Inside of that folder is a `stacks-node` binary.
 
 Assuming a `Linux x64 glibc` machine, the commands to download and uncompress the node binary look like this:
 
@@ -198,7 +198,7 @@ Assuming a `Linux x64 glibc` machine, the commands to download and uncompress th
 cd ~/stacks-node
 
 # Download the node binary zip
-wget https://github.com/stacks-network/stacks-core/releases/download/3.1.0.0.0/linux-glibc-x64.zip
+wget https://github.com/stacks-network/stacks-core/releases/download/3.1.0.0.3/linux-glibc-x64.zip
 
 # Unzip the node binary archive
 unzip linux-glibc-x64.zip
@@ -384,14 +384,14 @@ To ensure the node has been set up correctly, you can run the following commands
 ~/stacks-node/stacks-node version
 
 # Output:
-INFO [1729788035.383049] [testnet/stacks-node/src/main.rs:285] [main] stacks-node 3.1.0.0.0 (release/3.1.0.0.0:dd1ebe6, release build, linux [x86_64])
-stacks-node 3.1.0.0.0 (release/3.1.0.0.0:dd1ebe6, release build, linux [x86_64])
+INFO [1737057614.446096] [testnet/stacks-node/src/main.rs:278] [main] stacks-node 3.1.0.0.3 (release/3.1.0.0.3:906a8cc, release build, linux [x86_64])
+stacks-node 3.1.0.0.3 (release/3.1.0.0.3:906a8cc, release build, linux [x86_64])
 
 # Verify the node's config
 ~/stacks-node/stacks-node check-config --config ~/stacks-node/node-config.toml
 
 # Output:
-INFO [1729788064.913032] [testnet/stacks-node/src/main.rs:285] [main] stacks-node 3.1.0.0.0 (release/3.1.0.0.0:dd1ebe6, release build, linux [x86_64])
+INFO [1737057614.446096] [testnet/stacks-node/src/main.rs:278] [main] stacks-node 3.1.0.0.3 (release/3.1.0.0.3:906a8cc, release build, linux [x86_64])
 INFO [1729788064.913175] [testnet/stacks-node/src/main.rs:318] [main] Loading config at path /home/admin/stacks-node/node-config.toml
 INFO [1729788064.969551] [testnet/stacks-node/src/main.rs:331] [main] Loaded config!
 ```

nakamoto-upgrade/nakamoto-activation-guide-for-signers.md

@@ -17,8 +17,8 @@ This initial phase focuses on testing Signer 3.0 readiness in a testnet environm
 
 **Action Required:**
 
-1. Update stacks-node to version 3.0.0.0.1 ([here](https://github.com/stacks-network/stacks-core/releases/tag/3.0.0.0.1))
-2. Update signer to version 3.0.0.0.0.1 ([here](https://github.com/stacks-network/stacks-core/releases/tag/signer-3.0.0.0.0.1))
+1. Update stacks-node to version 3.1.0.0.3 ([here](https://github.com/stacks-network/stacks-core/releases/tag/3.1.0.0.3))
+2. Update signer to version 3.1.0.0.3.0 ([here](https://github.com/stacks-network/stacks-core/releases/tag/signer-3.1.0.0.3.0))
 3. [Run a Primary Testnet node](setting-up-a-primary-post-nakamoto-testnet-node.md) alongside your Signer
 4. Create a testnet wallet address
 5. Complete the provided form ([here](https://blocksurvey.io/signer-nakamoto-activation-upgrade-GrOV5aivQ2.z2fh3bqEyLQ?v=o))

nakamoto-upgrade/nakamoto-rollout-plan/nakamoto-for-exchanges.md

@@ -30,9 +30,9 @@ The main thing exchanges will notice when the Nakamoto rollout is complete is th
 
 * [Testnet documentation](https://docs.stacks.co/nakamoto-upgrade/nakamoto)
 * [API documentation](https://docs.hiro.so/nakamoto/stacks-js)
-* [Core Binaries](https://github.com/stacks-network/stacks-core/releases/tag/3.0.0.0.0)
-* [Signer Binary](https://github.com/stacks-network/stacks-core/releases/tag/signer-3.0.0.0.0.0)
-* [Core Docker Images](https://hub.docker.com/r/blockstack/stacks-core/tags?page=1\&name=3.0.0.0.0)
-* [Signer Docker Image](https://hub.docker.com/r/blockstack/stacks-signer/tags?page=1\&name=3.0.0.0.0.0)
-* [Stacks Blockchain API](https://github.com/hirosystems/stacks-blockchain-api/releases/tag/v7.10.0)
-* [Stacks Blockchain API Docker Images](https://hub.docker.com/r/hirosystems/stacks-blockchain-api/tags?page=1\&name=7.10.0)
+* [Core Binaries](https://github.com/stacks-network/stacks-core/releases/tag/3.1.0.0.3)
+* [Signer Binary](https://github.com/stacks-network/stacks-core/releases/tag/signer-3.1.0.0.3.0)
+* [Core Docker Images](https://hub.docker.com/r/blockstack/stacks-core/tags?page=1\&name=3.1.0.0.3)
+* [Signer Docker Image](https://hub.docker.com/r/blockstack/stacks-signer/tags?page=1\&name=3.1.0.0.3.0)
+* [Stacks Blockchain API](https://github.com/hirosystems/stacks-blockchain-api/releases/tag/v8.4.0)
+* [Stacks Blockchain API Docker Images](https://hub.docker.com/r/hirosystems/stacks-blockchain-api/tags?page=1\&name=8.4.0)

nakamoto-upgrade/setting-up-a-primary-post-nakamoto-testnet-node.md

@@ -2,7 +2,7 @@
 
 ### **Setup A Stacks Primary Testnet Node**
 
-Once your signer is upgraded to version 3.0.0.0.0.1 ([here](https://github.com/stacks-network/stacks-core/releases/tag/signer-3.0.0.0.0.1)) you’ll need to run a primary testnet node alongside it.
+Once your signer is upgraded to version 3.1.0.0.3.0 ([here](https://github.com/stacks-network/stacks-core/releases/tag/signer-3.1.0.0.3.0)) you’ll need to run a primary testnet node alongside it.
 
 You have two options here. The first is to run the Bash script below and it will handle everything for you, including creating the configuration file, downloading and extracting a chain state archive, and getting the node up and running.
 
@@ -20,7 +20,7 @@ STACKS_RPC_PORT="40443"
 STACKS_P2P_PORT="40444"
 
 IMG="blockstack/stacks-core"
-VER="3.0.0.0.0"
+VER="3.1.0.0.3"
 STX_NODE_CONFIG="${STACKS_DIR}/Config.toml"
 
 mkdir -p ${STACKS_DIR}/data
@@ -241,7 +241,7 @@ An example for running the node’s Docker image with docker run is below. Be su
 ```bash
 IMG="blockstack/stacks-core"
 
-VER="3.0.0.0.0"
+VER="3.1.0.0.3"
 
 STX_NODE_CONFIG="./node-config.toml"
 
@@ -260,7 +260,7 @@ stacks-node start \\
 Or, using a custom Dockerfile:
 
 ```docker
-FROM blockstack/stacks-core:3.0.0.0.0
+FROM blockstack/stacks-core:3.1.0.0.3
 COPY node-config.toml /config.toml
 EXPOSE 20444
 EXPOSE 20443