Elysian Release

A Data Store for the new Web of Trust

The ixo protocol dictates how information which has been cryptographically secured is processed, distributed and ultimately stored. In the ixo ecosystem, these packets of data represent verifiable impact claims. Many now believe that merkelised private data stores are crucial to the building and long-term viability of many Web 3.0 applications, and are by no means limited to the ixo protocol.

The core ixo development team have been putting together a highly-customisable new database utility, combining the use of hash-chains with decentralisation, to build a set of new standards for the web of tomorrow. The team is now pleased to announce that this open-source protocol, Elysian, will soon be released.

Elysian, in Greek mythology, refers to a place accessible only to those permitted to do so by the gods — such as the righteous and the courageous. In the same vein, the protocol imbues users with a powerful toolkit for controlling access to private data in the cybersphere of the new internet. Only individuals possessing the correct credentials can gain access to Elysian data stores, thanks to the magic of decentralised authentication and applied cryptography.

In the context of ixo, particularly where impact data is concerned, this must be privately owned, with the permissions to access this at the discretion of the creator of a given project — claims will often include sensitive information and personal data, so it’s important that this system comply with a range of regulations when it comes to privacy and jurisdiction.

On another note, the team wanted to create stores that could be censorship-resistant — as they have seen in the past, reliance on centralised entities to host data has clearly failed a number of industries. By harnessing decentralisation, this bottleneck can be circumvented altogether, and flattens the power structures that have arisen.

In order to be valuable to the many applications of the ixo protocol, data stores need a handful of features: immutability, non-repudiability and a system that only grants access to specific individuals, based on credentials. On top of this, in order to compete, they need to be fast, cheap, secure and easy to use. These features are highly-sought after, not only for the purpose of the ixo protocol , but for many Web 3.0 applications.


The data stores are deployed in the ixo network for every project. Its identifier is comprised of a record (controlled by the project owner), which acts as a pointer to the location where the project data maintains a database of all pertinent information to said project. The owner has the standard CRAB (Create, Retrieve, Append, Burn) functions and can dynamically assign these to other participants as needed. Given the current issues with scalability in blockchain systems, the data is stored off-chain, although proofs of data submission (and other metadata pertinent to the tracking of project performance) are stored in the ixo blockchain, or the Global Impact Ledger.

Signed messages, containing project data, are relayed to the blockchain for processing, whereupon the consensus mechanism allows for their validation before they are appended to the hash-chain record in the project’s private data store — in essence, each project has its own validated hash-chain. The ixo whitepaper should be examined for more insight into how the protocol enables verification of the claims, tokenises the proofs of impact, and allows for these to be traded.


When a user sets up a data store under Elysian, a dynamically customisable list of credentials is established, outlining which actions can be performed, and by whom. These are not set in stone, and can be updated or revoked at the discretion of the creator. Access is compliant with the current consent requirements for data protection.

Data stored within an Elysian data store is immutable as this is an append-only data store (data cannot be deleted or updated). Any operations occurring first require the authentication of the user (in the form of digital identifiers) that requests access to modify the database. The data itself is entirely verifiable, given its conforming to the W3C standards for verifiable claims. Only messages compliant to the predefined JSON template designed for the data store are accepted. Of course, the cryptographic signatures must also match.

The public key of the digital identifier signing a request is retrieved from the identifier blockchain record and subsequently validated. After this has been verified, the record is appended with a timestamp, and the hash of the previous transaction is included.

The flow of information on the ixo protocol

Web 3.0 for the Masses

The ixo development team believes Elysian is a core building block for a wealth of data-driven applications in the Web 3.0 revolution, whose aim is to decentralise incumbent architectures. The team is looking forward to moving this project into full production as an incredibly versatile tool in the ixo network and beyond. The team is encouraging everyone to get involved, and to flesh out the features and use cases of Elysian, to truly make it an open-source utility for all.

Join Our Community

Learn more about ixo and how to get involved at ixo.foundation

Like what you read? Give Brennon Hampton a round of applause.

From a quick cheer to a standing ovation, clap to show how much you enjoyed this story.