Eventually Consistent Hierarchical Object Store supporting multiple concurrent writers and latent offline writers.
A protocol, application, and SDK for managing a decentralized user identity for end users and developers.
The set of peer networking technologies behind ECHO, HALO and KUBE.
A reslilient, self-contained set of services for hosting and supporting decentralized applications.
An ECHO replication domain containing objects which all the peers in the space replicate continuously.
A unit of data in a space, a bag of properties and values with a type and identity.
A service provided by DXOS KUBEs which helps peers locate each other on the network and establish peer-to-peer connections.
A special generated code or URL containing one which is used for peers to identify each other when joining a space.
A second factor provided to the invited member by the inviter to verify their identity when joining a space.
A value identifying a particular space.
Represents an agent or actor in the system.
ECHO data and HALO identities are physically stored in browser storage on the HALO application's domain, not the consuming application's. This enables data privacy and gives end-users control over their data. Read more about HALO vault topology.
A running instance of the DXOS
Client represents a device on the network. Every browser profile acts as a device. A CLI application is it's own device. HALO replicates identity and credential information across devices securely and automatically and supports device revocation.
Also known as a paper key. A string of values that make it possible to recover an identity in case of a lost device.
A flat representation of a specific state of an ECHO space. An ECHO space is made of feeds of mutations which are collapsed into a snapshot for the purposes of catching up a peer or downloading the state of the database without the log of changes.
A specific point in time when the members of a space agree to drop or compress history older than a certain point in time. To call an epoch, peers periodically agree on a specific snapshot to refer to as the beginning of the current epoch. This mechanism allows ECHO spaces to control their size on disk and on the wire.
The vault implements a few generic UI flows for managing spaces, membership, and identity. The shell can be invoked by the dxos client API and is rendered by the Vault in an iframe, minimizing impact to the consuming application.