Monbase audit reports

BNB Chainmonbase.com

Monbase has 1 public audit report from CertiK; dated 4 Mar 2024; 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 firm12

Statuses are the security firms’ own

12 findings are still open or acknowledged in the firms’ reports: 3 high, 2 medium, 7 low (7 open, 5 acknowledged).

High
3
Medium
2
Low
7
  • High Acknowledged

    Centralization Risks

    MonbaseCoin · CertiK · 4 Mar 2024 · Report ↗

  • High Acknowledged

    Initial Token Distribution

    MonbaseCoin · CertiK · 4 Mar 2024 · Report ↗

  • High Acknowledged

    Logic issue in the function `transferFrom()`

    MonbaseCoin · CertiK · 4 Mar 2024 · Report ↗

  • Medium Acknowledged

    Lack of reasonable boundary

    MonbaseCoin · CertiK · 4 Mar 2024 · Report ↗

  • Medium Acknowledged

    Logic issue in the function `_transfer()`

    MonbaseCoin · CertiK · 4 Mar 2024 · Report ↗

  • Low Open

    Financial models

    MonbaseCoin · CertiK · 4 Mar 2024 · Report ↗

  • Low Open

    Inefficient Memory Parameter

    MonbaseCoin · CertiK · 4 Mar 2024 · Report ↗

  • Low Open

    Missing Keyword `payable` or the `receive` Functi

    MonbaseCoin · CertiK · 4 Mar 2024 · Report ↗

  • Low Open

    Missing Zero Address Validation

    MonbaseCoin · CertiK · 4 Mar 2024 · Report ↗

  • Low Open

    Pull-Over-Push Pattern

    MonbaseCoin · CertiK · 4 Mar 2024 · Report ↗

All 12 open and acknowledged findings

Audits1

Newest first

ReportSecurity firmDateScopeCritical findingsFindingsSource
MonbaseCoinSecurity firm: CertiKDate: Scope: 1 address on BNB ChainNone openFindings: 3 high · 2 medium · 8 low
1 fixed · 5 acknowledged · 7 open
skynet.certik.com ↗

Findings13

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

SeverityOpenAcknowledgedFixed
Critical000
High030
Medium020
Low701
LowFinancial modelsMonbaseCoin · CertiK · 4 Mar 2024Open

The OPVToken is a deflationary token that charges transaction fees for each transaction between non-whitelisted addresses. Some popular deflationary tokens will automatically add the transaction fees to the liquidity pool or just burn out to be locked forever when selling, e.g., Safemoon. While OPVToken transfers the transaction fees directly to `_feeWallet`, which has no benefits for better liquidity and token price but increases the centralized risks.

Open the report
LowInefficient Memory ParameterMonbaseCoin · CertiK · 4 Mar 2024Open

One or more parameters with `memory` data location are never modified in their functions and those functions are never called internally within the contract. Thus, their data location can be changed to `calldata` to avoid the gas consumption copying from calldata to memory. ```solidity=430 function modifyWhiteListSender( ``` `modifyWhiteListSender` has memory location parameters: `newAddr`, `removedAddr`. --- ```solidity=467 function modifyWhiteListReceiver( ``` `modifyWhiteListReceiver` has memory location parameters: `newAddr`, `removedAddr`. --- ```solidity=504 function modifyBlackList( ``` `modifyBlackList` has memory location parameters: `newAddr`, `removedAddr`. --- ```solidity=549 function modifyWhiteListBot( ``` `modifyWhiteListBot` has memory location parameters: `newAddr`, `removedAddr`. --- ```solidity=586 function modifyDexPool( ``` `modifyDexPool` has memory location parameters: `newAddr`, `removedAddr`.

Open the report
LowMissing Keyword `payable` or the `receive` FunctiMonbaseCoin · CertiK · 4 Mar 2024Open

The `flush()` function in the `ERC20` contract uses `{value:}` structure and is designed to receive native tokens, but the `payable` function is missing in the contract and the `receive` function is also missing, making it impossible to receive native tokens. Although the `receive` function is added to the child contract `OPVToken`, the parent contract will face the above issue if it is deployed standalone.

Open the report
LowMissing Zero Address ValidationMonbaseCoin · CertiK · 4 Mar 2024Open

Addresses are not validated before assignment or external calls, potentially allowing the use of zero addresses and leading to unexpected behavior or vulnerabilities. For example, transferring tokens to a zero address can result in a permanent loss of those tokens. ```solidity=544 return to.transfer(value); ``` - `to` is not zero-checked before being used. --- ```solidity=617 _feeWallet = feeWallet; ``` - `feeWallet` is not zero-checked before being used.

Open the report
LowPull-Over-Push PatternMonbaseCoin · CertiK · 4 Mar 2024Open

The change of `owner` by function `transferOwnership()` overrides the previously set `owner` with the new one without guaranteeing the new `owner` has the ability to actuate transactions on-chain.

Open the report
LowUnchecked ERC-20 `transfer()`/`transferFrom()` CaMonbaseCoin · CertiK · 4 Mar 2024Open

The return values of the `transfer()` and `transferFrom()` calls in the smart contract are not checked. Some ERC-20 tokens' transfer functions return no values, while others return a bool value, they should be handled with care. If a function returns `false` instead of reverting upon failure, an unchecked failed transfer could be mistakenly considered successful in the contract. ```solidity=546 IERC20(coinAddress).transfer(to, value); ```

Open the report
LowUsage of `transfer`/`send` for Sending Native TokMonbaseCoin · CertiK · 4 Mar 2024Open

It is not recommended to use Solidity's `transfer()` and `send()` functions for transferring native tokens, since some contracts may not be able to receive the funds. Those functions forward only a fixed amount of gas (2300 specifically) and the receiving contracts may run out of gas before finishing the transfer. Also, EVM instructions' gas costs may increase in the future. Thus, some contracts that can receive now may stop working in the future due to the gas limitation. ```solidity=544 return to.transfer(value); ``` - `ERC20.transferToken` uses `transfer()`.

Open the report

Contracts1

AddressChainSource code
0x85b1c275af0c4e65dc9f5dbfc9ce52bd007722a6Chain: BNB ChainSource code: Verified source

Monbase: questions

Is Monbase audited?

Trustblock holds 1 public audit report for Monbase, dated 4 Mar 2024. The latest is by CertiK (“MonbaseCoin”).

Who audited Monbase?

CertiK wrote the report Trustblock holds for Monbase.

Are there open findings in Monbase’s audits?

12 findings are still open or acknowledged in the firms’ reports: 3 high, 2 medium, 7 low (7 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="monbase"
></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