ImmuneBytes Completes Pluteus Smart Contract Audit |2022|

4 min readOct 17, 2022

ImmuneBytes officially proclaimed the successful completion of the smart contract security audit for the Pluteus smart contract.

Our auditors conducted a thorough audit to ensure optimum risk coverage, leaving no room for hidden flaws.

At ImmuneBytes, a detailed smart contract audit is performed, ensuring:

  • Identification and reduction of risks.
  • Optimized gas usage
  • Use of best practices and principles.
  • Improved quality and code structure.
  • Calculations and token distribution are outlined in the whitepaper.

The contract underwent a thorough code review and structural, static, and dynamic analysis. After the initial audit, a few high severity issues were found, which were refactored and verified in the final audit. The problems, if persisted, could have remarkably influenced the project’s performance.

Audit Report Overview

  • Project Name: Pluteus
  • Languages: Solidity(Smart contract)
  • GitHub commit hash for audit: 6499d42f3de8414829ec076fcb07077983c905a6
  • Platforms and Tools: Remix IDE, Truffle, Truffle Team, Ganache, Solhint, VScode,

Contract Library, Slither, SmartCheck

Audit Summary

The ImmuneBytes team laid the project through rigorous testing, commencing with an analysis of the smart contract architecture to make sure it is well-structured and secure for third-party smart contracts and libraries.

A careful line-by-line analysis of the Smart Contract was done to look for any potential issues, including Signature Replay Attacks, Unchecked External Calls, External Contract Referencing, Race Conditions, Transaction-ordering Dependency, Variable Shadowing, Timestamp Dependency, DDoS Attacks, and others.

To make sure the functions work as intended, we execute unit tests written by the developer during the unit testing process. During automated testing, we examined the Smart Contract using technologies we had created in-house to find vulnerabilities and security problems.

Audit Goals

To confirm that the smart contract is secure, resilient, and working according to its specifications, auditors thoroughly scrutinize for vulnerabilities in the system. The following three categories can be used to group the audit activities:

  1. Security: Spotting security flaws in each smart contract as well as the overall system of contracts.
  2. Sound Architecture: This system’s architecture was evaluated using best practices and accepted software for smart contracts.
  3. Correctness and quality of the code: a careful review of the contract’s source code with the following goals in mind:
  • Correctness
  • Readability
  • Sections of code with high complexity
  • Quantity and quality of test coverage

Security Level References

Each issue in this report was given one of the following severity ratings:

  • High severity issues, bugs that must be corrected in order for code to behave as intended.
  • Medium severity faults could potentially create problems and should finally be resolved.
  • Low severity issues, such as trivial details and warnings, can be ignored but are better fixed later.

For Pluteus quantified severity issues:

Audit Report

Auditor’s Recommendations

While auditing the Pluteus smart contract, it was discovered that the code contains both high and low-severity flaws.

In addition to other suggestions made in the report, our auditors propose that the developers rectify high severity issues on priority to enhance the smart contract’s functionality.

After the code had been refactored, the final audit was carried out; its specifics are as follows:

  • Project Name: Pluteus
  • Languages: Solidity(Smart contract)
  • GitHub commit hash for audit: 6499d42f3de8414829ec076fcb07077983c905a6
  • Testnet Deployment: 0x88aBc4A596eE8dd89F4809a06AC667f322400349
  • Platforms and Tools: Remix IDE, Truffle, Truffle Team, Ganache, Solhint, VScode,

Contract Library, Slither, SmartCheck

About Pluteus


BEP-20 deflationary token on Binance Smart Chain

Initial supply: 1 Trillion tokens

Following is an overview of the project’s launch, burning mechanism, and tokenomics.


Fair Launch on — the team must participate in Fair Launch and does not keep any tokens.

Trading pair configured with Locked Liquidity on PancakeSwap.


Burning 25% of the initial supplies initially

Burns performed manually during the project’s earliest phase to increase awareness and value for holders.

Burning of tokens — an irrevocable, open act. Tokens burned are deducted from the total supply.


As an anti-dump’n pump policy, there is a 9% fee on each transaction that encourages investors to long-term hold.

About ImmuneBytes

ImmuneBytes is a security start-up to provide security services in the blockchain area. The team has a core competency in doing security audits, penetration tests, and smart contract audits. ImmuneBytes’s security auditors have worked on numerous A-league projects and thoroughly understood DeFi technologies like AAVE, Compound, 0x Protocol, Uniswap, and dydx.

The team has been able to safeguard a number of blockchain projects by delivering security services on multiple frameworks. The ImmuneBytes team supports businesses with a thorough system analysis, ensuring security and overseeing the entire project.

Visit ImmuneBytes to learn more about their services.




Build a hack-proof solution with the industry’s leading blockchain security company.