Maker Token (MKR) security audit, conducted by the Callisto Network Security Department in March 2019.
Maker Token (MKR) Specificities
Audit Top 200 CoinMarketCap tokens.
Symbol : MKR Name : Maker
Circulating supply: 1 000 000
Total supply: 1 000 000
Max supply: No data
Number of lines:
Maker Token (MKR) Smart Contract Security Audit Report
Are Your Funds Safe?
1. In scope
In total, 5 issues were reported including:
5 low severity issues.
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 a
Transferevent should be emitted.
burnfunction also should emit the
2.3. It is necessary to check the input address of
- In the
transferFromfunctions, input destination address is not checked for a null value and the funds can be transferred to a
- Also it is needed to check input address for
In case if the
approve function is called with only “beneficiary” address parameter then max-uint value(!) of token will be approved to recipient.
Also the approved value doesn’t decrease when
trnsferFrom called in case of max-uint approved value. It is some sort of ERC20 discrepancy.
2.5. Owner’s Privileges
The contract owner allow himself to pause functions of contract (
The audited smart contract can be deployed. Only low severity issues were found during the audit.
4. Revealing audit reports
Trust The Blockchain, Audit Your Smart Contracts.
Follow Callisto’s Security Department on Twitter to get our latest news and updates!