From 9c1c9583b7dbd201a1ce4f1573145b8a8af97618 Mon Sep 17 00:00:00 2001 From: Ikko Eltociear Ashimine Date: Thu, 16 Jan 2025 15:21:58 +0900 Subject: [PATCH] docs: update Validator-HOWTO accomodate -> accommodate --- doc/Validator-HOWTO | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/Validator-HOWTO b/doc/Validator-HOWTO index b5388231..e4716213 100644 --- a/doc/Validator-HOWTO +++ b/doc/Validator-HOWTO @@ -1,6 +1,6 @@ The aim of this document is to provide step-by-step instructions for setting up a full node for the TON Blockchain as a validator. We assume that a TON Blockchain Full Node is already up and running as explained in FullNode-HOWTO. We also assume some familiarity with the TON Blockchain Lite Client. -Note that a validator must be run on a dedicated high-performance server with high network bandwidth installed in a reliable datacenter, and that you'll need a large amount of Grams (test Grams, if you want to run a validator in the "testnet") as stakes for your validator. If your validator works incorrectly or is not available for prolonged periods of time, you may lose part or all of your stake, so it makes sense to use high-performance, reliable servers. We recommend a dual-processor server with at least eight cores in each processor, at least 256 MiB RAM, at least 8 TB of conventional HDD storage and at least 512 GB of faster SSD storage, with 1 Gbit/s network (and Internet) connectivity to reliably accomodate peak loads. +Note that a validator must be run on a dedicated high-performance server with high network bandwidth installed in a reliable datacenter, and that you'll need a large amount of Grams (test Grams, if you want to run a validator in the "testnet") as stakes for your validator. If your validator works incorrectly or is not available for prolonged periods of time, you may lose part or all of your stake, so it makes sense to use high-performance, reliable servers. We recommend a dual-processor server with at least eight cores in each processor, at least 256 MiB RAM, at least 8 TB of conventional HDD storage and at least 512 GB of faster SSD storage, with 1 Gbit/s network (and Internet) connectivity to reliably accommodate peak loads. 0. Downloading and compiling ~~~~~~~~~~~~~~~~~~~~~~~~~~~~