Metaplustoken - Audit

CertiK1 address on Polygon (POS)

CertiK reviewed Meta Plus Token (Metaplustoken - Audit) on 26 Oct 2023: 8 findings, 0 critical; 2 marked fixed, 1 acknowledged, 5 open.

No open critical findings
Open the reportOpen Meta Plus Token’s security record

Report hosted on skynet.certik.com.

Trustblock does not review code.

Findings8

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

SeverityOpenAcknowledgedFixed
Critical000
High011
Medium000
Low501
LowMissing Zero Address ValidationOpen

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=547 payable(feeReceiver_).transfer(msg.value); ``` - `feeReceiver_` is not zero-checked before being used. --- ```solidity=548 _owner = tokenOwner; ``` - `tokenOwner` is not zero-checked before being used.

LowRedundant StatementsOpen

The linked statements do not affect the functionality of the codebase and appear to be either remnants of test code or older functionality. The audit team would like to confirm if this is the case.

LowState Variable Should Be Declared ConstantOpen

State variables that never change should be declared as `constant` to save gas. ```solidity=538 uint256 public Optimization = 103120037778758951045; ``` - `Optimization` should be declared `constant`.

LowUnchecked ERC-20 `transfer()`/`transferFrom()` CaOpen

The return values of the `transfer()` call 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=529 IERC20(tokenAddress).transfer(owner(), tokenAmount); ```

LowUsage of `transfer`/`send` for Sending Native TokOpen

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=547 payable(feeReceiver_).transfer(msg.value); ``` - `METAPLUSTOKEN.constructor` uses `transfer()`.

Contracts in scope1

AddressChainSource code
0x58d70ef99a1d22e1a8f8f0e8f27c1babcf8464f3Chain: Polygon (POS)Source code: Verified source

Part of Meta Plus Token’s security record

Meta Plus Token
Audits1 audit by 1 firmLast audit Oct 2023, by CertiK.
Critical findingsNo open critical findingsIn 1 report.
Open Meta Plus Token’s security record

Security firm

CertiK

1,045 projects reviewed · 1,376 reports · latest May 2025

See CertiK’s audits

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