KERIOX is a Rust implementation of the Decentralized Key Management System (DKMS) that under the hood uses the Key Event Receipt Infrastructure (KERI) protocol.
The Human Colossus Foundation has been developing and maintaining KERIOX since 2020.
- For running example infrastructure (Witnesses, etc.), see https://github.com/THCLab/ambient-infrastructure
- Connect to the Infrastructure
- for Command-Line Interface (CLI)-based interaction, use
dkms-bin - for Rust client, see test.
- for FFI bindings (clients for different programming languages), see https://github.com/THCLab/keri-bindings
- for Command-Line Interface (CLI)-based interaction, use
KERIOX is an open-source Rust implementation of the Key Event Receipt Infrastructure (KERI) , a system designed to provide a secure identifier-based trust spanning layer for any stack. The current version of the KERI paper can be found here.
KERI provides the same security and verifiability properties for transactions as a blockchain or distributed ledger can, without the overhead of requiring an absolute global ordering of transactions. Because of this, there is no need for a canonical chain and thus there is no "KERI Chain" or "KERI Network". KERI Identifiers can be generated independently in a self-sovereign and privacy-preserving manner and are secured via a self-certifying post-quantum resistant key management scheme based on blinded pre-rotation, auditable and flexible key events and a distributed conflict resolution algorithm called KAACE.
EUPL 1.2
We have distilled the most crucial license specifics to make your adoption seamless: see here for details.
KERIOX implementation is in progress and ongoing. We support all the KERI protocol's significant features and provide the second most advanced implementation right after the keripy reference implementation.
We furthermore support bindings to NodeJS and Dart. See our keri-bindings repository.
This repository provides the implementation of the KERI protocol. keriox_core brings the core protocol features that are further consumed by the following concepts:
- Witness: the KERI Witness
- Watcher: the KERI Watcher
- Controller: the client for accessing the infrastructure