Autonomi
LearnBuildWho we ArePublicationsGet ANTStart a Node
  • Learn
  • Node
  • ANT Token
  • Developers
  • Autonomi Docs
  • Introduction
    • What is Autonomi?
      • The Internet's Crowd Storage Layer
      • Everything's Encrypted
      • Lifetime Storage; One Time Fee
      • Built From Everyday Devices
      • Private by Design
      • Blockchainless Data
      • Secure & Efficient
    • Background
    • A Self-Organizing System
    • Fundamental Principles
    • Key Features
  • How It Works
    • Overview
    • Fully Autonomous Data Network
      • A Serverless Web
      • Nodes
      • Clients
    • Network Architecture
      • Building on Kademlia
      • libp2p
      • Content-Addressable Storage
    • Encryption and Authentication
      • Self-Encryption
      • Multilayered encryption
      • Self-Authentication
      • Multisig Credentials
    • Network Economics
      • Key Properties
      • Token Supply
      • Gas Fee
      • Quote Calculations
    • Consensus Not Required
      • Stigmergy
      • Conflict-free Replicated Data Types
    • Data types
      • Chunks
      • Registers
    • Defence Against Cyberattacks
      • Beating Common Threats
  • Learn More
    • Team
    • Autonomi Foundation
    • FAQs
    • Glossary
    • References
Powered by GitBook

Get Involved

  • Start a Node
  • Discord
  • Forum

Follow Us

  • X
  • Reddit
  • LinkedIn
On this page
  1. How It Works
  2. Encryption and Authentication

Self-Encryption

PreviousEncryption and AuthenticationNextMultilayered encryption

Last updated 12 months ago

All content (documents, images, videos, etc.) on Autonomi are encrypted.

When a client uploads a piece of content to the Network (for example a video) it is first broken into chunks. Those chunks are then ‘self-encrypted’, a process patented by MaidSafe by which each chunk is encrypted using its own hash and the hashes of the two previous chunks in the same file. These encrypted chunks are then hashed again to arrive at the XOR Network address where the chunk will be stored.

At the same time, a ‘data map’ is created on the client device, which maps the chunk number to the XOR network address of the chunk and the hash to decrypt it and its two successors, allowing the content to be recreated. A number of copies of each chunk are stored by nodes in the Section to ensure redundancy.

Data maps and other metadata are not encrypted, but on the network they are kept inside encrypted folders if the data is private.

The client retains the data map for the content it has uploaded and keys to decrypt it locally. That way no keys or passwords need ever leave a person's device. Users can choose to share content with others by sharing their keys / data map with them. They can also choose to make the content fully public, in which case the folders containing the relevant files are unencrypted.

Deeper Dive…

[PDF]

Self-encrypting Data — MaidSafe White-paper (2010)