DA nodes should provide a simple api for any node to read and write data blobs, and be agnostic to the underlying DA blob encoding scheme.

General Nomos DA flow

  1. Data Object is “chunked” by the Zone
  1. Chunks are dispersed to the nodes (ideally all)
  1. The certificate (Blob Certificate in Block - ‣) is created after Zone receives the attestations from the nodes that they will try to “persist” the chunks.

  2. The certificate is sent to the DA mempool of Nomos node by the Zone

  3. The block producer picks the certificate form the DA specific mempool and writes it into the block

  1. When a DA node receives a new block, it double checks if it has data to be written, related to the certificates that are included in the block.
  1. The data chunks for AppID should be available in DA nodes via the READ API shortly after the block is considered available in the blockchain

  2. When a client wants to query a specific range (or sequential nonce) of rows from a node for a specific blob, it has to provide the AppID for witch to retrieve data for and provide the range of "nonces".

Verifiable Information Dispersal Certificate (VID Certificate)

The VID Certificate is a crucial part of ensuring data integrity in Nomos DA. It's created as part of chunk dissemination process by Nomos Zone and is used by Block Producer to verify the dissemination:

Metadata Required from NZ to Block Producer

When the NZ sends the VID Certificate to the Block Producer, it includes essential metadata about the DataBlob. This metadata consists of: