Digital Bay
0xF77B213f211E0DC8F4834Df18c4f33b17C4cFc62 0xF77B...4cFc62

Static analysis Dynamic analysis Symbolic Execution SWC check

Our platform, powered by Web3, allows direct wallet payments for convenience and ease. Apart from retail items, Digital Bay serves as a one-stop-shop for any item you can find, why use other platforms when you can pay in Digital tokens rather than fiat cash? This innovative approach to shopping and payment ensures users maximize their time and productivity while maintaining privacy. Experience the seamless and efficient world of Digital Bay today

Contract address
0xF77B...4cFc62
Network Ethereum Mainnet
License Unlicense
Compiler v0.8.19 v0.8.19+commit.7dd6d404
Type N/A
Language Solidity
Request date 2023/05/04
Revision date 2023/05/04
Critical
Passed
High
Passed
Medium
Passed
Informational
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

  • There are several authorized addresses in this contract. If the owner renounce own ownership it is possible that there are another authorized addresses that can modify state variables (Check below Authroized Privileges section). DYOR here.
  • Authorized addresses cannot be renounced if there is no owner. It is recommended to add a renounce function that only authorized addresses can call.

Owner Privileges

  • Update fee marketing- and buyback-receivers. Remember that this addresses are EOA (external owned addresses).
  • enable trading only once. It is recommended to look at the "tradingOpen" variable to ensure that the trading is enabled.
  • update fees (total fee includes every fees below)
    • liquidity
    • marketing
    • buyback
    • burn
  • update fee receivers
  • set swap back settings
    • enabled
    • threshold (min 1 * 10^decimals)
  •  

Authorized Privileges

  • update max wallet percentage
  • update max tx percentage
  • clear stuck tokens from contract
  • update fe exempt
  • manage tx limit exempt. 
  • manage wallet limit exempt
  • update multipliers
    • sell (max 15%)
    • buy (max 15%)
    • transfer (mac 10%)

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

48

State variables
public

23

Total lines
of code

577

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

State variable visibility

DigitalBay.sol

L191-197

L218

L219

L205

L237

Description

State variable visibility is missing. Provide a visibility explicitly.

Pending

#2 Issue

Trading enable

DigitalBay.sol

L396

Description

Owner is able to open the trade. That means if the owner doesn't open the trade it the contract and optional all funds are locked. Check the trading status and dyor.

optimization Issues

Pending

#1 Issue

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

DigitalBay.sol

L116-119

L121-123

L536-538

Description

Use the `external` attribute for functions never called from the contract.

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.