AnubisPad
0xd9f88B4475aed2cA1107aCe1677a672A95b15daB 0xd9f8...b15daB

Static analysis Dynamic analysis Symbolic Execution SWC check

AnubisPad is a launchpad, DEX, and DAO platform on Arbitrum & zkSync Era. Deployed on the Arbitrum and zkSync Era networks, leveraging the technology and power of both platforms to create a unique AnubisPad. AnubisPad includes key features: Launchpad, DEX, DAO forming a complete ecosystem, helping to incubate new projects on Arbitrum and zkSync Era.

Contract address
0xd9f8...b15daB
Network Arbitrum
License Unlicense
Compiler v0.8.10 v0.8.10+commit.fc410830
Type N/A
Language Solidity
Request date 2023/04/07
Revision date 2023/04/08
Critical
Passed
High
Passed
Medium
Passed

Owner privileges

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.
Contract cannot be locked Owner cannot lock any user funds.
Token cannot be burned There is no burn function within the contract.
Ownership is not renounced Contract can be manipulated by owner functions.
Comments

Ownership Privileges

  • Set Buy and Sell tax but not more than 1%
  • Enable trading but cannot disable it
  • Include/Exclude wallets/addresses from fees
  • Set/Update AMM pair address

The fees of the contract will go to the dead address, and the contract should exclude the router address from fee as well.

Note for Investors: We only Audited one token contract for the Anubis Team. However, If the project has other contracts (for example, a Presale contract etc), and they were not provided to us in the audit scope then we cannot comment on its security and we are not responsible for it in any way.

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)
The auditing process follows a routine series of steps:
  • 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

85

State variables
public

10

Total lines
of code

583

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)

AnubisPad.sol

L460

L479

Description

Rename the local variables that shadow another component.

Pending

#2 Issue

Missing Events Arithmetic (events-maths)

AnubisPad.sol

L495-499

L501-505

Description

Emit an event for critical parameter changes.

Pending

#3 Issue

Floating Pragma

AnubisPad.sol

-

Description

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

informational Issues

Pending

#1 Issue

Functions that are not used (dead-code)

AnubisPad.sol

L121-138

L104-106

L108-110

L112-114

L116-119

L85-94

L96-102

L549-565

L515-517

L13-16

L74-76

L78-81

Description

Remove unused functions.

Pending

#2 Issue

Function initializing state variables (function-init-state)

AnubisPad.sol

L394

L395

L397

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.

optimization Issues

Pending

#1 Issue

State variables that could be declared constant (constable-states)

AnubisPad.sol

L380

L378

L379

L382

Description

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

Pending

#2 Issue

Public function that could be declared external (external-function)

AnubisPad.sol

L161-164

L166-170

L440-442

L444-446

L448-450

L452-454

L460-462

L464-467

L469-472

L474-477

L487-489

L491-493

L511-513

L522-525

L527-531

Description

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.