Project overview - Illuminati Financial

Type ERC20/BEP20
Language Solidity
Request date 2022/07/12
Latest Revision date 2022/07/12

Illuminati Financial is the first project that invented the unlimited NFTs Farming Protocol for infinite passive income. We have created a protocol that’s hassle-free for everyone. The most advanced protocol but simplest one that anyone can understand. With just 3 simple steps: Buy Box - Farm NFTs - Token auto staking. NFTs Farming will yield for token $ILLU, then $ILLU will be auto-staked with 666,666% fixed APY for more $ILLU as rewards and then they will be auto-compounded. The rebase time is every 30 minutes. Everything will be automatic, $ILLU holders just need to hold NFTs + Token then you have an optimal compound interest and infinite passive income.

Price Chart

Audit Summary

Static analysis Dynamic analysis Symbolic Execution SWC check
Network Binance Smart Chain
License & Compiler MIT / v0.7.6+commit.7338295f
Contract address 0x93628Aa010D803E25D9C21AA4c3A17788a26E73b
Critical issues found The contract does contain issues of high or medium criticality. In some circumstances, the Contract may not function as intended and may pose a safety risk.
Contract owner can mint It's possible to mint new tokens.
Contract owner cannot blacklist addresses. It's not possible to lock user funds by blacklisting addresses.
Contract owner cannot set fees above 25% The fees can be a maximum of 25%. The contract can therefore not be locked.
Token transfer can be locked Owner can lock user funds with owner functions.
Token cannot be burned There is no burn function within the contract.
Ownership is not renounced Contract can be manipulated by owner functions.
No Issues found.
No Issues found.
1 Issue found. 0 resolved.
4 Issues found. 0 resolved.
4 Issues found. 0 resolved.
1 Issue found. 0 resolved.

  • Owner can
    • lock user funds by
      • setting address to blacklist
      • setting maxSellTransactionAmount to 0
    • mint new tokens by setting own address as vault

Audit Scope

This audit covered the following files listed below with a SHA-1 Hash. The above token Team provided us with the files that needs to be tested.

We will verify the following claims:
  • Correct implementation of Token standard
  • Deployer cannot mint any new tokens
  • Deployer cannot burn or lock user funds
  • Deployer cannot pause the contract
  • Overall checkup (Smart Contract Security)
The auditing process follows a routine series of steps:
  • Review of the specifications, sources, and instructions provided to SolidProof to make sure we understand the size, scope, and functionality of the smart contract.
  • Manual review of code, which is the process of reading source code line-by-line in an attempt to identify potential vulnerabilities.
  • Comparison to specification, which is the process of checking whether the code does what the specifications, sources, and instructions provided to SolidProof describe.
  • Test coverage analysis, which is the process of determining whether the test cases are actually covering the code and how much code is exercised when we run those test cases.
  • Symbolic execution, which is analysing a program to determine what inputs causes each part of a program to execute.
  • Best practices review, which is a review of the smart contracts to improve efficiency, effectiveness, clarify, maintainability, security, and control based on the established industry and academic practices, recommendations, and research.
  • Specific, itemized, actionable recommendations to help you take steps to secure your smart contracts.

A file with a different Hash has been modified, intentionally or otherwise, after the security review. A different Hash could be (but not necessarily) an indication of a changed condition or potential vulnerability that was not within the scope of this review.

Public functions Public state variables Total lines of code Capabilities
62 20 759

Public functions Public state variables Total lines of code Capabilities
62 20 759

Audit details

Throughout the review process, care was taken to evaluate the repository for security-related issues, code quality, and adherence to speciïŹcation and best practices. To do so, reviewed line-by-line by our team of expert pentesters and smart contract developers, documenting any issues as there were discovered.

Risk represents the probability that a certain source-threat will exploit vulnerability, and the impact of that event on the organization or system. Risk Level is computed based on CVSS version 3.0.

#4 | Prevent passing own contract address
Severity Location Status
Medium IlluminatiToken.sol : 750-752 Pending

Prevent passing own contract address to rescueToken.

#1 | Missing Events Arithmetic (events-maths)
Severity Location Status
Low IlluminatiToken.sol : 455-465, 543-545, 557-560, 562-565, 567-570, 572-574, 588-608 Pending

Emit an event for critical parameter changes.

#2 | Missing Zero Address Validation (missing-zero-check)
Severity Location Status
Low IlluminatiToken.sol : 276, 360, 745 Pending

Check that the address is not zero.

#4 | rewardYieldDenominator should not be 0
Severity Location Status
Low IlluminatiToken.sol : 559 Pending

Prevent variable to become 0, otherwise this will cause a revert while rebasing

#5 | FeeDenominator should not become 0
Severity Location Status
Low IlluminatiToken.sol : 607 Pending

Make sure that the feeDenominator will not become 0. Otherwise it will causes revert in the contract because you are not able to divide by 0.

#2 | Functions that are not used (dead-code)
Severity Location Status
Informational IlluminatiToken.sol : 741-743, 194-197, 110-113, 104-108, 92-96, 84-90, 98-102 Pending

Remove unused functions.

#4 | Unused state variables (unused-state)
Severity Location Status
Informational IlluminatiToken.sol : 82 Pending

Remove unused state variables.

#5 | feeExempt for treasury
Severity Location Status
Informational IlluminatiToken.sol : 576-580 Pending

Make sure the set old treasury to false before changing it.

#6 | feeExempt for liquidity
Severity Location Status
Informational IlluminatiToken.sol : 582-586 Pending

Make sure to set liquidity to false before changing.

#1 | Public function that could be declared external (external-function)
Severity Location Status
Optimization IlluminatiToken.sol : 215-217, 219-221, 223-225, 242-244, 255-258, 260-262, 284-286, 534-536, 750-752 Pending

Use the `external` attribute for functions never called from the contract.


Disclaimer reports are not, nor should be considered, an “endorsement” or “disapproval” of any particular project or team. These reports are not, nor should be considered, an indication of the economics or value of any “product” or “asset” created by any team. do not cover testing or auditing the integration with external contract or services (such as Unicrypt, Uniswap, PancakeSwap etc’...) Audits do not provide any warranty or guarantee regarding the absolute bug- free nature of the technology analyzed, nor do they provide any indication of the technology proprietors. SolidProof Audits should not be used in any way to make decisions around investment or involvement with any particular project. These reports in no way provide investment advice, nor should be leveraged as investment advice of any sort. Reports represent an extensive auditing process intending to help our customers increase the quality of their code while reducing the high level of risk presented by cryptographic tokens and blockchain technology. Blockchain technology and cryptographic assets present a high level of ongoing risk. SolidProof’s position is that each company and individual are responsible for their own due diligence and continuous security. SolidProof in no way claims any guarantee of security or functionality of the technology we agree to analyze.