Swan Node Snapshots
This guide provides an advanced optimization method for SWAN Node operators looking to expedite their node initialization process. As a complementary resource to the Node Operator guide, snapshots offer a time-saving alternative to full chain synchronization.
Key Components
Hardware Requirements
8-Core CPU
Minimum 16 GB RAM
Locally attached NVMe SSD
Sufficient storage (recommended: 2 * current chain size + snapshot size + 20% buffer)
Prerequisite
This tutorial assumes you are familiar with Docker and have it running on your machine.
Running a Swan Node
This tutorial will walk you through setting up your own Swan Node, you can see here: https://docs.swanchain.io/bulders/swan-node
Snapshots
If you're a prospective or current SWAN Node operator and would like to restore from a snapshot to save time on the initial sync, it's possible to always get the latest available snapshot of the Swan chain on mainnet by using the following CLI commands. The snapshots are updated every two weeks.
Snapshot Restoration Process
In the home directory of your SWAN Node, create a folder($SWAN_NODE_DATA
). If you already have this folder, remove it to clear the existing state and recreate it. Next, run the following code and wait for the operation to complete.
Init Swan Node configuration
Download the snapshot and untar it
Swan Mainnet Snapshot:
You'll then need to untar the downloaded snapshot and place the $SWAN_NODE_DATA/data/geth/
subfolder
Start Swan node
L1RPC
URL andL1BEACON
You'll need your own L1RPC
URL and L1BEACON
URL. This can be one that you run yourself.
Run the docker command
Confirm you get a response from:
Check the node sync status
Last updated