Check yourself: Immutable chunks

Questions and answers, readable without JavaScript.

1. What is the network storage primitive?

   • A mutable file path
   • A lease you renew
   • The wallet private key
   • An immutable, content-addressed chunk. Change the bytes and the address changes
   Answer 1

   An immutable, content-addressed chunk. Change the bytes and the address changes

   Autonomi 2.0's docs, as the note reads them, do not store a mutable file. The primitive is an immutable content-addressed chunk.

   Read the note → · Autonomi Stores Immutable Chunks — Public Address vs Private DataMap

2. How do public and private retrieval differ?

   • Public uses a different DHT
   • They are two stories over the same chunks. Public publishes the DataMap address; private keeps the DataMap with the client
   • Private skips encryption
   • Public data cannot be content-addressed
   Answer 2

   They are two stories over the same chunks. Public publishes the DataMap address; private keeps the DataMap with the client

   Public and private are not two machines. POST /v1/data/public returns an address. POST /v1/data returns a serialized DataMap without publishing it. Both still store chunks.

   Read the note → · Autonomi Stores Immutable Chunks — Public Address vs Private DataMap

3. What is an "update" on this store?

   • An overwrite at the same path
   • An edit the close group applies in place
   • A new upload that produces new chunk addresses
   • A rename of the wallet key
   Answer 3

   A new upload that produces new chunk addresses

   There is no honest overwrite at this path. A new version is a new upload. Old chunks remain as previously written.

   Read the note → · Autonomi Stores Immutable Chunks — Public Address vs Private DataMap