PandAI Token smart contract security audit, conducted by the Callisto Network Security Department in February 2023.


PandAI Token Security Audit Report

Are Your Funds Safe?


PandAI Token smart contract security audit report performed by Callisto Security Audit Department

1. In scope

2. Findings

In total, 1 issue were reported, including:

      • 0 high-severity issues.
      • 0 medium severity issue.
      • 1 low severity issue.

In total, 2 note were reported, including:

      • 1 note.
      • 1 owner privilege.

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

Severity: Low.


Lack of transaction handling mechanism issue. WARNING! This is a very common issue, and it has already caused millions of dollars in 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 Owner Privileges

Severity: Owner Privileges.


Currently, the total supply of the tokens is minted to the owner of the contract, and the distribution of tokens is controlled by the owner.

    constructor() ERC20("PandAI Token", "PANDAI") {
        _mint(msg.sender, 100000000000000 * 10 ** decimals());

Consider transferring the tokens initially to a multi-sig account so that the tokens are protected by multiple members during the distribution and vesting period.

2.3 Follow good coding practices

Severity: Note


  1. Missing docstrings

    The PandAIToken contract in the code base lack documentation. Docstrings improve readability and ease maintenance. They should explicitly explain the purpose or intention of the functions, the scenarios under which they can fail, the roles allowed to call them, the values returned, and the events emitted.

    Consider thoroughly documenting all functions (and their parameters) that are part of the contracts’ public API. Functions implementing sensitive functionality, even if not public, should be documented as well. Consider following the Ethereum Natural Specification Format (NatSpec) when writing docstrings.

  2. Unlocked Pragma

    Contracts should be deployed using the same compiler version/flags with which they have been tested. Locking the floating pragma, i.e. by not using ^ in pragma solidity ^0.8.9, ensures that contracts do not accidentally get deployed using an older compiler version with unfixed bugs.

  3. Missing test suite

    The contract is missing a test suite to validate and verify the behavior of the contract functionalities. Add tests are recommended to ensure that the contract functions and behaves as expected.

  4. PandAI Token has 6 decimals

    Tokens with 18 decimals are the current norm. For instance, USDC has 6 decimals, cTokens from Compound, and WBTC has 8. Your internal calculations may be inaccurate if you handle PandAI tokens without considering these cases.

3. Security practices

4. Conclusion

The audited smart contract can be deployed. Only low-severity issues were found during the audit.

It is recommended to adhere to the security practices described in pt. 4 of this report to ensure the contract’s operability and prevent any issues that are not directly related to the code of this smart contract.

5. 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!