MetaDex audit reports

Polygon (POS)metadex.io

MetaDex has 1 public audit report from CertiK; dated 7 Feb 2023; no critical findings reported.

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

    Centralization Risks

    Metadex · CertiK · 7 Feb 2023 · Report ↗

  • Low Open

    Contract Can Lock MetaDex Indefenitely

    Metadex · CertiK · 7 Feb 2023 · Report ↗

  • Low Open

    Third Party Dependencies

    Metadex · CertiK · 7 Feb 2023 · Report ↗

  • Low Open

    Too Many Digits

    Metadex · CertiK · 7 Feb 2023 · Report ↗

  • Low Open

    Unnecessary `payable` Address Type

    Metadex · CertiK · 7 Feb 2023 · Report ↗

  • Low Open

    Unnecessary Use of SafeMath

    Metadex · CertiK · 7 Feb 2023 · Report ↗

Audits1

Newest first

ReportSecurity firmDateScopeCritical findingsFindingsSource
MetadexSecurity firm: CertiKDate: Scope: Files listedNone openFindings: 1 high · 22 low
17 fixed · 1 acknowledged · 5 open
skynet.certik.com ↗

Findings23

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

SeverityOpenAcknowledgedFixed
Critical000
High010
Medium000
Low5017
LowContract Can Lock MetaDex IndefenitelyMetadex · CertiK · 7 Feb 2023Open

When calculating the amount that each ticket can claim or the amount that may be auto injected it is rounded down. This can cause the `amountToShareToWinners` to be larger than the amount that can actually be claimed/auto-injected. In this case the difference will be locked in the contract forever as there is no way to recover the tokens.

Open the report
LowThird Party DependenciesMetadex · CertiK · 7 Feb 2023Open

The contract is serving as the underlying entity to interact with third party VRF. The scope of the audit treats 3rd party entities as black boxes and assume their functional correctness. However, in the real world, 3rd parties can be compromised and this may lead to lost or stolen assets. In addition, upgrades of 3rd parties can possibly create severe impacts, such as increasing fees of 3rd parties, migrating to new LP pools, etc.

Open the report
LowToo Many DigitsMetadex · CertiK · 7 Feb 2023Open

Literals with many digits are difficult to read and review. ```solidity=168 require((thisTicketNumber >= 1000000) && (thisTicketNumber <= 1999999), "Outside range"); ``` --- ```solidity=170 _numberTicketsPerLotteryId[_lotteryId][1 + ((thisTicketNumber / 100000) % 10)]++; ``` --- ```solidity=174 _numberTicketsPerLotteryId[_lotteryId][11111 + ((thisTicketNumber / 10) % 100000)]++; ``` --- ```solidity=175 _numberTicketsPerLotteryId[_lotteryId][111111 + ((thisTicketNumber / 1) % 1000000)]++; ``` --- ```solidity=669 uint32 transformedWinningNumber = _bracketCalculator[_bracket] + ((winningTicketNumber / (100000 / (uint32(10)**_bracket)) ) % (uint32(10)**(_bracket + 1))); ``` --- ```solidity=672 uint32 transformedUserNumber = _bracketCalculator[_bracket] + ((userNumber / (100000 / (uint32(10)**_bracket)) ) % (uint32(10)**(_bracket + 1))); ``` --- ```solidity=16 constructor() ERC20("METADEX", "METADEX") ERC20Capped(1000000000 * (10**uint256(18))) { ```

Open the report
LowUnnecessary `payable` Address TypeMetadex · CertiK · 7 Feb 2023Open

In `release()` function, the address `vestingSchedule.beneficiary` is casted to `address payable` type, but no base currency tokens are transferred in or out from that address. So it is an unnecessary casting operation.

Open the report
LowUnnecessary Use of SafeMathMetadex · CertiK · 7 Feb 2023Open

The `SafeMath` library is used unnecessarily in `TokenVesting.sol`. With Solidity compiler versions 0.8.0 or newer, arithmetic operations will automatically revert in case of integer overflow or underflow.

Open the report

Contracts

No deployed address is recorded for these audits.

The reports name a repository or files. Open a report to see its scope.

The repositories and files the reports name

MetaDex: questions

Is MetaDex audited?

Trustblock holds 1 public audit report for MetaDex, dated 7 Feb 2023. The latest is by CertiK (“Metadex”).

Who audited MetaDex?

CertiK wrote the report Trustblock holds for MetaDex.

Are there open findings in MetaDex’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="metadex"
></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