Aventus Protocol deployed to Ethereum MainNet following successful code audit

This update is from Aventus Protocol Foundation – Medium

We’re pleased to announce that the first version of the Aventus Protocol source code, released last month, has successfully completed a full and unbiased auditing process.

Following the audit, the source code will today be deployed in beta onto the Ethereum MainNet; a major milestone in the Aventus roadmap.

The audit was carried out by Solidified, the leading technical auditing service for Ethereum smart contracts; their 150+ community of Solidity experts has previously audited over 40 companies (including Polymath, Melonport, Bankera and Spring Role), securing over 30,000 ETH. Solidified were selected due to their high reputation in the Ethereum community, wealth of experience, and bug bounty programme — an offering which enlists the help of the Ethereum community in order to de-risk code and make smart contracts more secure.

Engaging with independent experts to carry out an in-depth and unbiased 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 revealed zero Critical issues, and minimal Major and Minor issues, all of which have now been addressed.

The auditing company awards a Solidified Stamp to companies whose smart contracts successfully pass all stages of the audit with no Critical or Major issues.

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, Solidified concluded that “the contracts were also checked for overflow/underflow issues, DoS, and re-entrancy vulnerabilities. None were discovered. The code was found to be well tested for many different scenarios.”

As well as carrying out a general code review, Solidified also compared the functionality of the code release with that outlined in v3 of the Aventus whitepaper, highlighting areas in which our approach to the protocol mechanics has evolved over time.

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’re very pleased — though not surprised! — that the audit report identified no critical issues,” said Andy Grant, CTO at Aventus, “We worked very hard on the first release of the protocol, so it’s great to see that hard work paying off.”

“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.”

Now that you are here, we invite you to join our Telegram Group, Discord, Reddit, Twitter, Facebook, Youtube and LinkedIn.


Aventus Protocol deployed to Ethereum MainNet following successful code audit was originally published in Aventus Protocol Foundation on Medium, where people are continuing the conversation by highlighting and responding to this story.

Powered by WPeMatico