How it works
This page follows a snapshot from a contributor feed to a node operator in five stages: a JSON feed, an entry in the registry, a scheduled sync, a database, and access through the Marketplace, the SnapsOS CLI and the REST API.
The path
- Feed. Each listing has a JSON feed served over HTTPS, with any file name such as
index.json. It is a JSON array with one entry per snapshot: download URL, size, creation date, block height and SHA256 checksum. - Registry. One registry file per contributor and chain ID holds the contributor profile and the URL of each feed with its snapshot type and update period.
- Sync. The application reads the registry and every listed feed every 2 minutes.
- Database. Snapshots are stored and listed while they appear in their feed. Older ones stay available through the historical route of the REST API.
- Access. The stored data is available in the Marketplace, in the terminal with the SnapsOS CLI, and through the REST API for scripts.
Next steps
- Quickstart: find, download and restore a snapshot
- Glossary: the terms used across the docs
- Contribute snapshots: publish your own snapshots