Aventus Protocol deployed to Ethereum MainNet
Following an independent code audit process, the source code for the Aventus Protocol (released last month) will today be deployed in beta onto the Ethereum MainNet; a major milestone in the Aventus roadmap.
Engaging with independent experts to carry out an unbiased code review means that we can bulletproof the Aventus offering, delivering the business-critical security that is so needed in order to carry out controlled ticketing transactions.
The audit report can be found here.
A Solidity code coverage checker was used as a code coverage tool in order to ensure that source code was thoroughly tested, further de-risking the project and minimising the chances of unforeseen bugs.
In a closing summary, the audit concludes that “the code was found to be well tested for many different scenarios”.
The functionality of the code release was also compared with that outlined in Version 3 of the Aventus whitepaper, highlighting areas in which our approach to the protocol mechanics has evolved over time. These changes are now reflected in Version 4 of the Aventus whitepaper.
A key area of change is in stake-weighted voting within the Aventus community, performed using the AVT token in order to determine or challenge the legitimacy of events and third-party applications registered within the community. In V3 of the Aventus whitepaper, it was stated that (in the case of a deposit-based vote) the losing party’s deposit would be distributed amongst the winning party and all voters. Following discussions both internally and with the community, it was decided that the losing party’s deposit should be distributed amongst the winning party and winning voters. This was to prevent opportunistic behaviour by voters, who might otherwise place 50/50 stakes during votes in order to benefit either way, thereby adding no value to the community and making the legitimacy of events unverifiable. Version 4 of the whitepaper will be updated accordingly, to reflect this improvement.
“We worked very hard on the first release of the protocol, so it’s great to see that hard work paying off,” said Andy Grant, CTO at Aventus, “Deploying to MainNet is a massive step for the Protocol and means we can start to really support the ticketing industry.”
“The positivity of this first audit report is testament to the hard work and diligence of the Aventus engineering team,” said Andrew Ford, CMO of Aventus, “As we progress along the Aventus roadmap, building out tangible solutions to the challenges faced by the ticketing industry, we will continue both to audit and to update the whitepaper in accordance with major milestones and releases. This will ensure that the Aventus protocol is as secure and performant as possible.”
Disclaimer: We have not completed the entire due diligence process with Solidified, such as final verification of fixes or posting contracts on the bug bounty. Only the initial audit and subsequent verification of several issues fixed was performed.
