A
A
Akord docs
Akord protocol
Search…
⌃K

Concepts

Learn some of the key concepts in the Akord protocol.

Vaults

The Akord protocol is built to facilitate the creation of a vault – a secure and dynamic on-chain space. In the vault, one or more members can join and interact with the vault by uploading files or posting messages.

Memberships

Each vault allows for members to join. Members have an assigned access level (owner, contributor, or viewer). Each time a member is added or removed, the protocol rotates the encryptions, preventing old members from viewing new data.

Stacks

In an Akord vault, files and other assets are organized as 'stacks'. A stack represents one single file and all the subsequent revisions that may come after.

Nodes

Abstracted as a data object in the vault, a node functions as a pointer to data with in a context. Nodes contain a hash to some external data. Nodes can refer to a parent node to establish a hierarchical or group-based topography. Nodes can also refer to a previous version of itself, enabling auditing of immutable data.

Permaweb

The Arweave blockchain enables paid up front, permanent storage. As a fundamental data layer, the blockchain provides provable, immutable and perpetual data storage, on chain. This data made available to the web through the 'permaweb' layer. Essentially, a set of services providing access to Arweave data.

Proof system

A proof system is a protocol between a prover and verifier. The prover holds a secret, say a birthdate, blood test results or net worth. The secret is encrypted.
The verifier would like to verify a statement about the secret with a high degree of conviction. For example, 'Are you at least 21?', ' Do you have at least $2m in assets?'
Using various encryption algorithms, developers can deploy proof chains to enable zero knowledge proofs between provers and verifiers.