IPFS Storage
Coming Soon
IPFS integration is under active development and will be available soon.
All ZecNames data — proofs, the Merkle tree state, and the full registry — will be pinned to IPFS for added decentralization.
Why IPFS?
Today, proofs and registry data are served from a centralized API. If the API goes down, you can still reconstruct everything from the Zcash blockchain, but that takes time. IPFS adds a middle layer:
- Proofs are content-addressed — the IPFS hash of a proof is deterministic. Anyone can fetch and verify it without relying on the ZecNames API.
- Registry snapshots — periodic snapshots of the full Merkle tree state, pinned to IPFS. Any node can serve the data.
- No single point of failure — even if the API server goes offline, all data remains accessible on the IPFS network.
What Will Be Stored
| Data | Description |
|---|---|
| SP1 proofs | Every registration proof, individually addressable |
| Merkle tree snapshots | Full SMT state at each block with changes |
| Proof chain index | Ordered list of all proofs with their IPFS CIDs |
This means anyone can run a fully independent verifier using only the Zcash blockchain and IPFS — no reliance on the ZecNames API at all.