Overview

This page introduces the concepts that matter most when you build on Autonomi.

Storage model

Autonomi stores data as immutable, content-addressed chunks. The developer-facing storage surfaces in this docs set are public data, private data, chunks, files, directories, and DataMaps. Public workflows return an address that can be shared; private workflows return retrieval metadata that you keep client-side.

Read more in Data Types.

Keys, addresses, and DataMaps

Wallet keys pay for writes, public addresses retrieve public data, and DataMap values are the critical retrieval material for private data.

Read more in Keys, Addresses, and DataMaps.

Self-encryption

Before uploaded content is stored, it is encrypted and split into chunks. The self_encryption crate and the higher-level upload paths in ant-sdk and ant-core are responsible for producing the DataMap and chunk layout used later for retrieval.

Read more in Self-Encryption.

Post-quantum cryptography

The cryptography stack uses ML-DSA-65 for signatures and ML-KEM-768 for key encapsulation. Those algorithms matter most when you are reasoning about network identity, transport security, or the broader security model.

Read more in Post-Quantum Cryptography.

Payment model

Autonomi is designed around pay-once, immutable storage. Uploads are wallet-backed writes: you pay when you store data, then retrieve it later without recurring storage fees or retrieval payments.

Read more in Payment Model.

Reading guide

Start here depending on what you need next:

• If you are building an application: Data Types, then Store and Retrieve Data with the SDKs

• If you need to understand wallets, public addresses, and private retrieval material: Keys, Addresses, and DataMaps

• If you need to understand the encryption path: Self-Encryption

• If you need to understand upload costs and wallets: Payment Model, then Estimate Costs and Handle Upload Payments

• If you need the security context: Post-Quantum Cryptography