Current flow

The current setup, in which a single iroh node, per validator, is running in a docker container.

Upload

• rust-recall -- http --> objects
  • temp-{hash}-{upload_id}
• objects api adds the blob to the local iroh node
• entangler
  • ent-{uuid} for each entangled blob
• temp-seq-{hash_seq_hash}
  • sequence contains metdata + references to the entangeled blobs

Commitment

• resolver resolves temp-seq-{hash_seq_hash}
  • the nodeid of the proposing validators iroh node is stored as source on chain
  • the propsing one from the local iroh node
  • other validators download from the propsing one, based on the source field
• on quorum reached
  • add store-seq-{hash_seq_hash}
  • rm temp-seq-{hash_seq_hash} (only relevant to the one adding the data)

Download

• rust-recall -- http -> objects
  • GetObject by key
  • /v1/objects/{address}/{key}
• objects server
  • resolves key -> hash_seq_hash / metadata
• entangler
  • download data using hash and recovery_hash from the local iroh node

New Flow (iroh@0.33)

The new setup, in which an iroh node is running embedded in the resolver, as well as the objects server.

iroh-r: iroh node in the resolver iroh-o: iroh node in the objects server

Upload

At this stage data is only stored in the iroh-o node.

• rust-recall -- http --> objects
  • temp-{hash}-{upload_id}