How does it work?
Anagolay is a peer-to-peer network that stores records of Rights, Restrictions, and Proofs of any digital content. It empowers the users to store, claim, sell, and rent their work with the correct transfer of Rights and usage of Licenses.Read the White Paper
Statements & Claims
Statements guarantee the rightfulness of a claim: Copyright, Ownership or any other data that can be presented as a semantic triple
Statement is a record stored on the chain that proves the truthfulness of a Claim using the cryptographic signatures of a Holder and an Issuer. On Anagolay every claim is backed up by a bundle of Proofs.
At this time, we support two types of statements: Copyright and Ownership.
More will be added when we see the need for it and a practical use case.
The proof is sufficient evidence or a sufficient argument for the truth of a proposition.
Anagolay associates several identifiers of authenticity (we call them Proofs) and allows to verify the correctness of a claim against such identifiers.
Computing the identifiers is a repeatable process that always returns the same output no matter where or when the computation executes as long as the user provides the same input data.
The execution consists of a number of tasks, called Operations. When connected together, they make up a Workflow.
Workflow & Operations
Operation is a basic building block of a transparent and verifiable proof generation process. Stored Operations must be permanent.
Operation is a well-structured library with standardized input and output signatures, written in Rust and compiled to WASM. All Operations must be versatile, easy to integrate, and can be used in almost any environment.
Connected together, like lego pieces, Operations form a Workflow - a graph that has a single Operation entry-point. Once executed, a Workflow produces the list of strings that act as the input data identifiers - Proofs.
Anagolay requirements for decentralized storage are: IPFS based (content addressability), permanency, high durability
All the source code and compiled code is stored on IPFS nodes aiming for permanent storage. The default storage layer is Anagolay IPFS node, users can opt in to store their data on any IPFS powered systems of their choice.
The challenge is to have Workflows & Operations Artifacts stored on IPFS permanently.
Web Apps Layer
Substrate with our pallets