CertiK reviewed Monbase (MonbaseCoin) on 4 Mar 2024: 13 findings, 0 critical; 1 marked fixed, 5 acknowledged, 7 open.
Report hosted on skynet.certik.com.
Trustblock does not review code.
Statuses are the security firm’s own, from its report.
| Severity | Open | Acknowledged | Fixed |
|---|---|---|---|
| Critical | 0 | 0 | 0 |
| High | 0 | 3 | 0 |
| Medium | 0 | 2 | 0 |
| Low | 7 | 0 | 1 |
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.
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`.
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.
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.
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.
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); ```
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()`.
| Address | Chain | Source code |
|---|---|---|
| 0x85b1…22a60x85b1c275af0c4e65dc9f5dbfc9ce52bd007722a6 | Chain: BNB Chain | Source code: Verified source |
1,045 projects reviewed · 1,376 reports · latest May 2025
See CertiK’s auditsSomething 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