Shield Protocol Token (SHIELD) security audit, conducted by the Callisto Network Security Department in February 2021.


Shield Protocol Token (SHIELD) Specificities




Audit Request

Shield Protocol smart contract security audit report performed by Callisto Security Audit Department.



Shield Protocol Token (SHIELD) Smart Contract Security Audit Report

Are Your Funds Safe?


1. In scope

2. Findings

In total, 3 issues were reported including:

  • 1 low severity issue.
  • 2 notes.

No critical security issues were found.

2.1. Known vulnerabilities of BEP-20 / ERC-20 token

Severity: low.


  1. 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. Unnecessary getter functions

Severity: note.


The variables _decimals, _symbol, _name declared as public so compiler create getter function for them. But for those variables already there are getter function decimals(), symbol(), name(). This issue caused higher gas consumption during deployment, but does not impact on contract works.


Variable _decimals_symbol_name have to be declared as private.

2.3.Wrong returns type

Severity: note.


The function decimals() returns type uint256 but variable _decimals has type uint8.


The function decimals() has to returns uint8.

3. Conclusion

The audited smart contract can be deployed. Only low severity issus was found during the audit. The pointed notes don’t impact on contract works but show the how it has to be by good practice.

4. Revealing audit reports


Smart Contract Audits by Callisto Network.


Why Audit Smart Contracts?

Our Most Popular Audit Reports.

Trust the Blockchain, Audit the Smart Contracts.

Follow Callisto’s Security Department on Twitter to get our latest news and updates!