> For the complete documentation index, see [llms.txt](https://service.block-pro.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://service.block-pro.net/mainnet/dora/snapshots.md).

# Snapshots

Restore Dora Mainnet data while preserving your validator identity.

**Mainnet · `vota-ash` · v1.1.0**

Restore recent chain data while keeping your own node configuration and validator identity. First install the binary and create the service using [Installation](https://service.block-pro.net/mainnet/dora/installation.md).

## Availability

| Provider | Source                                                                           | Availability                                                                    |
| -------- | -------------------------------------------------------------------------------- | ------------------------------------------------------------------------------- |
| BlockPro | [Snapshot directory](https://server-2.block-pro.net/dora/)                       | Publication interval: every 4 hours. Check the directory for a current archive. |
| ITRocket | [Mainnet snapshots](https://itrocket.space/services/mainnet/doravota/#snapshots) | Check the current archive height and version.                                   |
| Polkachu | [Mainnet snapshots](https://polkachu.com/tendermint_snapshots/dora)              | Check the provider's version and restore requirements.                          |

Use the BlockPro archive once it appears in the directory, or choose a current community snapshot. Do not construct a filename from an example date or height.

For the v1.1.0 binary, choose a **vota-ash snapshot that has completed the v1.1.0 upgrade**, at height **18,223,900 or later**, with a compatible database backend. The snapshot must include the completed-upgrade record; check the provider's version and compatibility notes as well as its height.

If no compatible post-v1.1.0 archive is available yet, use the [v1.0.1 binary](https://github.com/DoraFactory/doravota/releases/tag/v1.0.1) with a snapshot that has completed v1.0.1. Reach the local v1.1.0 halt at **18,223,900**, then follow [Upgrade](https://service.block-pro.net/mainnet/dora/upgrade.md). Older snapshots require the earlier upgrade sequence. The v1.1.0 binary checks that the required upgrades are active before executing blocks. [Upgrade guards](https://github.com/DoraFactory/doravota/blob/v1.1.0/app/app.go)

For ITRocket's alternative, the metadata below identifies its current archive.

```bash
curl -fsS https://server-1.itrocket.net/mainnet/doravota/.current_state.json | jq '{file: .snapshot_name, height: .snapshot_height, size: .snapshot_size, block_time: .snapshot_block_time, database: .db_backend}'
```

## Download and inspect

Use the same account and home directory as the node service. Ensure you have room for the compressed archive, extracted data and a copy of your current database. These steps expect a **tar.lz4 archive containing a top-level data directory**. If the provider uses another layout or compression format, adapt to its documented layout before continuing.

Do not restore a snapshot while another node is signing with the same validator key. Keep your latest local signing state; never use a provider's signing state in its place.

### Set the archive URL

Copy the actual current download URL from the selected provider.

```bash
read -rp "Current Dora Mainnet .tar.lz4 URL: " SNAPSHOT_URL
```

### Download the archive

Stop on download errors and do not continue with a partial file.

```bash
curl -fL --retry 3 "$SNAPSHOT_URL" -o "$HOME/dora-snapshot.tar.lz4"
```

### Test compression

Check the LZ4 stream before extraction. If the provider publishes a checksum, compare that too; this test alone does not authenticate a provider.

```bash
lz4 -t "$HOME/dora-snapshot.tar.lz4"
```

### Inspect archive paths

Confirm relative paths under data/. Reject absolute paths, parent-directory traversal and unexpected links. The procedure imports only data, not another operator's config or keys.

```bash
tar -I lz4 -tf "$HOME/dora-snapshot.tar.lz4" | less
```

### Create a staging directory

Extract outside the active node home.

```bash
DORA_RESTORE=$(mktemp -d "$HOME/dora-restore.XXXXXX")
```

### Extract the archive

Run as the node user, without sudo. Do not extract directly over the live home.

```bash
tar -I lz4 -xf "$HOME/dora-snapshot.tar.lz4" -C "$DORA_RESTORE" --no-same-owner --no-same-permissions
```

### Confirm the expected layout

Continue only if data/ exists at the staging root. If it does not, stop and follow the provider's documented archive layout.

```bash
test -d "$DORA_RESTORE/data"
```

## Preserve local identity and state

### Stop the service

Wait until the node has stopped before taking the final signing-state backup.

```bash
sudo systemctl stop dorad
```

### Check that the service is stopped

Expect inactive. Also stop any separate supervisor or manual process using this home.

```bash
sudo systemctl is-active dorad
```

### Create a private backup directory

Keep this shell open so the backup variable remains available.

```bash
DORA_BACKUP="$HOME/dora-backup-$(date +%Y%m%d-%H%M%S)"
```

### Restrict backup access

Create the directory with permissions limited to your user.

```bash
install -d -m 0700 "$DORA_BACKUP"
```

### Back up configuration

Preserve your own genesis, node key and validator key.

```bash
cp -a "$HOME/.dora/config" "$DORA_BACKUP/config"
```

### Back up the latest signing state

This must succeed. If the file is missing on a previously active validator, stop and recover its latest state before proceeding.

```bash
cp -a "$HOME/.dora/data/priv_validator_state.json" "$DORA_BACKUP/priv_validator_state.json"
```

### Preserve the current database

Move rather than delete the old data directory. The service must stay stopped.

```bash
mv "$HOME/.dora/data" "$DORA_BACKUP/data"
```

## Restore and verify

### Install the restored data

Move only the inspected data directory into the node home.

```bash
mv "$DORA_RESTORE/data" "$HOME/.dora/data"
```

### Restore your signing state

Overwrite the snapshot's signing state with your own latest local state before starting.

```bash
cp -a "$DORA_BACKUP/priv_validator_state.json" "$HOME/.dora/data/priv_validator_state.json"
```

Your config directory stays in place. Preserve any existing external `wasm/` bytecode for historical research; live Wasm execution was removed in v1.0.0, and v1.1.0 keeps the archive read-only. This guide does not replace that directory from a provider archive.

### Check snapshot settings

Keep statesync enable=false in config.toml when restoring an archive, and confirm the database backend matches the provider metadata. Do not change unrelated enable fields.

```bash
nano "$HOME/.dora/config/config.toml" "$HOME/.dora/config/app.toml"
```

### Start the service

Start only after successful restoration and ownership checks. The files should belong to the service account.

```bash
sudo systemctl start dorad
```

### Read startup logs

Check for database, version or network errors. If the v1.1.0 startup guard rejects the snapshot, stop and check that the restored state is compatible with this release.

```bash
sudo journalctl -u dorad -n 100 --no-pager -o cat
```

### Check synchronization

Confirm chain vota-ash, a current block time and catching\_up=false after catch-up.

```bash
curl -fsS http://127.0.0.1:26657/status | jq '.result | {chain: .node_info.network, height: .sync_info.latest_block_height, time: .sync_info.latest_block_time, catching_up: .sync_info.catching_up}'
```

Compare the height and block hash at the same height with an independent [public RPC](https://service.block-pro.net/mainnet/dora/services.md). Keep backups until recovery is verified. Do not restore an older signing-state file after this node has signed new blocks.

[v1.1.0 release and restoration notes](https://github.com/DoraFactory/doravota/releases/tag/v1.1.0) · [PQCAuth rollout notes](https://github.com/DoraFactory/doravota/blob/v1.1.0/docs/PQCAUTH-ROLLOUT-PLAN.md)
