ATHREUM Info
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.
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.
On-Chain Insights
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.
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.
Scope of Work
Files and details
This audit covered the following files listed below with a SHA-1 Hash. The Team mentioned above provided us with the files that need to be evaluated.
- Review the specifications, sources, and instructions provided to SolidProof to ensure we understand the smart contract's size, scope, and functionality.
- Manual review of code, which is the process of reading source code line-by-line in an attempt to identify potential vulnerabilities.
- Specification comparison checks whether the code does what the specifications, sources, and instructions provided to SolidProof describe.
- Test coverage analysis determines whether the test cases are actually covering the code and how much code is exercised when we run those test cases.
- Symbolic execution is analyzing a program to determine what inputs cause each part of a program to execute.
- Based on the established industry and academic practices, recommendations, and research, best practices review smart contracts to improve efficiency, effectiveness, clarity, maintainability, security, and control.
- Specific, itemized, actionable recommendations to help you take steps to secure your smart contracts.
A file with a different Hash has been intentionally or otherwise modified 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.
Findings and Audit result
low Issues | 6 findings
Pending
#1 low Issue
Local variables shadowing (shadowing-local)
Rename the local variables that shadow another component.
Pending
#2 low Issue
Missing Events Arithmetic (events-maths)
Emit an event for critical parameter changes.
Pending
#3 low Issue
Missing Zero Address Validation (missing-zero-check)
Check that the address is not zero.
Pending
#4 low Issue
Floating pragma solidity version.
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 low Issue
Remove safemath library.
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 low Issue
Missing visibility.
It is recommended to add 'public' or 'private' during the initialization of a state variable or a mapping.
medium Issues | 2 findings
Pending
#1 medium Issue
Liquidity is added to externally owned account.
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 medium Issue
Owner can lock user funds.
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.
optimization Issues | 2 findings
Pending
#1 optimization Issue
State variables that could be declared constant (constable-states)
Add the `constant` attributes to state variables that never change.
Pending
#2 optimization Issue
Public function that could be declared external (external-function)
Use the `external` attribute for functions never called from the contract.
informational Issues | 2 findings
Pending
#1 informational Issue
Functions that are not used (dead-code)
Remove unused functions.
Pending
#2 informational Issue
Unused state variables (unused-state)
Remove unused state variables.
Ownership Privileges
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.