Illuminati Financial
0x93628Aa010D803E25D9C21AA4c3A17788a26E73b 0x9362...26E73b

Static analysis Dynamic analysis Symbolic Execution SWC check

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.

Contract address
0x9362...26E73b
Network Binance Smart Chain
License MIT
Compiler v0.7.6 v0.7.6+commit.7338295f
Type N/A
Language Solidity
Request date 2022/07/12
Revision date 2022/07/12
Critical
Passed
High
Passed
Medium
1 Issue
Low
4 Issues
Informational
4 Issues
Optimization
1 Issue

Owner privileges

Crucial 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 is possible to mint new tokens.
Contract owner cannot blacklist addresses. It is not possible to lock user funds by blacklisting addresses.
Contract owner cannot set high fees The fees, if applicable, can be a maximum of 25% or lower. The contract can therefore not be locked. Please take a look in the comment section for more details.
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.
Comments

  • 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.

Functions
public

62

State variables
public

20

Total lines
of code

759

Capabilities
Hover on items

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.

medium Issues

Pending

#1 Issue

Prevent passing own contract address

IlluminatiToken.sol

L750-752

Description

Prevent passing own contract address to rescueToken.

low Issues

Pending

#1 Issue

Missing Events Arithmetic (events-maths)

IlluminatiToken.sol

L455-465

L543-545

L557-560

L562-565

L567-570

L572-574

L588-608

Description

Emit an event for critical parameter changes.

Pending

#2 Issue

Missing Zero Address Validation (missing-zero-check)

IlluminatiToken.sol

L276

L360

L745

Description

Check that the address is not zero.

Pending

#3 Issue

rewardYieldDenominator should not be 0

IlluminatiToken.sol

L559

Description

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

Pending

#4 Issue

FeeDenominator should not become 0

IlluminatiToken.sol

L607

Description

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.

informational Issues

Pending

#1 Issue

Functions that are not used (dead-code)

IlluminatiToken.sol

L741-743

L194-197

L110-113

L104-108

L92-96

L84-90

L98-102

Description

Remove unused functions.

Pending

#2 Issue

Unused state variables (unused-state)

IlluminatiToken.sol

L82

Description

Remove unused state variables.

Pending

#3 Issue

feeExempt for treasury

IlluminatiToken.sol

L576-580

Description

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

Pending

#4 Issue

feeExempt for liquidity

IlluminatiToken.sol

L582-586

Description

Make sure to set liquidity to false before changing.

optimization Issues

Pending

#1 Issue

Public function that could be declared external (external-function)

IlluminatiToken.sol

L215-217

L219-221

L223-225

L242-244

L255-258

L260-262

L284-286

L534-536

L750-752

Description

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

Diagrams

Disclaimer

SolidProof.io 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. SolidProof.io do not cover testing or auditing the integration with external contract or services (such as Unicrypt, Uniswap, PancakeSwap etc’...)

SolidProof.io 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.

SolidProof.io 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.