Skip to content

Commit e294243

Browse files
dineshpintodineshpinto
authored
chore(deps): bump disk requirements and version for running infra (#1047)
2 parents 497f7f8 + 438414d commit e294243

File tree

6 files changed

+22
-22
lines changed

6 files changed

+22
-22
lines changed

‎docs/network/0-overview.mdx‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -353,7 +353,7 @@ Discover suitable options for your needs on the [Flare Wallets](https://flare.ne
353353

354354
## Consensus mechanism
355355

356-
- **Consensus Protocol:** Snowman++ (from [Avalanche](https://build.avax.network/docs/quick-start)) provides a high-throughput, totally ordered consensus with fast finality. Learn more on the [Consensus](/network/consensus) page.
356+
- **Consensus Protocol:** Snowman++ (from [Avalanche](https://build.avax.network/docs/primary-network)) provides a high-throughput, totally ordered consensus with fast finality. Learn more on the [Consensus](/network/consensus) page.
357357

358358
- **Sybil resistance mechanism:** Proof-of-Stake (PoS)
359359

‎docs/network/4-consensus.mdx‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ import CodeBlock from "@theme/CodeBlock";
1111
import ThemedImage from "@theme/ThemedImage";
1212
import useBaseUrl from "@docusaurus/useBaseUrl";
1313

14-
The consensus protocol running on all Flare networks is Snowman++, introduced by [Avalanche](https://build.avax.network/docs/quick-start).
14+
The consensus protocol running on all Flare networks is Snowman++, introduced by [Avalanche](https://build.avax.network/docs/primary-network).
1515
This runs on both the P- and C-chains.
1616

1717
<div style={{ textAlign: "center", margin: "30px 0" }}>

‎docs/run-node/1-system-requirements.mdx‎

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -38,8 +38,8 @@ These requirements represent a baseline for running a stable go-flare node.
3838
| :------------------------ | :------------------------------ |
3939
| **CPU** | 4 cores |
4040
| **RAM** | 16 GB |
41-
| **Disk space (pruned)** | 500 GB SSD |
42-
| **Disk space (archival)** | 3.5 TB SSD |
41+
| **Disk space (pruned)** | 1 TB SSD |
42+
| **Disk space (archival)** | 5.7 TB SSD |
4343
| **Disk growth** | 30 GB/month |
4444
| **Disk speed** | 1200 MB/s read + 600 MB/s write |
4545

@@ -50,8 +50,8 @@ These requirements represent a baseline for running a stable go-flare node.
5050
| :------------------------ | :------------------------------ |
5151
| **CPU** | 4 cores |
5252
| **RAM** | 16 GB |
53-
| **Disk space (pruned)** | 150 GB SSD |
54-
| **Disk space (archival)** | 1 TB SSD |
53+
| **Disk space (pruned)** | 250 GB SSD |
54+
| **Disk space (archival)** | 1.2 TB SSD |
5555
| **Disk growth** | 5 GB/month |
5656
| **Disk speed** | 1200 MB/s read + 600 MB/s write |
5757

@@ -62,8 +62,8 @@ These requirements represent a baseline for running a stable go-flare node.
6262
| :------------------------ | :------------------------------ |
6363
| **CPU** | 4 cores |
6464
| **RAM** | 16 GB |
65-
| **Disk space (pruned)** | 2 TB SSD |
66-
| **Disk space (archival)** | 8 TB SSD |
65+
| **Disk space (pruned)** | 2.7 TB SSD |
66+
| **Disk space (archival)** | 11.2 TB SSD |
6767
| **Disk growth** | 120 GB/month |
6868
| **Disk speed** | 1200 MB/s read + 600 MB/s write |
6969

@@ -74,8 +74,8 @@ These requirements represent a baseline for running a stable go-flare node.
7474
| :------------------------ | :------------------------------ |
7575
| **CPU** | 4 cores |
7676
| **RAM** | 16 GB |
77-
| **Disk space (pruned)** | 150 GB SSD |
78-
| **Disk space (archival)** | 1 TB SSD |
77+
| **Disk space (pruned)** | 300 GB SSD |
78+
| **Disk space (archival)** | 1.6 TB SSD |
7979
| **Disk growth** | 11 GB/month |
8080
| **Disk speed** | 1200 MB/s read + 600 MB/s write |
8181

‎docs/run-node/2-from-source.mdx‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -32,7 +32,7 @@ Make sure to check the [hardware requirements](/run-node/system-requirements) be
3232
# 1. Find the latest stable release tag from:
3333
# https://github.com/flare-foundation/go-flare/releases
3434
# 2. Set the tag name in the variable below:
35-
LATEST_TAG="vX.Y.Z" # <-- REPLACE vX.Y.Z WITH THE ACTUAL LATEST TAG e.g. v1.11.0
35+
LATEST_TAG="vX.Y.Z" # <-- REPLACE vX.Y.Z WITH THE ACTUAL LATEST TAG e.g. v1.12.0
3636
```
3737

3838
2. Clone and build the binary:
@@ -202,7 +202,7 @@ These are some of the most relevant CLI parameters you can use. Read more about
202202

203203
#### Sample JSON configuration:
204204

205-
Most of the C-Chain configuration options can be found in the [Avalanche C-Chain Configuration docs](https://build.avax.network/docs/nodes/chain-configs/c-chain).
205+
Most of the C-Chain configuration options can be found in the [Avalanche C-Chain Configuration docs](https://build.avax.network/docs/nodes/chain-configs/avalanche-l1s/subnet-evm).
206206
Note that the default values are overridden only if specified in the given config file.
207207
Only provide values which differ from the defaults to avoid issues with future updates.
208208

@@ -250,7 +250,7 @@ To update your node to a newer version of go-flare:
250250
# 1. Find the latest stable release tag from:
251251
# https://github.com/flare-foundation/go-flare/releases
252252
# 2. Set the tag name in the variable below:
253-
LATEST_TAG="vX.Y.Z" # <-- REPLACE vX.Y.Z WITH THE ACTUAL LATEST TAG e.g. v1.11.0
253+
LATEST_TAG="vX.Y.Z" # <-- REPLACE vX.Y.Z WITH THE ACTUAL LATEST TAG e.g. v1.12.0
254254
git checkout ${LATEST_TAG}
255255
```
256256

‎docs/run-node/3-using-docker.mdx‎

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -105,7 +105,7 @@ Mounting these allows you to manage them directly without entering the container
105105
```
106106

107107
2. **Create configuration file:** Create a `config.json` file. This example provides a standard configuration for a public RPC node.
108-
Most of the C-Chain configuration options can be found in the [Avalanche C-Chain Configuration docs](https://build.avax.network/docs/nodes/chain-configs/c-chain).
108+
Most of the C-Chain configuration options can be found in the [Avalanche C-Chain Configuration docs](https://build.avax.network/docs/nodes/chain-configs/avalanche-l1s/subnet-evm).
109109
Note that the default values are overridden only if specified in the given config file.
110110
Only provide values which differ from the defaults to avoid issues with future updates.
111111

@@ -147,7 +147,7 @@ You can run your node using either the [Docker CLI](#using-docker-cli) directly
147147
# 1. Find the latest stable release tag from:
148148
# https://hub.docker.com/r/flarefoundation/go-flare/tags
149149
# 2. Set the tag name in the variable below (only use versioned tags):
150-
LATEST_TAG="vX.Y.Z" # <-- REPLACE vX.Y.Z WITH THE ACTUAL LATEST TAG e.g. v1.11.0
150+
LATEST_TAG="vX.Y.Z" # <-- REPLACE vX.Y.Z WITH THE ACTUAL LATEST TAG e.g. v1.12.0
151151
```
152152

153153
2. **Start the container:**
@@ -365,7 +365,7 @@ Docker Compose simplifies node management by defining the entire configuration i
365365
# 1. Find the latest stable release tag from:
366366
# https://hub.docker.com/r/flarefoundation/go-flare/tags
367367
# 2. Set the tag name in the variable below (only use versioned tags):
368-
image: flarefoundation/go-flare:vX.Y.Z # <-- REPLACE vX.Y.Z WITH THE ACTUAL LATEST TAG e.g. v1.11.0
368+
image: flarefoundation/go-flare:vX.Y.Z # <-- REPLACE vX.Y.Z WITH THE ACTUAL LATEST TAG e.g. v1.12.0
369369
restart: on-failure
370370
environment:
371371
- NETWORK_ID=flare
@@ -392,7 +392,7 @@ Docker Compose simplifies node management by defining the entire configuration i
392392
# 1. Find the latest stable release tag from:
393393
# https://hub.docker.com/r/flarefoundation/go-flare/tags
394394
# 2. Set the tag name in the variable below (only use versioned tags):
395-
image: flarefoundation/go-flare:vX.Y.Z # <-- REPLACE vX.Y.Z WITH THE ACTUAL LATEST TAG e.g. v1.11.0
395+
image: flarefoundation/go-flare:vX.Y.Z # <-- REPLACE vX.Y.Z WITH THE ACTUAL LATEST TAG e.g. v1.12.0
396396
restart: on-failure
397397
environment:
398398
- NETWORK_ID=costwo
@@ -419,7 +419,7 @@ Docker Compose simplifies node management by defining the entire configuration i
419419
# 1. Find the latest stable release tag from:
420420
# https://hub.docker.com/r/flarefoundation/go-flare/tags
421421
# 2. Set the tag name in the variable below (only use versioned tags):
422-
image: flarefoundation/go-flare:vX.Y.Z # <-- REPLACE vX.Y.Z WITH THE ACTUAL LATEST TAG e.g. v1.11.0
422+
image: flarefoundation/go-flare:vX.Y.Z # <-- REPLACE vX.Y.Z WITH THE ACTUAL LATEST TAG e.g. v1.12.0
423423
restart: on-failure
424424
environment:
425425
- NETWORK_ID=songbird
@@ -446,7 +446,7 @@ Docker Compose simplifies node management by defining the entire configuration i
446446
# 1. Find the latest stable release tag from:
447447
# https://hub.docker.com/r/flarefoundation/go-flare/tags
448448
# 2. Set the tag name in the variable below (only use versioned tags):
449-
image: flarefoundation/go-flare:vX.Y.Z # <-- REPLACE vX.Y.Z WITH THE ACTUAL LATEST TAG e.g. v1.11.0
449+
image: flarefoundation/go-flare:vX.Y.Z # <-- REPLACE vX.Y.Z WITH THE ACTUAL LATEST TAG e.g. v1.12.0
450450
restart: on-failure
451451
environment:
452452
- NETWORK_ID=coston
@@ -604,7 +604,7 @@ Keep your node up-to-date with the latest stable release of `go-flare` for secur
604604
3. Update the `docker-compose.yaml` file with the new tag and start the new container:
605605

606606
```bash
607-
LATEST_TAG="vX.Y.Z" # <-- Replace with the actual latest tag e.g v1.11.0
607+
LATEST_TAG="vX.Y.Z" # <-- Replace with the actual latest tag e.g v1.12.0
608608
yq -i ".services.node.image = flarefoundation/go-flare:${LATEST_TAG}" /opt/node/docker-compose.yaml
609609
docker compose -f /opt/node/docker-compose.yaml up -d
610610
```

‎docs/run-node/4-register-validator.mdx‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -67,7 +67,7 @@ Failure to implement these measures significantly increases the risk to your nod
6767

6868
As described in [Secure the node](#secure-the-node), a validator node should have minimal APIs enabled.
6969
Below is a sample `config.json` demonstrating a secure configuration with limited `eth-apis` and disabled admin APIs:
70-
Most of the C-Chain configuration options can be found in the [Avalanche C-Chain Configuration docs](https://build.avax.network/docs/nodes/chain-configs/c-chain).
70+
Most of the C-Chain configuration options can be found in the [Avalanche C-Chain Configuration docs](https://build.avax.network/docs/nodes/chain-configs/avalanche-l1s/subnet-evm).
7171
Note that the default values are overridden only if specified in the given config file.
7272
Only provide values which differ from the defaults to avoid issues with future updates.
7373

@@ -185,7 +185,7 @@ This ensures your node always starts with the correct `Node-ID`.
185185

186186
```bash
187187
# Find the latest tag at [https://hub.docker.com/r/flarefoundation/go-flare/tags](https://hub.docker.com/r/flarefoundation/go-flare/tags)
188-
LATEST_TAG="vX.Y.Z" # e.g., v1.11.0
188+
LATEST_TAG="vX.Y.Z" # e.g., v1.12.0
189189

190190
# Mount the staking volume and set the staking path environment variables
191191
docker run -d --name flare-node \

0 commit comments

Comments
 (0)