Q2 Epics

Aventus Protocol Proof of Authority network Ethereum-based protocol v1

Decentralized Tier 2 Research

Aventus Classic

ZK-Snarks Implementation

Business Rules Engine

Developer Engagement

Updated Whitepaper and Light Paper

The major protocol changes in this Quad reflected the use of Ethereum to underwrite the transaction scaling properties of the Tier 2 solution. These changes required substantial analysis and experimentation.

Aventus Protocol Proof of Authority network Ethereum-based protocol v1

The Aventus Protocol Proof of Authority network tier 2 solution will be elaborated on in the upcoming whitepaper.

Decentralized Tier 2 Research

With the release of Protocol v1 it was time to realize the vision of a decentralized version of the Protocol, as shared within the original Whitepaper from 2017.

The objective was to research and build a Tier 2 blockchain on Ethereum where Aventus network participants will be able to run a node, much like Bitcoin and Ethereum participants can. The nodes will form a peer-to-peer network, with any Aventus transaction propagation across the network being processed by one of the nodes into a block, and all nodes coming to consensus on blocks to add to the chain. Tendermint technology was explored and a proof of concept built and the Protocol development team are now positioned to have the use of Tendermint to build out the full decentralized V1 as an option.

Aventus Classic

The team have been further developing Aventus.js, adding and updating documentation, and working on new additions to improve scale based on learnings in solidity. A formal release of Aventus Classic is planned and will be referenced in the upcoming whitepaper.

ZK-Snarks Implementation

Following in-depth research we took a decision to use Zero Knowledge Proofs to allow users of the Aventus network to prove they have a barcode for a ticket on chain (therefore proving it is their ticket) without publicly exposing the barcode itself. We are among the blockchain market leaders in the field of ZK-Snarks making valuable contributions to various blockchain projects.

We are building libraries for iOS and Android mobile platforms which support proof generation and a library for server-side verification of our Snark implementation. Considerable effort has been spent on the optimization of the code, some of which has needed to be created from scratch on account of the newness of the technology, as the computationally intensive algorithms associated with Zero Knowledge Proofs have to be capable of running on resource constricted smartphones if there is to be mass adoption.

Business Rules Engine

Rather than prescribing which rules an event owner can choose from governing their ticket inventory we have been exploring a more general purpose rules engine which can be configured by the ticket seller, enforced by the Aventus network Proof of Authority operator and enforced or challenged if needed on the main Ethereum network.

Developer Engagement

A developer engagement project has been established with the goal of making Aventus tier 2 more approachable and accessible for interested 3rd party developers. Treating 3rd party developers as users of our documentation, this initiative is a commitment to continuing to refine and improve the developer experience associated with using the Aventus protocol and includes:

making it easier to sign up to use Sandbox environments

creating ‘Getting Started’ guides and explainer videos

engaging with developer users to refine and evolve the developer experience and supporting materials over time

Starting this project now and committing to this approach over time is a crucial part of the longer term plan to move the Aventus Protocol to the open source community.

Updated Whitepaper and Light Paper

Through engagement with the ticketing industry we developed a greater understanding of the nature of ticketing and the challenges within the industry. As we continued to share our vision of a Protocol composed of Ethereum smart contracts that would allow for the creation and validation of events, the issuance and sale of tickets in primary and secondary ticket markets, and the distribution of ticket sale revenue and market/event fees between the event organisers, ticket promoters, market matchers, attendees, etc. we realised that in viewing tickets as digital assets and in building a tier 2 based Aventus Proof of Authority network we were in fact building a solution that could easily lend itself not just to ticketing but to digital asset management in general. We therefore started having conversations with other sectors that use digital assets requiring business rules and permission management.

These conversations are sufficiently interesting for us to have made a decision to update the whitepaper. We will maintain the original elements described within the original whitepaper which will now be referred to as Aventus Classic, while illustrating some key findings that hindered its adoption. We will propose tweaks to the Aventus ecosystem to position it to have the best chance at becoming a standard for the ticketing industry, but also and importantly position the Protocol to be applicable more generally to other types of digital assets. In taking this approach we recognize the importance of having any potential other use cases for the Protocol thoroughly reviewed to ensure regulatory compliance of AVT.

Various authorities have become much more aware of tokens and whilst the frameworks they are creating are continually evolving, there is certainly more information available than when we set out on this mission.