DollarMoon audit reports

DollarMoon has 1 public audit report from CertiK; dated 30 May 2023; no critical findings reported. It also holds 1 deployed contract on 1 chain.

Critical findings
No open critical findings
In 1 report.
Open the latest report
Your label, live
Get the label for your site

Last updated . It holds audits and findings, contracts and incidents up to Nov 2026. Trustblock does not review code.

Open findings across every firm15

Statuses are the security firms’ own

15 findings are still open or acknowledged in the firms’ reports: 4 high, 1 medium, 10 low (10 open, 5 acknowledged).

High
4
Medium
1
Low
10
  • High Acknowledged

    Centralization Risks in DollarMoon.sol

    Dollarmoon - Audit 1 · CertiK · 30 May 2023 · Report ↗

  • High Acknowledged

    Initial Token Distribution

    Dollarmoon - Audit 1 · CertiK · 30 May 2023 · Report ↗

  • High Acknowledged

    Lost Reward Of Dividend Tracker

    Dollarmoon - Audit 1 · CertiK · 30 May 2023 · Report ↗

  • High Acknowledged

    No Lower limit for `maxSellTransactionAmount`

    Dollarmoon - Audit 1 · CertiK · 30 May 2023 · Report ↗

  • Medium Acknowledged

    Potential Out-of-Gas Exception

    Dollarmoon - Audit 1 · CertiK · 30 May 2023 · Report ↗

  • Low Open

    `uniswapV2Router` Not Excluded After Update

    Dollarmoon - Audit 1 · CertiK · 30 May 2023 · Report ↗

  • Low Open

    Exclude Dead Address from Dividends

    Dollarmoon - Audit 1 · CertiK · 30 May 2023 · Report ↗

  • Low Open

    Missing Emit Events

    Dollarmoon - Audit 1 · CertiK · 30 May 2023 · Report ↗

  • Low Open

    Missing Error Messages

    Dollarmoon - Audit 1 · CertiK · 30 May 2023 · Report ↗

  • Low Open

    Potential Sandwich Attacks

    Dollarmoon - Audit 1 · CertiK · 30 May 2023 · Report ↗

All 15 open and acknowledged findings

Audits1

Newest first

ReportSecurity firmDateScopeCritical findingsFindingsSource
Dollarmoon - Audit 1Security firm: CertiKDate: Scope: 1 address on BNB ChainNone openFindings: 4 high · 1 medium · 10 low
5 acknowledged · 10 open
skynet.certik.com ↗

Findings15

Statuses are the security firm’s own, from each report.

SeverityOpenAcknowledgedFixed
Critical000
High040
Medium010
Low1000
Low`uniswapV2Router` Not Excluded After UpdateDollarmoon - Audit 1 · CertiK · 30 May 2023Open

The `uniswapV2Router` is excluded from receiving dividend at contract deployment, but will start receiving dividend when `uniswapV2Router` is updated.

Open the report
LowExclude Dead Address from DividendsDollarmoon - Audit 1 · CertiK · 30 May 2023Open

The `DEAD` address is not excluded from dividends. In this case, the burned tokens still sharing dividends, and the dividends will be left over to the `DividendTracker` contract.

Open the report
LowMissing Emit EventsDollarmoon - Audit 1 · CertiK · 30 May 2023Open

There should always be events emitted in the sensitive functions that are controlled by centralization roles.

Open the report
LowMissing Error MessagesDollarmoon - Audit 1 · CertiK · 30 May 2023Open

The **require** can be used to check for conditions and throw an exception if the condition is not met. It is better to provide a string message containing details about the error that will be passed back to the caller.

Open the report
LowPotential Sandwich AttacksDollarmoon - Audit 1 · CertiK · 30 May 2023Open

