Tezos is a proof-of-stake blockchain.
This website helps people operating Tezos nodes to synchronize to the head of the chain, so they are operational faster.
What is a snapshot?
A Tezos snapshot is a package containing Tezos chain data necessary for the node to synchronize to the network and validate blocks.
In the absence of a snapshot, running a Tezos node for the first time requires syncing the historical mainnet chain from its genesis on June 2018, which takes several days. Consequently, most people spinning up new nodes use a snapshot.
Importing a Tezos snapshot performs a sanity check of its contents. Consequently, it still takes a bit of time to import a snapshot- currently up to one hour on mainnet.
How to use
We provide permalinks: URLs that never change and reliably point to a recent snapshot. This allows to write automation where your node may automatically download a recent snapshot at first boot.
For example, to download a recent rolling snapshot of Tezos mainnet, simply do:
The run the import command.
All commands can be found in the snapshot page.
Tezos node version
We display the Tezos node version used for snapshot generation. For best results, use the same version to import your snapshot. The snapshot format may have changed.
What is a tarball ?
In addition to snapshot, we provide tarballs. Unlike snapshots, tarballs are raw archives of the Tezos node data directory, in lz4 format.
We provide 2 kind of tarballs:
Rolling tarballs are generated from our rolling snapshots. We take a rolling snapshot, import it into a node, then package its data directory into a tarball.
Effectively, by importing a tarball instead of a snapshot, you skip the snapshot import that the node would normally do.
Consequently, by importing a tarball, you can go from zero to a fully synced node in less time: currently it takes about 9 minutes to get a fully synced rolling node.
Archive tarballs contain the full backend data directory of an archive node, complete will all history of transactions since genesis. Archive snapshots do not exist, so importing a tarball is the only way of getting an archive node, short of syncing from scratch.
Most Tezos users do not need an archive node. It is mostly useful for indexing the entire chain.
Internal sanity checks
Before making tarballs available, we test them internally: we import them and make sure that the node starts and RPC becomes available.
Snapshot import performs some safety checks to ensure that the chain state that you are importing is consistent. In contrast, importing a tarball completely bypasses these checks. As a consequence, by importing a tarball, you entrust the tarball provider to give you the correct mainnet chain.
Please evaluate whether this is appropriate for your use case. If not, you may elect to use a snapshot or generate your own tarballs.
How to use a tarball?
For example to expand one of our tarballs for a mainnet archive node -
curl -LfsS "https://mainnet.xtz-shots.io/archive-tarball" \ | lz4 -d | tar -x -C "/var/tezos"
The XTZ-Shots platform provides metadata for programmatic interaction with the service.
Query a json-formatted list of all artifacts available on the platform:
jq command-line tool, you can filter through the snapshots to find the one you need.
# Find the most recent mainnet rolling tarball built with Octez v15: curl -s https://xtz-shots.io/tezos-snapshots.json | jq '[ . | select(.chain_name == "mainnet") | select(.artifact_type == "tarball") | select(.history_mode == "rolling") | select(.tezos_version | contains("(15")) ] | sort_by(.block_height) [-1]'
We also provide metadata permalinks to gather all information for the most recent artifacts available on the platform.
curl -L https://mainnet.xtz-shots.io/rolling-snapshot-metadata curl -L https://mainnet.xtz-shots.io/rolling-tarball-metadata curl -L https://mainnet.xtz-shots.io/archive-tarball-metadata
We are generating these artifacts in a Kubernetes environment.
The snapshot engine can be deployed as a tezos-k8s Helm chart.
Brought to you by Oxhead Alpha
We are Oxhead Alpha, a blockchain infrastructure company.
We maintain a series of open source infrastructure projects to further the tezos ecosystem of open-source software projects to deploy secure bakers and nodes.
Users are solely responsible for any risks associated with usage of the Tezos network. Users should do their own research to determine if Tezos is the appropriate platform for their needs and should apply judgement and care in their network interactions.
Unless required by applicable law or agreed to in writing, Oxhead Alpha provides a service on an “AS IS” BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using our services.