Skip to content

Commit 4e26652

Browse files
author
Will Binns
authored
Update hdd requirements and add snapshot info (#112)
* README: Update disk requirement * README: Add info regarding snapshots * README: s/500 GB/1 TB/
1 parent 3bf7383 commit 4e26652

1 file changed

Lines changed: 17 additions & 1 deletion

File tree

README.md

Lines changed: 17 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -32,7 +32,7 @@ This repository contains the relevant Docker builds to run your own node on the
3232
We recommend you have this configuration to run a node:
3333

3434
- at least 16 GB RAM
35-
- an SSD drive with at least 100 GB free
35+
- an SSD drive with at least 1 TB free
3636

3737
### Troubleshooting
3838

@@ -77,6 +77,22 @@ services:
7777
- $HOME/data/base:/data
7878
```
7979
80+
### Snapshots
81+
82+
If you're a prospective or current Base 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 Base chain on mainnet and/or testnet by using the following CLI commands. The snapshots are updated every hour.
83+
84+
**Mainnet**
85+
86+
```
87+
wget https://base-mainnet-archive-snapshots.s3.us-east-1.amazonaws.com/$(curl https://base-mainnet-archive-snapshots.s3.us-east-1.amazonaws.com/latest)
88+
```
89+
90+
**Testnet**
91+
92+
```
93+
wget https://base-goerli-archive-snapshots.s3.us-east-1.amazonaws.com/$(curl https://base-goerli-archive-snapshots.s3.us-east-1.amazonaws.com/latest)
94+
```
95+
8096
### Syncing
8197

8298
Sync speed depends on your L1 node, as the majority of the chain is derived from data submitted to the L1. You can check your syncing status using the `optimism_syncStatus` RPC on the `op-node` container. Example:

0 commit comments

Comments
 (0)