Skip to main content

Storage

This section covers how Tessera manages data storage, including sharding, chunk distribution, and network storage patterns.

Overview​

JAM's storage model distributes exported data chunks across the network in a sharded manner, ensuring:

  • Data availability: Work-package outputs and state chunks are retrievable
  • Sharding: Efficient distribution of storage responsibilities across validators
  • Chunk distribution: Erasure coding and availability guarantees
  • Network storage patterns: How chunks are requested, stored, and served

Topics in this section​

4.1 Sharding & Chunk Distribution​

How exported data is divided and distributed:

  • Erasure coding for availability and reconstruction
  • Chunk assignment to validators
  • Storage responsibilities per shard
  • Data export and import flows

References: Gray Paper sections on erasure coding, data availability, and exports

4.2 Network Storage Patterns​

Network protocols for storage operations:

  • Chunk request/response protocols
  • Availability store management
  • Chunk retrieval and serving
  • Storage pruning and retention policies

References: JAMNP-S specification for chunk distribution protocols

Implementation notes​

The storage layer is implemented in tessera/jam/storage/ with network protocols in tessera/jam/network/protocols/ (CE 140-143 for chunk distribution).

📘 Next: Explore storage implementation details in the codebase