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.

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

75.56
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
0x986b...Fa8f
Network
BNB Smart Chain - Mainnet
License N/A
Compiler N/A
Type N/A
Language Solidity
Onboard date 2023/11/01
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.


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.

Files and details

Functions
public

/

State variables
public

/

Total lines
of code

/

Capabilities
Hover on items

/

Findings and Audit result

medium Issues | 2 findings

Pending

#1 medium Issue
Liquidity is added to externally owned account.
ATHREUM.sol
L735-748
Description

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.
ATHREUM.sol
L578-580
Description

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 | 6 findings

Pending

#1 low Issue
Local variables shadowing (shadowing-local)
ATHREUM.sol
L502
L521
Description

Rename the local variables that shadow another component.

Pending

#2 low Issue
Missing Events Arithmetic (events-maths)
ATHREUM.sol
L541-547
L549-555
L557-563
L565-568
L570-576
L578-580
L582-584
Description

Emit an event for critical parameter changes.

Pending

#3 low Issue
Missing Zero Address Validation (missing-zero-check)
ATHREUM.sol
L586
L590
Description

Check that the address is not zero.

Pending

#4 low Issue
Floating pragma solidity version.
ATHREUM.sol
L8
Description

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.
ATHREUM.sol
L36-87
Description

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.
ATHREUM.sol
L393
L424
Description

It is recommended to add 'public' or 'private' during the initialization of a state variable or a mapping.

optimization Issues | 2 findings

Pending

#1 optimization Issue
State variables that could be declared constant (constable-states)
ATHREUM.sol
L387
L385
L386
L416
L149
Description

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

Pending

#2 optimization Issue
Public function that could be declared external (external-function)
ATHREUM.sol
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
Description

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)
ATHREUM.sol
L127-144
L110-112
L114-116
L118-120
L122-125
L91-100
L102-108
L18-21
L79-81
L83-86
Description

Remove unused functions.

Pending

#2 informational Issue
Unused state variables (unused-state)
ATHREUM.sol
L149
Description

Remove unused state variables.