Shield Protocol Token (SHIELD) security audit, conducted by the Callisto Network Security Department in February 2021.
Shield Protocol Token (SHIELD) Specificities
Shield Protocol Token (SHIELD) Smart Contract Security Audit Report
Are Your Funds Safe?
1. In scope
- Commit hash f5c1a5d77c158f84889b65a4070f7b80c3cf6898 BinanceSmartChain_SHIELD.sol
In total, 3 issues were reported including:
- 1 low severity issue.
No critical security issues were found.
2.1. Known vulnerabilities of BEP-20 / ERC-20 token
- 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
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.
_namehave to be declared as
2.3.Wrong returns type
decimals() has to returns
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
Trust the Blockchain, Audit the Smart Contracts.
Follow Callisto’s Security Department on Twitter to get our latest news and updates!