Snapshot Download
Last updated 21 February 2024
Syncing a fresh new node will take quite a while. You may use snapsync you or may download and use the following snapshots.
After you download the .tgz file, you can untar it into ~/.opera (or any path of your choice). Then you can run opera command with the default datadir ~/.opera (or you can specify a custom path: --datadir <path>).
Pruned data
Pruned snapshot can be used for: (1) a read node, or (2) a validator node. If you'd run an API node, please use non-pruned snapshot.
Snapshot URL | Version | Run | Size |
1.1.3-rc.5 | --db.preset ldb-1 | Pruned |
Snapsynced snapshot can be used for a read node. It can be used for validator node, but it's best to use full sync for validator node.
Snapshot URL | Version | Run | Size |
1.1.3-rc.5 | --db.preset ldb-1 (snap-synced snapshot) | Pruned |
Non-pruned data
Non-pruned snapshot can be used for: (1) a read node, (2) a full archive API node, or (3) a validator node.
Snapshot URL | Version | Run | Size |
1.1.3-rc.5 | --db.preset ldb-1 | Full |
Trace data
Trace snapshot can be used for an Trace API node.
Snapshot URL | Version | Run | Size |
1.1.3-rc.5 | --db.preset pbl-1 | Full |
Steps
Steps to download snapshot and untar:
mkdir ~/download
cd ~download
Then download the tgz, then untar
tar zxvf <tgz_file>
If the download URL contains multiple (split) tgz files, such as *_split_x.tgz, then you can download and untar them separately.
After untarring is finished, you will have ~/download/.opera/chaindata.
Option 1: remove and use the newly untarted chaindata folder
# remove ~/.opera/chaindata if it exists, and then:
mv ~/download/chaindata ~/.opera
Option 2: replace the old ~/.opera with the new ~/download/.opera
#remove ~/.opera if it exists, make sure you backup the keystore folder.
# then move the untarred .opera into a path (e.g., home)
mv ~/download/.opera ~
Checksum
You can also download md5 checksum file <tgz_file>.md5.
Last updated