You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .gitbook/includes/note-for-existing-signersth....md
+3-3Lines changed: 3 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -26,7 +26,7 @@ The output will specify which configuration key caused the panic (there may be m
26
26
27
27
```
28
28
$ stacks-node check-config --config ./Config.toml
29
-
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])
29
+
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])
30
30
INFO [1729707265.671604] [testnet/stacks-node/src/main.rs:318] [main] Loading config at path ./Config.toml
31
31
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
32
32
```
@@ -40,6 +40,6 @@ Note that in the Stacks node config file, the `block_proposal_token` field has b
40
40
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.
Copy file name to clipboardExpand all lines: guides-and-tutorials/running-a-signer/README.md
+6-6Lines changed: 6 additions & 6 deletions
Original file line number
Diff line number
Diff line change
@@ -134,7 +134,7 @@ Note that at the moment the signer should only be run on testnet using these ins
134
134
135
135
#### Running the Signer with Docker
136
136
137
-
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.
137
+
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.
138
138
139
139
When running the Docker container, you’ll need to ensure a few things:
140
140
@@ -148,7 +148,7 @@ Be sure to replace the `STX_SIGNER_PATH` with the correct path to your config fi
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:
276
+
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:
277
277
278
278
* The port configured for `p2p_bind` must be exposed to the internet
279
279
* 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
@@ -83,7 +83,7 @@ From this file, you'll need the `privateKey` value.
83
83
84
84
### Download the stacks-signer binary
85
85
86
-
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.
86
+
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.
87
87
88
88
Assuming a `Linux x64 glibc` machine, the commands to download and uncompress the signer binary look like this:
89
89
@@ -92,7 +92,7 @@ Assuming a `Linux x64 glibc` machine, the commands to download and uncompress th
@@ -189,7 +189,7 @@ We have created guides for running both a [full Bitcoin node](../nodes-and-miner
189
189
190
190
### Download the stacks-node binary
191
191
192
-
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.
192
+
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.
193
193
194
194
Assuming a `Linux x64 glibc` machine, the commands to download and uncompress the node binary look like this:
195
195
@@ -198,7 +198,7 @@ Assuming a `Linux x64 glibc` machine, the commands to download and uncompress th
Copy file name to clipboardExpand all lines: nakamoto-upgrade/setting-up-a-primary-post-nakamoto-testnet-node.md
+4-4Lines changed: 4 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
3
3
### **Setup A Stacks Primary Testnet Node**
4
4
5
-
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.
5
+
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.
6
6
7
7
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.
8
8
@@ -20,7 +20,7 @@ STACKS_RPC_PORT="40443"
20
20
STACKS_P2P_PORT="40444"
21
21
22
22
IMG="blockstack/stacks-core"
23
-
VER="3.0.0.0.0"
23
+
VER="3.1.0.0.3"
24
24
STX_NODE_CONFIG="${STACKS_DIR}/Config.toml"
25
25
26
26
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
0 commit comments