Keys, Addresses, and DataMaps
Autonomi keeps upload payment, public retrieval, and private retrieval separate.
Why it matters
If you are building on Autonomi, you need to understand three different things:
wallet keys pay for uploads
public addresses retrieve public data
DataMapretrieves private data
Treating those as one all-purpose developer key makes the rest of the system harder to understand.
What you handle
Wallet private key
You provide it
Pay for uploads
Public address
Returned after a public upload or public DataMap store
Share or store it, then use it to retrieve public data
DataMap
Returned after a private upload or saved locally by some tools
Store it safely, then use it to retrieve private data
Wallet private key
The wallet private key is used for paid writes.
Depending on the tool you use, that appears as:
AUTONOMI_WALLET_KEYforantdSECRET_KEYforantan attached
Walletinant-core
This key is about payment, not about private-data decryption.
Public address
A public address is what you use to retrieve data that has been published on the network.
When you upload public data or store a public DataMap, the tooling returns an address that other readers can use later. If the content changes, the address changes too, because the storage model is content-addressed and immutable.
DataMap
A DataMap is the private retrieval material that ties uploaded content back to its encrypted chunks.
For private data:
the chunks are still stored on the network
the
DataMapis returned to you instead of being stored publiclyif you lose that
DataMap, you lose the practical ability to retrieve the private content
That means DataMap handling is a data-access concern, not a payment concern.
Practical example
The simplest way to think about the split is:
use a wallet key when you need to upload data
use a public address when you want to retrieve public data
use a
DataMapwhen you want to retrieve private data
Upstream sources
Related pages
Last updated