Skip to content

Commit 844ddd1

Browse files
committed
doc: update validators docs
1 parent d8ee8d5 commit 844ddd1

File tree

2 files changed

+26
-299
lines changed

2 files changed

+26
-299
lines changed

docs/misc/adding_validators.md

Lines changed: 26 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -11,6 +11,32 @@ It covers generating keys using `subkey` via Docker, starting the node, insertin
1111
- **Polkadot.js Browser Extension**: For managing accounts and signing transactions.
1212
- **Basic Knowledge**: Familiarity with command-line operations and blockchain concepts.
1313

14+
## Hardware
15+
16+
### Requirements
17+
18+
The most common way for a beginner to run a validator is on a cloud server running Linux. You may choose whatever VPS provider that you prefer, and whatever operating system you are comfortable with.
19+
For this guide we will be using Ubuntu 22.04, but the instructions should be similar for other platforms.
20+
21+
The transactions weights in TFchain were benchmarked on standard hardware. It is recommended that validators run at least the standard hardware in order to ensure they are able to process all blocks in time. The following are not minimum requirements but if you decide to run with less than this beware that you might have performance issue.
22+
23+
#### Standard Hardware
24+
25+
- CPU
26+
- x86-64 compatible;
27+
- Intel Ice Lake, or newer (Xeon or Core series); AMD Zen3, or newer (EPYC or Ryzen);
28+
- ~4~ 8 physical cores @ 3.4GHz;
29+
- Simultaneous multithreading disabled (Hyper-Threading on Intel, SMT on AMD);
30+
- Prefer single-threaded performance over higher cores count. A comparison of single-threaded performance can be found here.
31+
- Storage
32+
- An NVMe SSD. Should be reasonably sized to deal with blockchain growth. Minimum around 80GB but will need to be re-evaluated every six months.
33+
- Memory
34+
- ~32~ 64 GB DDR4 ECC.
35+
- System
36+
- Linux Kernel 5.16 or newer.
37+
38+
The specs posted above are not a hard requirement to run a validator, but are considered best practice. Running a validator is a responsible task; using professional hardware is a must in any way.
39+
1440
## 1. Generate Keys
1541

1642
### 1.1 Generate the Validator Account Key

docs/misc/creating_validator.md

Lines changed: 0 additions & 299 deletions
This file was deleted.

0 commit comments

Comments
 (0)