As of 30 Oct 2026, Mantle Network has 9 audit reports by 4 security firms on Trustblock; the latest is by MixBytes, dated 28 May 2025. Those reports list no open critical findings.
Record last updated . It holds audits and findings, contracts and incidents up to Oct 2026. Trustblock does not review code.
Newest first
| Audit | Security firm | Date | Scope | Critical findings | Report |
|---|---|---|---|---|---|
| Mantle Network fBTC Timelock security audit | Security firm: MixBytes | Date: | Scope: Not recorded (see the report) | No open critical findings | Open · GitHub |
| Mantle Op-geth & Op-stack Diff Audit | Security firm: OpenZeppelin | Date: | Scope: Files named in the report | No open critical findings | Open · blog.openzeppelin.com |
| Mantle V2 Solidity Contracts Audit | Security firm: OpenZeppelin | Date: | Scope: Files named in the report | 1 critical finding, fixed | Open · blog.openzeppelin.com |
| Mantle OP-Geth Audit | Security firm: OpenZeppelin | Date: | Scope: Files named in the report | 3 critical findings, fixed | Open · blog.openzeppelin.com |
| Mantle Node, Batcher, Proposer, and Tooling Increm | Security firm: OpenZeppelin | Date: | Scope: Files named in the report | No open critical findings | Open · blog.openzeppelin.com |
| Mantle Token and Bridge Audit | Security firm: OpenZeppelin | Date: | Scope: Files named in the report | No open critical findings | Open · blog.openzeppelin.com |
| Mantle Network (Bridge Contracts) | Security firm: Quantstamp | Date: | Scope: Repository at commit d627d24 | No open critical findings | Open · certificate.quantstamp.com |
| Mantle security review | Security firm: Sigma Prime | Date: | Scope: Not recorded (see the report) | 1 critical finding, fixed | Open · GitHub |
| Mantle Network (Token Migration) | Security firm: Quantstamp | Date: | Scope: Files named in the report | No open critical findings | Open · certificate.quantstamp.com |
Statuses are the security firm’s own, from each report.
| Severity | Open | Acknowledged | Fixed |
|---|---|---|---|
| Critical | 0 | 0 | 5 |
| High | 0 | 4 | 3 |
| Medium | 0 | 5 | 13 |
| Low | 12 | 26 | 31 |
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 report gives no description here.
Open the reportThe report gives no description here.
Open the reportThe report gives no description here.
Open the reportThe [proposal in BitDAO](https://snapshot.org/#/bitdao.eth/proposal/0x950dac4d5715b8aa8eab29c484b1c9dd0eed161141262b0425874f65be4d9f8e) states: > “The one-way token conversion ratio shall be set at 1 $BIT token to 1 $MNT token”. However, the `MantleTokenMigrator` contract computes the ratio based on `TOKEN_CONVERSION_NUMERATOR` and `TOKEN_CONVERSION_DENOMINATOR`, possibly not guaranteeing the 1:1 ratio.
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 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 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 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 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 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 report gives no description here.
Open the reportThe report gives no description here.
Open the reportThe report gives no description here.
Open the reportIt is important to validate input data even if they come from trusted sources to reduce human error: 1. `L1StandardBridge.initialize()` needs to validate `_l2TokenBridge` and `_l1BitAddress` against `address(0)` as well since there is no setter for them. 2. `L2StandardBridge.constructor()` needs to validate `_l2CrossDomainMessenger` and `_l1TokenBridge` against `address(0)` as well since there is no setter for them.
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 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 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 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 reportIt is important to validate inputs, even if they only come from trusted addresses, to avoid human error. The following is a non-exhaustive list of missing input validations: <br><br> 1. `MantleTokenMigrator.constructor()`: the `TOKEN_CONVERSION_NUMERATOR` has to be less than or equal to `TOKEN_CONVERSION_DENOMINATOR`. Additionally, the decimals of `BIT` and `MNT` tokens should be equal according to the NatSpec comments. 1. `MantleTokenMigrator.setTreasury()` needs a check against `address(0)`. Otherwise, the `defundContract()`, might just burn tokens.
Open the report`MantleTokenMigrator` contract implements `receive()` and `fallback()` functions. Based on the documentation and project use cases, the contract does not need to receive ETH at any point. The implementation of the functions also shows the Mantle team's intention: to make the transaction revert when receiving ETH in this contract.
Open the reportThe reports name a repository or files. Open a report to see its scope.
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="mantle-network"></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