Verify architecture

3 min

The published read path stops after 10 shards verify. It does not call all 30, and a successful download is not an offline-host drill. See what verify checks.

Sonnet, verify that we receive a list of hosts from the Tessera API (count them, work out their IP locations). Verify that we write to exactly 30 of them. Verify that when we read back, we call all thirty shards of each slab, but we hang up the phone once the fast 10 have been received and decrypted. Also, what reply do we get from Tessera when we write a slab, to confirm it is successfully stored in the manifest?