Following the recent beta release of the Aventus Protocol to the Ethereum MainNet, we have updated the Aventus whitepaper to reflect the Protocol’s current functionality.

The new whitepaper can be accessed here or via the Aventus website.

Version 4 of the whitepaper details which elements of our ideal, ‘future vision’ for the Aventus ecosystem are fulfilled within the beta release, as well as further expanding on the technology roadmap to realise that vision.

The updated version also brings the whitepaper in-line with last month’s Solidified code audit, which reviewed the code itself and also compared the functionality of the current code release with that outlined in Version 3 of the whitepaper.

Within beta, some elements of the ecosystem remain centralised while we iterate and develop the Protocol. From 1.0 onwards, once use of the Protocol has been established, control over system parameters will be handed to the AVT community, creating a fully decentralised solution.

Future Roadmap

Rather than define a precise and time-bound product roadmap, we are working actively and collaboratively with the ticketing industry to create an agile approach to the Aventus ecosystem based on client feedback and constant iteration. We believe this is the right way to test and challenge assumptions (both the industry’s and our own), educate (and learn from) key industry players, and ultimately drive blockchain adoption at a business and consumer level. We believe this demand-driven, business-led approach means that the Protocol will become something of true value, which can revolutionise the ticketing industry from the bottom up.

However, there are a number of services and solutions that we are currently working on and expect to implement as user-demand dictates.

Our current vision for the future and function of the Aventus solution architecture is developed in detail within Version 4 of the whitepaper.