Imperium Info

By leveraging the Proof of Stake (PoS) consensus mechanism, IMPERIUM presents a more environmentally-friendly and efficient solution compared to some blockchains that rely on Proof of Work (PoW).

Imperium Logo

TrustNet Score

The TrustNet Score evaluates crypto projects based on audit results, security, KYC verification, and social media presence. This score offers a quick, transparent view of a project's credibility, helping users make informed decisions in the Web3 space.

81.03
PoorExcellent

Real-Time Threat Detection

Real-time threat detection, powered by Cyvers.io, is currently not activated for this project.

This advanced feature provides continuous monitoring and instant alerts to safeguard your assets from potential security threats. Real-time detection enhances your project's security by proactively identifying and mitigating risks. For more information, click here.

TrustNet DataPulse

Loading...
Mobula Logo Data provided by mobula.io. Need data? Get your API.
Loading...

We are presently engaged in detailed discussions with our partners to finalize the arrangements. Information regarding presales will be made available on this platform in the near future. We appreciate your patience and look forward to sharing the upcoming opportunities with you soon!

We are currently in discussions with our partners to finalize the details. Information on token locking and vesting schedules will be provided on this platform soon. We appreciate your patience and look forward to sharing these upcoming opportunities with you shortly.

In the meantime, we’ve already integrated the LP lock overview from UNCX.network. Please visit the CEX/DEX tab for more information.

Security Assessments

Static AnalysisDynamic AnalysisSymbolic ExecutionSWC CheckManual Review
Contract address
0x994E...08D7
Network
BNB Smart Chain - Mainnet
License N/A
Compiler N/A
Type N/A
Language Solidity
Onboard date 2023/08/14
Revision date In progress

Summary and Final Words

No crucial issues found

The contract does not contain issues of high or medium criticality. This means that no known vulnerabilities were found in the source code.

Contract owner cannot mint

It is not possible to mint new tokens.

Contract owner cannot blacklist addresses.

It is not possible to lock user funds by blacklisting addresses.

Contract owner can set high fees

Contract owner is able to set fees above 25%. Very high fees can also prevent token transfer.

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.

Scope of Work

This audit encompasses the evaluation of the files listed below, each verified with a SHA-1 Hash. The team referenced above has provided the necessary files for assessment.

The auditing process consists of the following systematic steps:

  1. Specification Review: Analyze the provided specifications, source code, and instructions to fully understand the smart contract's size, scope, and functionality.
  2. Manual Code Examination: Conduct a thorough line-by-line review of the source code to identify potential vulnerabilities and areas for improvement.
  3. Specification Alignment: Ensure that the code accurately implements the provided specifications and intended functionalities.
  4. Test Coverage Assessment: Evaluate the extent and effectiveness of test cases in covering the codebase, identifying any gaps in testing.
  5. Symbolic Execution: Analyze the smart contract to determine how various inputs affect execution paths, identifying potential edge cases and vulnerabilities.
  6. Best Practices Evaluation: Assess the smart contracts against established industry and academic best practices to enhance efficiency, maintainability, and security.
  7. Actionable Recommendations: Provide detailed, specific, and actionable steps to secure and optimize the smart contracts.

A file with a different Hash has been intentionally or otherwise modified after the security review. A different Hash may indicate a changed condition or potential vulnerability that was not within the scope of this review.

Final Words

The following provides a concise summary of the audit report, accompanied by insightful comments from the auditor. This overview captures the key findings and observations, offering valuable context and clarity.


During the swapAndLiquify execution, the contract balance will be transferred to the imperiumDev.

Only owner privileges

  • The owner can set the fees up to 49%
  • exclude/include from/in fee
  • update ImperiumDev address
  • enable swap and liquify
  • set the number of transactions before liquify trigger
  • enable/disable fees on transfer
  • update max tx amount
    • setting it to 0 will lock the user's funds because the address cannot transfer anymore
  • update max wallet amount
    • setting it to 0 will lock the user's funds because the address cannot transfer anymore
  • process the swap and liquify manually
  • remove random tokens
  • set new router and pair
  • set new pair

Note - This Audit report consists of a security analysis of the Imperium smart contract. This analysis did not include functional testing (or unit testing) of the contract’s logic. Moreover, we only audited one token contract for the Imperium team, other contracts associated with the project were not audited by our team. We recommend investors do their research before investing. 

Files and details

Functions
public

/

State variables
public

/

Total lines
of code

/

Capabilities
Hover on items

/

Findings and Audit result

low Issues | 4 findings

Pending

#1 low Issue
Local variables shadowing (shadowing-local)
Imperium.sol
L582
L743
Description

Rename the local variables that shadow another component.

Pending

#2 low Issue
Missing Events Arithmetic (events-maths)
Imperium.sol
L634-640
L662-664
L707-709
L712-714
Description

Emit an event for critical parameter changes.

Pending

#3 low Issue
Missing Zero Address Validation (missing-zero-check)
Imperium.sol
L645
L913
Description

Check that the address is not zero.

Pending

#4 low Issue
Comparing instead of setting
Imperium.sol
L858
Description

Instead of setting the variable it is comparing. Replace the "==" to "=" if you want to set the "percent_Of_Tokens_To_Process" to 100.

optimization Issues | 2 findings

Pending

#1 optimization Issue
State variables that could be declared constant (constable-states)
Imperium.sol
L442
L443
L454
L452
L453
L456
L455
L464
Description

Add the `constant` attributes to state variables that never change.

Pending

#2 optimization Issue
Public function that could be declared external (external-function)
Imperium.sol
L222-225
L228-232
L557-559
L561-563
L565-567
L569-571
L577-580
L582-584
L586-589
L591-595
L597-600
L602-605
L619-621
L624-626
L645-648
L656-659
L662-664
L855-862
L900-904
L907-910
L913-915
Description

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

informational Issues | 4 findings

Pending

#1 informational Issue
Unused state variables (unused-state)
Imperium.sol
L456
L486
L491
Description

Remove unused state variables.

Pending

#2 informational Issue
Confusing variable naming
Imperium.sol
L950
Description

It is recommended to change the "tDev" to "tFee"

Pending

#3 informational Issue
No exclusion of imperium dev
Imperium.sol
L647
Description

It is recommended to include the old imperium dev address back in the fees during the update

Pending

#4 informational Issue
Unnecessary SafeMath library
Imperium.sol
-
Description

SafeMath is unnecessary above pragma version 0.8.x. Overflow/underflow issues will be handled by default above these versions. If you remove the SafeMath library, replace its operations with raw mathematical operations.