Skip to content

Instantly share code, notes, and snippets.

What would you like to do?

Curate (CUR8) Token Audit Report.

1. Summary

This document is a security audit report performed by RideSolo, where Curate (CUR8) Token has been reviewed.

Symbol       : CUR8
Name         : Curate
Capped supply: 100,000,000
Decimals     : 8 
Standard     : ERC20

2. In scope

3. Findings

2 issues were reported including:

  • 2 low severity issues.

3.1. Burn Mechanism

Severity: low


Transfers to address 0 is used as a basic burn mechanism, however transfer to address zero can also be a result of a mistake by a user or a dapp, devs should take this issue into consideration

Code snippet

    function transfer(address to, uint tokens) public returns (bool success) {
        balances[msg.sender] = safeSub(balances[msg.sender], tokens);
        balances[to] = safeAdd(balances[to], tokens);
        Transfer(msg.sender, to, tokens);
        return true;
    function transferFrom(address from, address to, uint tokens) public returns (bool success) {
        balances[from] = safeSub(balances[from], tokens);
        allowed[from][msg.sender] = safeSub(allowed[from][msg.sender], tokens);
        balances[to] = safeAdd(balances[to], tokens);
        Transfer(from, to, tokens);
        return true;
    function totalSupply() public constant returns (uint) {
        return _totalSupply  - balances[address(0)];

3.2. Known vulnerabilities of ERC-20 token

Severity: low


  1. It is possible to double withdrawal attack. More details here
  2. 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

4. Conclusion

Burn mechanism should be solved before deployement.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.