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
The Full-Sync Node is an available software implementation of a read-only SKALE Node that can help decrease the load on the core nodes of your chain. Applications are commonly read-heavy compared to writes, meaning they pull data from the chain more often than push them. For applications that contain many reads, a full-sync node can help increase chain stability and speed by reducing the number of actions the core nodes on the chain must do, leaving them with a more extraordinary ability to handle transactions.
General Steps
Provision a machine
Notify core team of IP/IPs range (x.x.x.x:x.x.x.x) and SKALE Chain for full-sync.
Complete Full Sync setup
Node Machine Requirements
A Linux x86_64 machine
Ubuntu 18.04
8 physical cores
32GB RAM
100GB root storage
2TB attached storage
Node Network Requirements
Ports 80, 443, 3009, and 10000–18192, and ICMP IPv4 shouldn't be closed by external firewall
Node Software Prerequisites
16GB Swap
docker
docker-compose → 1.27.4
iptables-persistent, btrfs-progs, lsof, lvm2, psmisc, and apt packages
[NOTE]
Before proceeding, notify the core team of the IP address of your full-sync node. It's suggested to use an elastic IP for the whitelisted IP address.
Apply executable permissions to the downloaded binary:
chmod +x /usr/local/bin/skale
Test the installation
skale --help
4 Prepare .env file:
CONTAINER_CONFIGS_STREAM="2.2.0-sync-node.0"
ENDPOINT=[[By Validator], YOUR GETH/INFURA ENDPOINT]
MANAGER_CONTRACTS_ABI_URL="https://raw.githubusercontent.com/skalenetwork/skale-network/master/releases/mainnet/skale-manager/1.9.0/skale-manager-1.9.0-mainnet-abi.json"
IMA_CONTRACTS_ABI_URL="https://raw.githubusercontent.com/skalenetwork/skale-network/master/releases/mainnet/IMA/1.3.0/mainnet/abi.json"
DISK_MOUNTPOINT=[[By Validator], your attached storage /dev/sda or /dev/xvdd (this is an example. You just need to use your 2TB block device)]
DOCKER_LVMPY_STREAM="1.0.2-stable.0"
ENV_TYPE="mainnet"
SCHAIN_NAME=[[By Validator], SCHAIN NAME FOR YOUR SYNC NODE]
Init sync node:
skale sync-node init [ENV_FILE_PATH]
Wait until your sync node will be inited
After the node is successfully inited, wait until skaled will download the snapshot and starts catchup blocks (usually 15–30 minutes)
Setup SSL certs
Node SSL certificates support secure communication with sChain endpoints. By default, each node of a SKALE Chain listens on HTTP and WS ports. If SSL certs exist on the node, then HTTPS and WSS ports are also turned on.
The Full-Sync Node is an available software implementation of a read-only SKALE Node that can help decrease the load on the core nodes of your chain. Applications are commonly read-heavy compared to writes, meaning they pull data from the chain more often than push them. For applications that contain many reads, a full-sync node can help increase chain stability and speed by reducing the number of actions the core nodes on the chain must do, leaving them with a more extraordinary ability to handle transactions.
General Steps
x.x.x.x:x.x.x.x
) and SKALE Chain for full-sync.Node Machine Requirements
Node Network Requirements
Node Software Prerequisites
From Fresh Machine
[NOTE]
Before proceeding, notify the core team of the IP address of your full-sync node. It's suggested to use an elastic IP for the whitelisted IP address.
Installation
4 Prepare
.env
file:skaled
will download the snapshot and starts catchup blocks (usually 15–30 minutes)Setup SSL certs
Node SSL certificates support secure communication with sChain endpoints. By default, each node of a SKALE Chain listens on HTTP and WS ports. If SSL certs exist on the node, then HTTPS and WSS ports are also turned on.
To upload SSL certs to the node run:
To check the status of your certs run:
Once certs are uploaded, HTTPS/WSS endpoints should become available for your chain.
Full sync node update
Update full sync SKALE node on current machine
Options:
--yes
- update without additional confirmationArguments:
ENV_FILEPATH
- path to env file where parameters are defined[NOTE]
You can just update a file with environment variables used during
skale sync-node init
.Maintenance
Maintenance commands are not available for a sync node.
The text was updated successfully, but these errors were encountered: