Imperium
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).
Owner privileges
Comments
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.
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)
- 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
93
State variables
public
13
Total lines
of code
963
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.
low Issues
Pending
#1 Issue
Local variables shadowing (shadowing-local)
L582
L743
Rename the local variables that shadow another component.
Pending
#2 Issue
Missing Events Arithmetic (events-maths)
L634-640
L662-664
L707-709
L712-714
Emit an event for critical parameter changes.
Pending
#3 Issue
Missing Zero Address Validation (missing-zero-check)
L645
L913
Check that the address is not zero.
Pending
#4 Issue
Comparing instead of setting
L858
Instead of setting the variable it is comparing. Replace the "==" to "=" if you want to set the "percent_Of_Tokens_To_Process" to 100.
informational Issues
Pending
#1 Issue
Unused state variables (unused-state)
L456
L486
L491
Remove unused state variables.
Pending
#2 Issue
Confusing variable naming
L950
It is recommended to change the "tDev" to "tFee"
Pending
#3 Issue
No exclusion of imperium dev
L647
It is recommended to include the old imperium dev address back in the fees during the update
Pending
#4 Issue
Unnecessary SafeMath library
-
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.
optimization Issues
Pending
#1 Issue
State variables that could be declared constant (constable-states)
L442
L443
L454
L452
L453
L456
L455
L464
Add the `constant` attributes to state variables that never change.
Pending
#2 Issue
Public function that could be declared external (external-function)
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
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.