. Next, in the home directory of your (i.e. the `base` folder), create a folder named `geth-data`. If you already have this folder, remove it to clear the existing state and then recreate it. Next, run the following code and wait for the operation to complete.
As downloading a snapshot takes about 9 hrs it is better to run it in a screen session
```
screen -S archive
```
Use `aria2c` to download the most recent Mainnet Archive Snapshot
cd ~/base
aria2c --file-allocation=none -c -x 10 -s 10 "https://base-snapshots-mainnet-archive.s3.amazonaws.com/$(curl https://base-snapshots-mainnet-archive.s3.amazonaws.com/latest)"
*press `ctrl+A and D` to return to previous screen and continue installation*
```bash
screen -r archive #will bring you back to monitor downloading progress
```
You'll then need to untar the downloaded snapshot and place the geth subfolder inside of it in the geth-data folder you created (unless you changed the location of your data directory)
```bash
tar -xvzf filename.tar.gz
# tar -xvzf base-mainnet-archive-1712388985.tar.gz
```
Next, you’ll need to move the snapshot to the where the geth data was stored in the docker container. If you initially tried to sync the node from scratch and are now trying with a snapshot:
```bash
cd /var/lib/docker/volumes/base_geth_data/_data
rm -rf geth
cd ~/base/snapshots/mainnet/download/
mv ~/base/snapshots/mainnet/download/geth /var/lib/docker/volumes/base_geth_data/_data/
cd /var/lib/docker/volumes/base_geth_data/_data/
ls
```
### Run Base Node
```bash
cd ~/base
docker-compose up -d
```
### Monitor Logs
Use `docker logs` to monitor your geth and op-node. The `-f` flag ensures you are following the log output
```
docker logs geth -f --tail 100
docker logs opnode -f --tail 100
```
Once your Base node starts syncing, the logs should look like this:
for op-geth:
```bash
INFO [05-14|00:11:15.654] Imported new potential chain segment number=14,428,064 hash=581e26..7e597a blocks=1 txs=43 mgas=5.638 elapsed=82.078ms mgasps=68.687 snapdiffs=161.36KiB triedirty=0.00B
INFO [05-14|00:11:15.656] Chain head was updated number=14,428,064 hash=581e26..7e597a root=01059a..8a2f59 elapsed=1.210252ms
INFO [05-14|00:11:17.759] Aborting state snapshot generation root=2c98d7..a0d61d in=0c4e7d..ec261d at=5aebd1..a6a6dc accounts=3,270,959 slots=6,006,594 storage=650.88MiB dangling=0 elapsed=7m17.533s eta=2h24m23.981s
INFO [05-14|00:11:17.759] Resuming state snapshot generation root=e19a42..4325ec in=0c4e7d..ec261d at=5aebd1..a6a6dc accounts=3,270,959 slots=6,006,594 storage=650.88MiB dangling=0 elapsed=7m17.534s eta=2h24m24.001s
INFO [05-14|00:11:17.790] Imported new potential chain segment number=14,428,065 hash=ad1eb4..fa4c07 blocks=1 txs=47 mgas=7.296 elapsed=135.218ms mgasps=53.955 snapdiffs=166.58KiB triedirty=0.00B
```
for op-node:
```bash
t=2024-05-13T22:02:48+0000 lvl=info msg="Received signed execution payload from p2p" id=0x303089f3d89660725bfccad20d306eab71eb97dc59cf87baee419d103bae13ae:14424210 peer=16Uiu2HAmEjC9jKoKzZhM4zLHrfDGth9DTL287asWALv5JY8f5UeN
t=2024-05-13T22:02:48+0000 lvl=info msg="Optimistically queueing unsafe L2 execution payload" id=0x303089f3d89660725bfccad20d306eab71eb97dc59cf87baee419d103bae13ae:14424210
t=2024-05-13T22:02:48+0000 lvl=info msg="Sync progress" reason="unsafe payload from sequencer" l2_finalized=0x52677a4adc91111968ee08ef4e56e2fdeb89ff71ba233c7331a227175e56365f:14407839 l2_safe=0xfb6626d86728c555db2e0722e38341f79a6646ed1955a488a9ef9df5862c2064:14407925 l2_pending_safe=0xfb6626d86728c555db2e0722e38341f79a6646ed1955a488a9ef9df5862c2064:14407925 l2_unsafe=0x303089f3d89660725bfccad20d306eab71eb97dc59cf87baee419d103bae13ae:14424210 l2_time=1715637767 l1_derived=0x6380d5a1c889e951981d6c34cfb347671650b3a5f64ab2fbd4d4a2f1d7f77fe5:19861259
t=2024-05-13T22:02:48+0000 lvl=info msg="Advancing bq origin" origin=0x153e0928fe8b7dbbe93f227af8c1364e8c181bf5fb9a5412ccb92027299ee648:19861260 originBehind=false
t=2024-05-13T22:02:50+0000 lvl=info msg="Reading channel" channel=004ac887def59644f5fc6c46a1c244ae frames=6
t=2024-05-13T22:02:50+0000 lvl=info msg="Found next batch" batch_type=SpanBatch batch_timestamp=1715605199 parent_check=0xfb6626d86728c555db2e0722e38341f79a6646ed origin_check=0x1f1df86ea9abd1140e95d5bdd2b7211a4cda56ef start_epoch_number=19861236 end_epoch_number=19861252 block_count=88
t=2024-05-13T22:02:50+0000 lvl=info msg="generated attributes in payload queue" txs=37 timestamp=1715605199
```
{% code overflow="wrap" %}
```bash
curl --data '{"method":"eth_syncing","params":[],"id":1,"jsonrpc":"2.0"}' -H "Content-Type: application/json" -X POST https://{YOUR_DOMAIN}
```
{% endcode %}
The result will return `false` if a node is fully synced
**Alternatively you can run**
```bash
curl -d '{"id":0,"jsonrpc":"2.0","method":"eth_getBlockByNumber","params":["latest",false]}' \
-H "Content-Type: application/json" https://{YOUR_DOMAIN}
```
and it will return more details about syncing progress
{% hint style="warning" %}
Sync speed will be highly dependent on your Layer 1 RPC
{% endhint %}