MaxiMine Token (MXM) security audit, conducted by the Callisto Network Security Department in July 2019.
MaxiMine (MXM) Specificities
Audit Top 200 CoinMarketCap tokens.
Maximine Coin (MXM).
Number of lines:
MaxiMine (MXM) Smart Contract Security Audit Report
Are Your Funds Safe?
1. In scope
In total, 5 issues were reported including:
- 4 low severity issues.
- 1 owner privilege (the ability of an owner to manipulate contract, may be risky for investors).
No critical security issues were found.
2.1. Known vulnerabilities of ERC-20 token
It is possible to double withdrawal attack. More details here.
- Lack of transaction handling mechanism issue. WARNING! This is a very common issue and it already caused millions of dollars losses for lots of token users! More details here.
Add the following code to the
transfer(_to address, ...) function:
require( _to != address(this) );
2.2. ERC20 Compliance — event missing
According to ERC20 standard when coins are minted(or burned) a
Transfer event should be emitted.
- Line 41, 163, 181.
2.3. ERC20 Compliance — transfer returns
According EIP20 Standard the
transfer function should returns boolean value
function transfer(address _to, uint256 _value) public returns (bool success). But here it is not implemented.
- Line 76.
2.4. ERC20 Compliance: zero-value transfers rejecting
EIP20 says that:
Transfers of 0 values MUST be treated as normal transfers and fire the Transfer event.
But in this contract, function
transferhas a condition:
require(balanceOf[_to] + _value > balanceOf[_to]);
- Line 56.
2.5. Owner Privileges
Severity: owner privileges.
The contract owner allowed to ban transfer functions for certain user.
- Line 86, 77, 111, 128.
The audited smart contract can be deployed. Only low severity issues were found during the audit.
4. Revealing audit reports
Trust the Blockchain, Audit the Smart Contracts.
Follow Callisto’s Security Department on Twitter to get our latest news and updates!