MetaTrace audit reports

Polygon (POS)metatrace.meGitHub

MetaTrace has 1 public audit report from CertiK; dated 8 Nov 2023; no critical findings reported. It also holds 2 deployed contracts 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 firm8

Statuses are the security firms’ own

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

High
3
Low
5
  • High Open

    Centralization Risks in MetaTraceGovernanceToken.

    MetaTrace · CertiK · 8 Nov 2023 · Report ↗

  • High Open

    Centralized Control of Contract Upgrade

    MetaTrace · CertiK · 8 Nov 2023 · Report ↗

  • High Open

    Initial Token Distribution

    MetaTrace · CertiK · 8 Nov 2023 · Report ↗

  • Low Acknowledged

    Missing sanity check in function `transfer()`

    MetaTrace · CertiK · 8 Nov 2023 · Report ↗

  • Low Acknowledged

    Outdated OpenZeppelin Implementation and Librarie

    MetaTrace · CertiK · 8 Nov 2023 · Report ↗

  • Low Acknowledged

    Pull-Over-Push Pattern In `transferOwnership()` F

    MetaTrace · CertiK · 8 Nov 2023 · Report ↗

  • Low Acknowledged

    Too Many Digits

    MetaTrace · CertiK · 8 Nov 2023 · Report ↗

  • Low Acknowledged

    Upgradeable contract is missing a `__gap[50]` sto

    MetaTrace · CertiK · 8 Nov 2023 · Report ↗

Audits1

Newest first

ReportSecurity firmDateScopeCritical findingsFindingsSource
MetaTraceSecurity firm: CertiKDate: Scope: 2 addresses on Polygon (POS)None openFindings: 3 high · 7 low
2 fixed · 5 acknowledged · 3 open
skynet.certik.com ↗

Findings10

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

SeverityOpenAcknowledgedFixed
Critical000
High300
Medium000
Low052
HighCentralization Risks in MetaTraceGovernanceToken.MetaTrace · CertiK · 8 Nov 2023Open

In the contract `MetaTraceGovernanceToken` the role `_owner` has authority over the functions shown in the diagram below. Any compromise to the `_owner` account may allow the hacker to take advantage of this authority and: - pause/unpause the contract at will. - upgrade the contract code to a potentially malicious one. Note that the function `renounceOwnership()` always reverts so the ownership is prevented from being renounced. ![](https://accelerator-tasks-prod.acc.corp.certik.com/11ee-4743-108274b0-b7f6-472fb79bb303/diagrams/centralization_MetaTraceGovernanceToken-MetaTraceGovernanceToken-_owner.svg) In the contract `OwnableUpgradeable` the role `_owner` has authority over the functions shown in the diagram below. Any compromise to the `_owner` account may allow the hacker to take advantage of this authority and transfer the ownership to one of its EoA. ![](https://accelerator-tasks-prod.acc.corp.certik.com/11ee-4743-108274b0-b7f6-472fb79bb303/diagrams/centralization_MetaTraceGovernanceToken-OwnableUpgradeable-_owner.svg)

Open the report
HighCentralized Control of Contract UpgradeMetaTrace · CertiK · 8 Nov 2023Open

In the contract `MetaTraceGovernanceToken.sol`, the role `admin` has the authority to update the implementation contract behind the contract. Any compromise to the `admin` account may allow a hacker to take advantage of this authority and change the implementation contract which is pointed by proxy and therefore execute potential malicious functionality in the implementation contract.

Open the report
HighInitial Token DistributionMetaTrace · CertiK · 8 Nov 2023Open

All of the `TRC` tokens are sent to the contract deployer or one or several externally-owned account (EOA) addresses. This is a centralization risk because the deployer or the owner(s) of the EOAs can distribute tokens without obtaining the consensus of the community. Any compromise to these addresses may allow a hacker to steal and sell tokens on the market, resulting in severe damage to the project.

Open the report

Contracts2

AddressChainSource code
0x1d5fd72c02cb52cec1395e5639e0c41b2174db07Chain: Polygon (POS)Source code: Verified source
0x40d9fc77027a281d85de1fa660c887e645ae26c3Chain: Polygon (POS)Source code: Verified source

MetaTrace: questions

Is MetaTrace audited?

Trustblock holds 1 public audit report for MetaTrace, dated 8 Nov 2023. The latest is by CertiK (“MetaTrace”).

Who audited MetaTrace?

CertiK wrote the report Trustblock holds for MetaTrace.

Are there open findings in MetaTrace’s audits?

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