Please enable JS

You You
Personas Personas®
Hubs Hubs
Connections Connections
Activity Activity
Privacy & Anonymity

Our technology is built on the idea that a user should trust the person authoring the personal data - not just the data itself (nor any block that holds it).

Our Vaults are distributed for security & anonymity and then federated for access, to enable atomic data ownership, ensuring no company, agency or analytics organisation can ever access your private data without your permission.

Each Vault is completely anonymous, and has no detectable relationship to any other Vault in the network. Only the owner of a Vault knows its connections & relationships to other Vaults in the network. A Vault can store any form of data, and the owner is free to publish cryptographically signed sets of data called Artefacts® from their Vault, either to the public at large or other specific Vaults. These shared relationships between Vaults form the VaultChain® (see below).
Even when publishing data - publically or privately, the information is disclosed in such away so as to only reveal the specific data published, without exposing any other related information, or metadata.
The VaultChain is split into partitions called 'Hubs'. A Hub allows Vault owners to control & share information in their own private partition of the VaultChain, again, only publishing information publically as they choose. An owner can create an unlimited number of Vaults and join or create an unlimted number of Hubs. The connections between Hubs and their Vaults defines their scope of the VaultChain.
Creating a Hub never reveals any information about the owner, their connections, or the data any Vault in it might - or might not contain. The owner's primary Vault, known as their Guardian Vault is never directly connected to any authentication process, and only the owner is able to identify their own Vault out of the 10's of millions in the network.
The Octopus VaultChain solves 3 core Blockchain challenges: Storage, Scalability & Privacy
  • Storage burden: As a Blockchain grows in size the cost of maintaining a full node rises and so fewer participants exist to form a consensus. In a VaultChain only those that want to hold or verify the data store the data. This places the burden of storage of long term data onto those that need the data.

  • Trust relationships: Hubs partition the size of the VaultChain to relevant participants, allowing owners to trust groups of network participants rather than just chains of hashed blocks. Hubs allow allow certain partitions of the VaultChain to operate with higher levels of trust than others.

  • Reputation: Because VaultChains are multi-node directed graphs, decentralised trust is built on network reputation & distance rather than proof-of-work.

  • Anonymity: Data stored in a VaultChain is built from anonymised linked data sets, the data can be retrieved and aggregated from multiple Vaults into large queryable graphs without breaking network anonymity. Sub-graphs within the dataset can be validated by different network participants.

  • Zero-knowledge: A VaultChain uses zero-knowledge proofs to reference specific datasets so preserving anonymity, whilst ensuring the graph is still navigable.

  • Audit Trails: A VaultChain allows newer data to be stored, updated & referenced as part of a single piece of auditable data.

  • Compliant: Data can be permanently deleted from a VaultChain, but only when all members of a Hub holding that data agree to its deletion.