In order to provide our existing token holders and new token holders an added peace of mind, we arranged for a Full Smart Contract Audit of the BODA smart contract to be conducted by an expert auditing team at the TechRate Audit & Development Firm. We have now received the full audit findings and we are delighted to share key points with our community.
The main purpose of the full smart contract audit was to:
- Ensure that the smart contract functions as intended.
- Identify potential security issues with the smart contract.
- Provide reassurance to our token holders that the contract is safe.
Wallet Analysis
In addition to auditing the complexity of the code, TechRate provided an analysis of the wallet holders. Of particular note was the two highest wallet holders at the time of the audit being:
- Burn address (0x000…dead) with 26.18% of the total starting supply.
- Locked liquidity address (0x703…8685) with 14.81% of the total starting supply.
The next highest wallet holds just 1.62% of the total starting supply. This is reflective of BODA’s stated position as a community-run token. There are no whales who can significantly manipulate the price.
The top 100 holders amount to 84% of the total supply with few having more than 1%. In the pie chart illustration, you will note that other than the burn wallet and the locked liquidity wallet, there is a very healthy spread of holders. The community focus is further reinforced by the anti-whale tax whereby 10% of each sale is deducted from the sale with 3% being recirculated to holders and 7% being locked in the liquidity wallet, which is also reducing the overall circulating supply of the token.
Issues Checked
In total there were 21 potential issues reviewed, ranging from compiler errors to Oracle calls to execution of permissions to fallback function security and a number of issues in between. Of these 21 potential issues, BODA received a pass in 20 and a low issue in 1. There were 0 high severity issues and 0 medium severity issues.
The low-severity issue related to when an out of gas exception.
Issue Identified: the function includeInReward() uses the loop to find and remove addresses from the _excluded list. Function will be aborted with OUT_OF_GAS exception if there will be a long excluded addresses list.
The function _getCurrentSupply also uses the loop for evaluating total supply. It also could be aborted with OUT_OF_GAS exception if there will be a long excluded addresses list.
Recommendation: use EnumerableSet instead of array or do not use long arrays.
Our Response: The above issue does not impact the function of the token and does not present any security issues. While in hindsight we would factor in the recommendation, the Dev key has been burnt to give full peace of mind that nothing untoward is possible with the code, so the code is unable to be altered and this recommendation is unable to be implemented. Given this is such a minor issue, this does not present any ongoing concerns.
Conclusion: your funds are SAFU!
We are extremely pleased with this audit outcome and trust that it will go a long way in reinforcing the positive aspects of this token as viewed by the community.
CLICK HERE TO READ THE FULL SMART CONTRACT AUDIT REPORT HERE
What’s Next?
Now we have received the full comprehensive audit report, the community will turn their focus on the future implementation of our unique approach to Yield Farming. The senior developer has commenced coding the yield farm and we are very excited to go into further detail about this in a future article.
If you would like to join our vibrant and loyal community, we invite you to join our Telegram, reach out to us via Twitter, connect with us on our Reddit and join the community of holders by buying on PancakeSwap V2.
