Frequently Asked Questions
General
What is SnapsVault
SnapsVault is a community driven marketplace for standardized node snapshots, with a unified metadata format, a web UI for discovery, and a CLI for automation that together speed up node bootstraps and recovery.
Who is it for
Node operators, validator teams, and developers who need fast, reliable, and verifiable node bootstraps, plus contributors who publish snapshots for the ecosystem.
Coverage and types
Which networks are supported
Mainnet and testnet networks for several chains are supported, with archival and pruned options so operators can choose speed or history as needed.
What snapshot types exist
Archival provides full history and Pruned is optimized for size and faster start, with Custom variants planned for specialized use cases.
How often are snapshots updated
Typical update cadence is 4 to 48 hours, with the exact timestamp visible per snapshot in the Marketplace UI and SnapsOS outputs.
Marketplace UI
Where to browse
Use the Marketplace to search and filter snapshots by network, chain, type, block height, date, and contributor, then open details or copy direct download links.
What metadata is visible
Type, network and chain ID, block height or range, size, creation date, contributor, pruning method, and a SHA 256 checksum for integrity verification.
Provider metrics and sorting
Filters and sorting are available, along with provider transparency features like Provider Since, Networks Covered, and a Trusted Score.
SnapsOS CLI
What is SnapsOS
SnapsOS automates discovery, verification, download, unpacking, and application using standardized metadata consistent with the Marketplace catalogs.
How to install
On Linux and macOS use the one line installer, or download the correct binary from releases and add it to the PATH.
Key capabilities and flags
Search by chain or chain ID and type, select the latest by height, limit listings, use quiet mode to print only URLs, and run SHA 256 integrity checks by default.
Format and metadata
File formats
Snapshots are compressed archives, typically .tar.lz4, with .tar.gz used by some providers and tooling.
Required metadata fields
Each snapshot entry includes URL, size, creation date in ISO 8601, earliest and latest block height where applicable, type, and a SHA 256 checksum in a standardized JSON feed.
Why standardization matters
Consistent schemas enable reliable verification, automation in SnapsOS, and clear display in the Marketplace for safer and quicker node operations.
Integrity and safety
How to verify a snapshot
Compute a local SHA 256 on the downloaded archive and compare it with the published checksum before applying to a node.
Built in safeguards in SnapsOS
Default hash verification, schema validation, preflight checks for disk space and permissions, pruning compatibility checks, and safe apply behavior to the chosen home directory, with non root usage recommended.
Privileges
Run SnapsOS as a non root user in production and elevate privileges only when strictly required.
Contributing snapshots
How to publish your snapshots
Host a snapshots.json feed with your entries and add a contributor.json in the public registry via pull request under chains, network, and chain ID, pointing to your feed and update cadence.
Example contributor.json
Include contributor identity and contact fields plus one or more snapshot feed pointers with update period and type following the documented structure.
Pre PR checklist
Validate JSON format, ensure HTTPS availability and stable uptime, place files under the correct directory, and maintain freshness since outdated or unavailable feeds can be removed.
Public API
Is there an API
A read only API is planned with endpoints for snapshots, networks, network details, and latest snapshots, with filters for network, chain_id, and type.
Basics
The base path is planned under API v1, initial access is unauthenticated with rate limits, and common uses include freshness monitoring and CI automation.
Providers and trust (Coming Soon)
Provider Since
The date a provider first contributed to the registry and Marketplace, used as a tenure signal in UI contexts.
Trusted Score
A composite signal that considers tenure, number of snapshots, networks covered, snapshot freshness, and availability to surface reliable providers.
Where it appears
Shown in Marketplace listings and provider contexts, with more transparency features planned for the frontend.
Troubleshooting
Hash mismatch
Re-download the archive, check network stability, do not apply the snapshot until the checksum matches, and include the URL and local hash output when reporting.
Node fails after apply
Verify the client version and pruning compatibility, confirm configuration in the target home directory, ensure sufficient free disk space, and try a newer snapshot or a different type if needed.
Slow downloads
Choose recent snapshots, check bandwidth and routing, and prefer SnapsOS for a resilient download and verification flow.
Operations and best practices
Usage recommendations
Always verify the SHA 256 checksum before production apply and keep the CLI updated for fixes and new features.
Automation
Use quiet mode and flags in cron or systemd, rely on structured logs and exit codes for monitoring, and align UI and CLI filters for consistency.
Learn more
See Marketplace UI, Install and Use SnapsOS, Coverage, API Reference, and Contribute Snapshots for detailed workflows and examples.