Aqua Tank Info

Designed and developed by ATA studios, Aqua Tank is Strategy card game, co-developed on the foundation of NFT-in-metaverse technology. This game features an exclusive new gaming model on the BSC, Play-to-Earn mode. Unlike any other blockchain games in the GameFi network, Aqua Tank is the pioneer in introducing the marine ecosystem to the BSC blockchain. The metaverse based blockchain game deliver a variety of utilities to the players as an all-rounder, seamlessly covering every niche of entertainment and earning. The Play-to-Earn model of the game encompasses all player utilities. Thus creating a competitive gaming environment where the best man wins!

Aqua Tank 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.

86.04
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
0x866E...F499
Network
BNB Smart Chain - Mainnet
License N/A
Compiler N/A
Type N/A
Language Solidity
Onboard date 2022/07/26
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 cannot set high fees

The fees, if applicable, can be a maximum of 25% or lower. The contract can therefore not be locked. Please take a look in the comment section for more details.

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.


The owner can change the value of "virusStatus" to true and subtract an extra 300 from the amount to be transferred for every caller who is included in fee.

The owner can set the fee as 100 percent because there is no protection against it and can transfer the whole transactional amount to their controlled wallet that they can also modify in the contract.

The owner can exclude anyone from the dividend payout.

Funds can be locked if the fee is set to the maximum value of uint. In that case, all the transfer transactions will revert.

Files and details

Functions
public

/

State variables
public

/

Total lines
of code

/

Capabilities
Hover on items

/

Findings and Audit result

medium Issues | 1 findings

Pending

#1 medium Issue
No maximum cap on fee
AquaTank.sol
L668
L673
L678
Description

The owner can set the fee as 100 percent because there is no protection against it and can transfer the whole transactional amount to their controlled wallet which they can also modify inside the smart contract.

low Issues | 6 findings

Pending

#1 low Issue
Local variables shadowing (shadowing-local)
AquaTank.sol
L1080
L1080
L1128
L1135
L1142
L1152
Description

Rename the local variables that shadow another component.

Pending

#2 low Issue
Missing Events Arithmetic (events-maths)
AquaTank.sol
L607-609
L663-666
L668-671
L673-676
L678-682
L707-710
Description

Emit an event for critical parameter changes.

Pending

#3 low Issue
Missing Zero Address Validation (missing-zero-check)
AquaTank.sol
L655
L659
L685,
Description

Check that the address is not zero.

Pending

#4 low Issue
Halting Transactions
AquaTank.sol
L707
Description

The owner can halt all the transactions by setting the maximum transaction amount to zero because there is no prevention against it

Pending

#5 low Issue
Contract doesn’t import npm packages from source (like OpenZeppelin etc.)
AquaTank.sol
L8-477
Description

We recommend importing all packages from npm directly without flattening the contract. Functions could be modified or can be susceptible to vulnerabilities

Pending

#6 low Issue
Floating Pragma
AquaTank.sol
L3
Description

The current pragma Solidity directive is “^0.8.0". Contracts should be deployed with the same compiler version and flags that they have been tested with thoroughly. Locking the pragma helps to ensure that contracts do not accidentally get deployed using other versions.

informational Issues | 5 findings

Pending

#1 informational Issue
Functions that are not used (dead-code)
AquaTank.sol
L118-121
L1162-1168
L1800-1802
L1816-1819
L1874-1877
L1845-1851
L1833-1840
Description

Remove unused functions.

Pending

#2 informational Issue
Function initializing state variables (function-init-state)
AquaTank.sol
L502
Description

Remove any initialization of state variables via non-constant state variables or function calls. If variables must be set upon contract deployment, locate initialization in the constructor instead.

Pending

#3 informational Issue
Unused state variables (unused-state)
AquaTank.sol
L1828
Description

Remove unused state variables.

Pending

#4 informational Issue
State variables that could be declared constant (constable-states)
AquaTank.sol
L512
L488
L495
L515
Description

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

Pending

#5 informational Issue
Unused return values (unused-return)
AquaTank.sol
L779-781
L792-879
L959-974
Description

Ensure that all the return values of the function calls are used.