A sandwich attack may happen when an attacker observes a transaction swapping tokens or adding liquidity without setting restrictions on slippage or minimum output amount. The attacker can manipulate the exchange rate by frontrunning (executing before the target) a transaction to purchase one of the assets and make profits by backrunning (executing after the target) a transaction to sell the asset. The following functions are called without setting restrictions on slippage or minimum output amount, so transactions triggering these functions are vulnerable to sandwich attacks, especially when the input amount is large: - `swapTokensForEth()` - `swapAndSendMarketingBNB()`

Open the report
LowState Variable Should Be Declared ConstantDollarmoon - Audit 1 · CertiK · 30 May 2023Open

State variables that never change should be declared as `constant` to save gas. ```solidity=1232 address public deadAddress = 0x000000000000000000000000000000000000dEaD; ``` - `deadAddress` should be declared `constant`.

Open the report
LowThird Party DependencyDollarmoon - Audit 1 · CertiK · 30 May 2023Open

The contract is serving as the underlying entity to interact with one or more third party protocols. The scope of the audit treats third party entities as black boxes and assume their functional correctness. However, in the real world, third parties can be compromised and this may lead to lost or stolen assets. In addition, upgrades of third parties can possibly create severe impacts, such as increasing fees of third parties, migrating to new LP pools, etc. ```solidity=1219 IUniswapV2Router02 public uniswapV2Router; ``` - The contract `DollarMoon` interacts with third party contract with `IUniswapV2Router02` interface via `uniswapV2Router`.

Open the report
LowUnused Return ValueDollarmoon - Audit 1 · CertiK · 30 May 2023Open

The return value of an external call is not stored in a local or state variable. ```solidity=1592 dividendTracker.processAccount(msg.sender, false); ``` --- ```solidity=1813 uniswapV2Router.addLiquidityETH{value: ethAmount}( address(this), tokenAmount, 0, // slippage is unavoidable 0, // slippage is unavoidable liquidityWallet, block.timestamp ); ```

Open the report
LowUnused State VariableDollarmoon - Audit 1 · CertiK · 30 May 2023Open

One or more state variables are never used in the codebase. Variable `MAX_INT256` in `SafeMathInt` is never used in `SafeMathInt`. ```solidity=408 int256 private constant MAX_INT256 = ~(int256(1) << 255); ``` ```solidity=406 library SafeMathInt { ```

Open the report
LowUser-Defined GettersDollarmoon - Audit 1 · CertiK · 30 May 2023Open

The linked functions are equivalent to the compiler-generated getter functions for the respective variables.

Open the report

Contracts1

AddressChainSource code
0x7d18f3fe6e638fad0adacc5db1a47f871a2c2cc4Chain: BNB ChainSource code: Verified source

DollarMoon: questions

Is DollarMoon audited?

Trustblock holds 1 public audit report for DollarMoon, dated 30 May 2023. The latest is by CertiK (“Dollarmoon - Audit 1”).

Who audited DollarMoon?

CertiK wrote the report Trustblock holds for DollarMoon.

Are there open findings in DollarMoon’s audits?

15 findings are still open or acknowledged in the firms’ reports: 4 high, 1 medium, 10 low (10 open, 5 acknowledged). No critical finding is reported. Statuses are the security firms’ own.

Show this on your site

Is this your project? Show this record on your own website. The label states what the record holds, links to this page and updates by itself. It is free and needs no sign-in.

Content

Facts

Automatic: the three strongest facts of this project’s own record (its last audit and two more), highlighted. They update with the record. Picking a fact turns Automatic off.

Fixed as
Language

Style

Layout
Theme
Accent
Corners

Format

Size
Date
Embed as
HTML
<head>
<script src="https://widget.trustblock.run/project-widget.min.js" defer></script>
</head>
<body>
<div
data-tb-project-widget
data-tb-project-slug="dollarmoon"
></div>
</body>

Paste the code where the label should appear. It uses no API credit and updates by itself.

Something wrong on this page? A missing report, a wrong date, a finding that was fixed since. Tell us and we check it against its source.

Tell us