# Snapshot

<figure><img src="https://github.com/takeshi-val/Logo/raw/main/pylons.png" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Snapshots allows a new node to join the network by recovering application state from a backup file. Snapshot contains compressed copy of chain data directory. To keep backup files as small as plausible, snapshot server is periodically beeing state-synced.
{% endhint %}

Snapshots are taken automatically every 6 hours starting at **02:00 UTC**

**pruning**: 100/0/19 | **indexer**: null | **version tag**: v0.2.0

| BLOCK   | AGE     | DOWNLOAD                                                                            |
| ------- | ------- | ----------------------------------------------------------------------------------- |
| 4106514 | 1 hours | [snapshot (1.02 GB)](https://snapshots.takeshi.team/pylons/snapshot_latest.tar.lz4) |

## Instructions

### Stop the service and reset the data

```bash
sudo systemctl stop pylonsd
cp $HOME/.pylons/data/priv_validator_state.json $HOME/.pylons/priv_validator_state.json.backup
rm -rf $HOME/.pylons/data
```

### Download latest snapshot

```bash
curl -L https://snapshots.takeshi.team/pylons/snapshot_latest.tar.lz4 | tar -Ilz4 -xf - -C $HOME/.pylons
mv $HOME/.pylons/priv_validator_state.json.backup $HOME/.pylons/data/priv_validator_state.json
```

### Restart the service and check the log

```bash
sudo systemctl start pylonsd && sudo journalctl -u pylonsd -f --no-hostname -o cat
```


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://services.takeshi.team/chain/mainnet/pylons/snapshot.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.