Metis has 3 public audit reports from QuillAudits and Hacken; the latest is QuillAudits, 8 Mar 2024; 4 critical findings, 2 open, 2 marked fixed. It also holds 1 deployed contract on 1 chain.
Last updated . It holds audits and findings, contracts and incidents up to Nov 2026. Trustblock does not review code.
Statuses are the security firms’ own
9 findings are still open or acknowledged in the firms’ reports: 2 critical, 2 high, 2 medium, 3 low (all open).
Denial of Service
Metis / ERC20 · Hacken · 6 Oct 2022 · Report ↗
Insufficient Balance
Metis / ERC20 · Hacken · 6 Oct 2022 · Report ↗
Funds Lock
Metis / ERC20 · Hacken · 6 Oct 2022 · Report ↗
Highly Permissive Role Access
Metis / ERC20 · Hacken · 6 Oct 2022 · Report ↗
Native tokens sent into the contract is not irredeemable
Metis - Vesting · QuillAudits · 8 Mar 2024 · Report ↗
Incorrect Function Logic
Metis / ERC20 · Hacken · 6 Oct 2022 · Report ↗
Centralization Issue
Metis - Vesting · QuillAudits · 8 Mar 2024 · Report ↗
Redundant Hardcoded Value
Metis / ERC20 · Hacken · 6 Oct 2022 · Report ↗
Style Guide Violation
Metis / ERC20 · Hacken · 6 Oct 2022 · Report ↗
Newest first
| Report | Security firm | Date | Scope | Critical findings | Findings | Source |
|---|---|---|---|---|---|---|
| Metis - Vesting | Security firm: QuillAudits | Date: | Scope: Files listed | None open | Findings: 1 medium · 2 low 1 fixed · 2 open | quillaudits.com ↗ |
| Metis | Security firm: QuillAudits | Date: | Scope: Files listed | None open | Findings: 1 low 1 fixed | quillaudits.com ↗ |
| Metis / ERC20 | Security firm: Hacken | Date: | Scope: 1 address on Ethereum | 2 open critical findings | Findings: 4 critical · 7 high · 6 medium · 14 low 24 fixed · 7 open | hacken.io ↗ |
Statuses are the security firm’s own, from each report.
| Severity | Open | Acknowledged | Fixed |
|---|---|---|---|
| Critical | 2 | 0 | 2 |
| High | 2 | 0 | 5 |
| Medium | 2 | 0 | 5 |
| Low | 3 | 0 | 14 |
The report gives no description here.
Open the reportThe report gives no description here.
Open the reportThe report gives no description here.
Open the reportThe report gives no description here.
Open the reportThe vault is designed with the receive payable function which makes the contract capable of receiving native tokens. However, it fails to implement a corresponding function to to withdraw native tokens sent into it. This implies that if the contract receives native tokens, they will be stuck in the contract as there is no function to withdraw.
Open the reportThe report gives no description here.
Open the reportThere are some critical functions in the contract with the whenNotPaused modifier which restricts when it can be invoked by anyone or not. Since the contract owner can pause and unpause the contract, activities on the contract could be halted by a malicious contract owner.
Open the reportThe report gives no description here.
Open the reportThe report gives no description here.
Open the report| Address | Chain | Source code |
|---|---|---|
| 0x9e32…ed8e0x9e32b13ce7f2e80a01932b42553652e053d6ed8e | Chain: Ethereum | Source code: Verified source |
Trustblock holds 3 public audit reports for Metis, dated 6 Oct 2022 to 8 Mar 2024. The latest is by QuillAudits (“Metis - Vesting”).
2 security firms wrote the reports Trustblock holds for Metis: QuillAudits and Hacken.
9 findings are still open or acknowledged in the firms’ reports: 2 critical, 2 high, 2 medium, 3 low (all open). Of 4 critical findings: 2 open, 2 marked fixed. Statuses are the security firms’ own.
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.
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.
<head><script src="https://widget.trustblock.run/project-widget.min.js" defer></script></head><body><divdata-tb-project-widgetdata-tb-project-slug="metis"></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