Injective Token Smart Contract Audit

Project Background

  • This Solidity smart contract defines an ERC20 token named “Injective Token” with the symbol “INJ”. Let’s break down the main components of the contract:
    • ERC20 Contract: This contract implements the ERC20 interface. It includes functions to transfer tokens (transfer()), approve token spending (approve()), transfer tokens on behalf of others (transferFrom()), and manage allowances. It also includes functions to increase and decrease allowances (increaseAllowance() and decreaseAllowance()). Additionally, it includes functions to mint (_mint()) and burn (_burn()) tokens.
    • InjectiveToken Contract: This contract inherits from the ERC20 contract and initializes the “Injective Token” with the symbol “INJ”. It mints 100 million tokens to the specified custodian address upon deployment.
  • Overall, this contract provides a basic implementation of an ERC20 token with standard functionality, along with additional safety features such as overflow/underflow checks and address validation.
  • The token is without any other custom functionality and without any ownership control, which makes it truly decentralized.


Executive Audit Summary

  • According to the standard audit assessment, the Customer`s solidity smart contracts are “Secured”.  This token contract does not have any ownership control, hence it is 100% decentralized.
  • We used various tools like Slither, Solhint and Remix IDE. At the same time this finding is based on critical analysis of the manual audit.
  • We found 0 critical, 0 high, 0 medium, 0 low and 3 very low-level issues.

Audit Report in PDF


Audit Report Flip book

Please wait while flipbook is loading. For more related info, FAQs and issues please refer to DearFlip WordPress Flipbook Plugin Help documentation.

Leave a Reply

Your email address will not be published. Required fields are marked *

14 − 1 =