# We’re Standardizing Tezos Snapshot Metadata
**URL:** https://forum.tezosagora.org/t/we-re-standardizing-tezos-snapshot-metadata/5090
**Category:** Project Updates
**Tags:** metadata
**Created:** [February 5, 2023, 11:41pm UTC](https://forum.tezosagora.org/t/we-re-standardizing-tezos-snapshot-metadata/5090 "2023-02-05T23:41:25Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@jorcutt](https://forum.tezosagora.org/u/jorcutt)
#### Post date: [February 5, 2023, 11:41pm UTC](https://forum.tezosagora.org/t/we-re-standardizing-tezos-snapshot-metadata/5090/1 "2023-02-05T23:41:25Z")
There are many providers for what we like to call “Tezos node storage artifacts”- snapshots and tarballs of Tezos filesystems. There are also many tools that rely on these artifacts and require information about their block height, size, etc.
Metadata about these artifacts is important, and the metadata consistency- even more so.
```bash
curl https://xtz-shots.io/tezos-snapshots.json
```
This is a collection of metadata for all of the Tezos node storage artifacts (snapshots and tarballs) we are currently offering on xtz-shots.
```bash
https://xtz-shots.io/
```
For tools like Tezos Packaging, Kiln, and BakeBuddy to work correctly- expected information (metadata) about these artifacts needs to be consistent. This is why we’re creating a standard form on xtz-shots for all providers to follow and collaborate on.
Oxhead Alpha’s tool to deploy tezos nodes in the cloud tezos-k8s also utilizes this metadata. When launching a node for a given network (mainnet, ghostnet…), the right artifact will be automatically downloaded and your new nodes will be synced in minutes.
We are hosting a public schema repo ([github.com/oxheadalpha/tezos-snapshot-metadata-schema](https://github.com/oxheadalpha/tezos-snapshot-metadata-schema)) that we hope the community will use to discuss and suggest changes/improvements.
This schema will be released to [oxheadalpha.com/schema](http://oxheadalpha.com/schema) and hopefully other providers will use it as the community iterates and collaborates on it.
The metadata for all Tezos node storage artifacts (snapshtos and tarballs) will validated against this schema so you can rest assured that the data you expect will be there, and your tools will work as expected.
If other providers follow suit you can also rest assured your tools will work with their artifacts as well!
---
### Author:  [@fraidev](https://forum.tezosagora.org/u/fraidev)
#### Post date: [March 21, 2023, 10:30am UTC](https://forum.tezosagora.org/t/we-re-standardizing-tezos-snapshot-metadata/5090/2 "2023-03-21T10:30:58Z")
Now our Snapshots API from Marigold is using the new standard:
> curl [https://snapshots.tezos.marigold.dev/api/tezos-snapshots.json](https://snapshots.tezos.marigold.dev/api/tezos-snapshots.json)
or just:
> curl [https://snapshots.tezos.marigold.dev/api](https://snapshots.tezos.marigold.dev/api)
It’s possible to visualize them on our frontend as well, on:
> [https://snapshots.tezos.marigold.dev](https://snapshots.tezos.marigold.dev/)
---
### Author:  [@nicolasochem](https://forum.tezosagora.org/u/nicolasochem)
#### Post date: [March 21, 2023, 5:44pm UTC](https://forum.tezosagora.org/t/we-re-standardizing-tezos-snapshot-metadata/5090/3 "2023-03-21T17:44:04Z")
Nice! @NomadicLabs next? 😉
Also, I found this interesting: [Introducing Chia Blockchain Database BitTorrent Checkpoints - Chia Network](https://www.chia.net/2023/03/19/introducing-chia-blockchain-database-bittorent-checkpoints/)