Meta Plus Token audit reports

Meta Plus Token has 1 public audit report from CertiK; dated 26 Oct 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 firm6

Statuses are the security firms’ own

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

High
1
Low
5
  • High Acknowledged

    Initial Token Distribution

    Metaplustoken - Audit · CertiK · 26 Oct 2023 · Report ↗

  • Low Open

    Missing Zero Address Validation

    Metaplustoken - Audit · CertiK · 26 Oct 2023 · Report ↗

  • Low Open

    Redundant Statements

    Metaplustoken - Audit · CertiK · 26 Oct 2023 · Report ↗

  • Low Open

    State Variable Should Be Declared Constant

    Metaplustoken - Audit · CertiK · 26 Oct 2023 · Report ↗

  • Low Open

    Unchecked ERC-20 `transfer()`/`transferFrom()` Ca

    Metaplustoken - Audit · CertiK · 26 Oct 2023 · Report ↗

  • Low Open

    Usage of `transfer`/`send` for Sending Native Tok

    Metaplustoken - Audit · CertiK · 26 Oct 2023 · Report ↗

Audits1

Newest first

ReportSecurity firmDateScopeCritical findingsFindingsSource
Metaplustoken - AuditSecurity firm: CertiKDate: Scope: 1 address on Polygon (POS)None openFindings: 2 high · 6 low
2 fixed · 1 acknowledged · 5 open
skynet.certik.com ↗

Findings8

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

SeverityOpenAcknowledgedFixed
Critical000
High011
Medium000
Low501
LowMissing Zero Address ValidationMetaplustoken - Audit · CertiK · 26 Oct 2023Open

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.

Open the report
LowRedundant StatementsMetaplustoken - Audit · CertiK · 26 Oct 2023Open

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.

Open the report
LowState Variable Should Be Declared ConstantMetaplustoken - Audit · CertiK · 26 Oct 2023Open

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

Open the report
LowUnchecked ERC-20 `transfer()`/`transferFrom()` CaMetaplustoken - Audit · CertiK · 26 Oct 2023Open

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); ```

Open the report
LowUsage of `transfer`/`send` for Sending Native TokMetaplustoken - Audit · CertiK · 26 Oct 2023Open

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()`.

Open the report

Contracts1

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

Meta Plus Token: questions

Is Meta Plus Token audited?

Trustblock holds 1 public audit report for Meta Plus Token, dated 26 Oct 2023. The latest is by CertiK (“Metaplustoken - Audit”).

Who audited Meta Plus Token?

CertiK wrote the report Trustblock holds for Meta Plus Token.

Are there open findings in Meta Plus Token’s audits?

6 findings are still open or acknowledged in the firms’ reports: 1 high, 5 low (5 open, 1 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="meta-plus-token"
></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