Overview
Aventus Classic exists as the protocol was outlined in the original Aventus Protocol Foundation whitepaper. Aventus Classic was built with the intention of solving the same core industry problems but the viability of this working at scale was questioned, which led to a fork and the design and development of a Tier 2 Protocol solution that supports the latest version of the whitepaper.
Principally - the Classic protocol was too closely tied to the Ethereum network and hence inherits some of its current flaws; including the ability to scale large transaction volumes in short time periods. Despite this, the Classic protocol is still a viable solution for a grassroots event owner working with low ticket volumes offering the same functionality of an open blockchain ticketing standard.
Usage
Aventus Classic allows a user to issue publicly-verifiable blockchain tickets on Ethereum. Anyone is free to utilize the Protocol and build any application on top of it to facilitate ticket management.
Typical Event Lifecycle
To give an idea of how the Protocol could be used to run an event, see the lifecycle journey below:
- eventOwner creates an event on the Protocol
- ticketOwner creates a private & public key-pair
- eventOwner sells tickets referencing ticketOwner's key-pair
- As the eventTime approaches the eventOwner compiles a list of ticketOwner public keys associated with the event from the public blockchain
- ticketOwners arrive at the event and prove ownership of their public key to the eventOwner to gain access
This flow would involve a wallet-like application for the ticketOwner to prove their key-pair and an eventOwner access control application to hold a doorlist of valid public keys and present an ownership challenge to the ticketOwners