Avrora has 1 public audit report from CertiK; dated 23 Aug 2023; no critical findings reported. It also holds 2 deployed contracts on 1 chain.
Last updated . It holds audits and findings, contracts and incidents up to Nov 2026. Trustblock does not review code.
Statuses are the security firms’ own
10 findings are still open or acknowledged in the firms’ reports: 4 high, 6 low (6 open, 4 acknowledged).
Centralization Risks in mAVRToken.sol
AVR · CertiK · 23 Aug 2023 · Report ↗
Centralized Control of Contract Upgrade
AVR · CertiK · 23 Aug 2023 · Report ↗
Initial Token Distribution in `AVR` contract
AVR · CertiK · 23 Aug 2023 · Report ↗
Initial Token Distribution in `mAVRToken` contrac
AVR · CertiK · 23 Aug 2023 · Report ↗
Divide Before Multiply
AVR · CertiK · 23 Aug 2023 · Report ↗
Missing Zero Address Validation
AVR · CertiK · 23 Aug 2023 · Report ↗
Redundant `require` check for the zero address
AVR · CertiK · 23 Aug 2023 · Report ↗
Risk of Front-running in mAVRToken Contract Deplo
AVR · CertiK · 23 Aug 2023 · Report ↗
Unnecessary Use of SafeMath
AVR · CertiK · 23 Aug 2023 · Report ↗
Unused State Variable
AVR · CertiK · 23 Aug 2023 · Report ↗
Newest first
| Report | Security firm | Date | Scope | Critical findings | Findings | Source |
|---|---|---|---|---|---|---|
| AVR | Security firm: CertiK | Date: | Scope: 2 addresses on BNB Chain | None open | Findings: 4 high · 6 low 4 acknowledged · 6 open | skynet.certik.com ↗ |
Statuses are the security firm’s own, from each report.
| Severity | Open | Acknowledged | Fixed |
|---|---|---|---|
| Critical | 0 | 0 | 0 |
| High | 0 | 4 | 0 |
| Medium | 0 | 0 | 0 |
| Low | 6 | 0 | 0 |
Performing integer division before multiplication truncates the low bits, losing the precision of calculation. ```solidity=783 _balances[msg.sender] = accountBalance - amount.div(100).mul(91); ``` --- ```solidity=785 _totalSupply -= amount.div(100).mul(91); ``` --- ```solidity=788 transfer(_withdrawalsContractAddress, amount.div(100).mul(9)); ``` ----- Performing integer division before multiplication truncates the low bits, losing the precision of calculation. ```solidity=1515 _balances[msg.sender] = accountBalance - amount.div(100).mul(90); ``` --- ```solidity=1516 _totalSupply -= amount.div(100).mul(90); ``` --- ```solidity=1517 transfer(_PlayToEarn, amount.div(100).mul(10)); ```
Open the reportAddresses are not validated before assignment or external calls, potentially allowing the use of zero addresses and leading to unexpected behavior or vulnerabilities. For example, transferring tokens to a zero address can result in a permanent loss of those tokens. ```solidity=763 _withdrawalsContractAddress = withdrawalsContractAddress_; ``` - `withdrawalsContractAddress_` is not zero-checked before being used. ```solidity=1482 _PlayToEarn = PlayToEarn; ``` - `PlayToEarn` is not zero-checked before being used.
Open the reportThe `require` check in the `burn()` function is redundant as it checks that `msg.sender` is not the zero address, but in reality, the zero address cannot initialize any transactions or calls.
Open the reportThe `initialize` function in the `mAVRToken` contract is responsible for the initial distribution of tokens to different addresses. However, it should be noted that the `initialize` function is not automatically called immediately after the deployment of the contract. This might lead to a potential front-running issue where a malicious actor can see the transaction that calls `initialize` before it is mined and then tries to take advantage of this situation.
Open the reportThe `SafeMath` library is used unnecessarily. With Solidity compiler versions 0.8.0 or newer, arithmetic operations will automatically revert in case of integer overflow or underflow. ```solidity=18 library SafeMath { ``` - An implementation of `SafeMath` library is found. --- ```solidity=747 using SafeMath for uint256; ``` - `SafeMath` library is used for `uint256` type in `AVR` contract. ```solidity=19 library SafeMath { ``` - An implementation of `SafeMath` library is found. --- ```solidity=1460 using SafeMath for uint256; ``` - `SafeMath` library is used for `uint256` type in `mAVRToken` contract.
Open the reportSome state variables are not used in the codebase. This can lead to incomplete functionality or potential vulnerabilities if these variables are expected to be utilized. Variable `_decimals` in `AVR` is never used in `AVR`. ```solidity=748 uint8 private _decimals; ``` ```solidity=745 contract AVR is ERC20 { ```
Open the report| Address | Chain | Source code |
|---|---|---|
| 0xcfe9…a77f0xcfe90d9fcbee5b4fe05a1723c493483b08b1a77f | Chain: BNB Chain | Source code: Verified source |
| 0x4481…05240x4481a01d7f5c8ec65ce963cb15d5bcfa05110524 | Chain: BNB Chain | Source code: Verified source |
Trustblock holds 1 public audit report for Avrora, dated 23 Aug 2023. The latest is by CertiK (“AVR”).
CertiK wrote the report Trustblock holds for Avrora.
10 findings are still open or acknowledged in the firms’ reports: 4 high, 6 low (6 open, 4 acknowledged). No critical finding is reported. Statuses are the security firms’ own.
Is this your project? Show this record on your own website. The label states what the record holds, links to this page and updates by itself. It is free and needs no sign-in.
Automatic: the three strongest facts of this project’s own record (its last audit and two more), highlighted. They update with the record. Picking a fact turns Automatic off.
<head><script src="https://widget.trustblock.run/project-widget.min.js" defer></script></head><body><divdata-tb-project-widgetdata-tb-project-slug="avrora"></div></body>
Paste the code where the label should appear. It uses no API credit and updates by itself.
Something wrong on this page? A missing report, a wrong date, a finding that was fixed since. Tell us and we check it against its source.
Tell us