What have we done in 2022? In two words, A LOT!

Overall highlights​

• we wrote and published Anagolay’s White Paper
• created six custom pallets to support Anagolay’s vision
• ran standalone testnet for 1 million blocks and 15 runtime updates without downtime
• migrated runtime source code from standalone node to parachain node
• rebranded 3 websites, including brand-new docs
• published 7 blog posts, and 7 demo videos
• built 4 web apps (svelte), including the chrome extension, aka Anagolay Wallet
• built and released first ever image processing service built on top of IPFS
• to support all the above, we built ~10 important libraries

The year 2022 was a year of refining the idea and finding a strong and immediately useful application of Anagolay technology. At the beginning of the year, we started with an ambitious goal of bringing a robust and scalable framework for rights management to the world.

With Anagolay, any verified online identity, like a web domain, Twitter handler, YouTube or GitHub account, or any Mastodon federated identity, can be used to send and receive funds: as community contributions to support a verified creator or a particular project.

Here's how it works.

We are proud to say that we have completed and delivered Milestone 1 of the recent Anagolay proposal under the Web3 Foundation Grant Program. - a yet another building block in the infrastructure for the future creative economy.

Within the scope of this proposal, we are creating a transparent and trusted process for verifying public internet identities that will enable content creators and open-source developers to monetize the support from their communities without relying on a centralized solution.

One of Anagolay strong points is the capability to generate code by combining Operations into a Workflow, given a manifest that is plain JSON.

This task is performed by the publish service through a template that, once fed with the Workflow manifest and all the required Operation information along with their Versions, produces some Rust code that is suitable to be called from WASM or natively and is preferably no-std (all Operations involved permitting this). This is important because it makes the Workflow very versatile, in fact:

• Rust is a widespread system language and if the Workflow is performant and supports no-std it can possibly be executed also on a Rust-based blockchain, like substrate.
• WASM is a standard assembly format that can run in the browser, under nodejs, and potentially be integrated with other environments as well.

In the following paragraphs, I will go through the different phases of implementation of the Workflow generation, outlining the difficulties I faced and the search for performance improvements. I believe my experience could be useful for many (or at least interesting for some).

Anagolay team has finalized the last milestone of Project Idiyanale Phase1 under the Web3 Foundation Grant Program.

The PR for the deliverable - https://github.com/w3f/Grant-Milestone-Delivery/pull/453

Accepted Grant Proposal - https://github.com/w3f/Grants-Program/pull/719

Anagolay is a next-generation framework for ownerships, copyrights, and digital licenses. We use Substrate to create transparent processes for the creation & validation of proofs and statements of rights.

Overview

In the Milestone 1 article we explained the core idea of Anagolay Network and its approach to the rights management, as well as defined the basics of Workflows and Operations. If you need a recap about Anagolay basics, we recommend going back to the Milestone 1 blogpost.

Milestone 2 brings plenty of new stuff: WebSocket microservice, brand new UI for workflow building, two operations, a new publisher job and rust code generation for workflows, deterministic build of WASM artifacts and two demo applications.

Overview

Anagolay is a peer-to-peer network that stores records of Rights (Copyright, Licenses, and Ownership), Restrictions, and Proofs of any digital content. It empowers users to store, claim, sell, and rent their work with the correct transfer of Rights and usage of Licenses. Actual digital data is never stored on the chain, only its cryptographic or perceptual proof. As such, the Proof acts as an identifier, verifiable by users who have access to the same data without disclosing it in the process.