ATHREUM
Athreum is building a decentralized cloud that anyone can use, is extremely powerful, has no central authority and provides access to Blockchainâs groundbreaking technologies and liquidity.
Owner privileges
Comments
Ownership Privileges
- The owner can add the market pair addresses.
- The owner can exempt wallets from max transaction amount.
- The owner can exclude wallets from fees.
- The owner can set any arbitrary value in the buy and sell tax amount which can be more than 100%.
- The owner can set any arbitrary value in the distribution setting, which can set any amount in the liquidity, marketing, and buyback sharing in the contract.
- The owner can set the max transaction amount which cannot be less than 4%.
- The owner can enable/disable the wallet limit.
- The owner can exempt the wallets from the wallet limit.
- The owner can set any arbitrary value in the wallet limit which can lock the user to transfer of tokens.
- The owner can set any arbitrary value in the minimum swap amount before swap.
- The owner can set the marketing wallet address.
- The owner can set the buyback wallet address.
- The owner can enable/disable swapping.
- The owner can enable/disable swapping by limit only which means when it is enabled only the minimum swap amount will be swapped.
- The owner can change the router pair address after initial deployment.
Note - This Audit report consists of a security analysis of the Athreum 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 Athreum team. Other contracts associated with the project were not audited by our team. We recommend investors do their own 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
96
State variables
public
26
Total lines
of code
769
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
Liquidity is added to externally owned account.
L735-748
The contract's liquidity is automatically added to the 'owner' address, which is not recommended because, in an extreme scenario, this can be used to drain liquidity from the contract.
Pending
#2 Issue
Owner can lock user funds.
L578-580
The owner can set any arbitrary value in the max wallet limit which can simply lock the transfer function and the user will not be able to transfer any funds to any wallet if the value is set to zero.
low Issues
Pending
#1 Issue
Local variables shadowing (shadowing-local)
L502
L521
Rename the local variables that shadow another component.
Pending
#2 Issue
Missing Events Arithmetic (events-maths)
L541-547
L549-555
L557-563
L565-568
L570-576
L578-580
L582-584
Emit an event for critical parameter changes.
Pending
#3 Issue
Missing Zero Address Validation (missing-zero-check)
L586
L590
Check that the address is not zero.
Pending
#4 Issue
Floating pragma solidity version.
L8
Adding the constant version of solidity is recommended, as this prevents the unintentional deployment of a contract with an outdated compiler that contains unresolved bugs.
Pending
#5 Issue
Remove safemath library.
L36-87
Compiler version above 0.8.0 has the ability to control arithmetic overflow/underflow. It is recommended to remove the unwanted code in order to avoid high gas fees.
Pending
#6 Issue
Missing visibility.
L393
L424
It is recommended to add 'public' or 'private' during the initialization of a state variable or a mapping.
informational Issues
Pending
#1 Issue
Functions that are not used (dead-code)
L127-144
L110-112
L114-116
L118-120
L122-125
L91-100
L102-108
L18-21
L79-81
L83-86
Remove unused functions.
Pending
#2 Issue
Unused state variables (unused-state)
L149
Remove unused state variables.
optimization Issues
Pending
#1 Issue
State variables that could be declared constant (constable-states)
L387
L385
L386
L416
L149
Add the `constant` attributes to state variables that never change.
Pending
#2 Issue
Public function that could be declared external (external-function)
L168-171
L173-177
L482-484
L486-488
L490-492
L494-496
L502-504
L506-509
L511-514
L516-519
L529-531
L537-539
L594-597
L599-601
L603-605
L611-628
L633-636
L638-642
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.