Global Messaging Token Audit
Audit · firm’s term: audit
OpenZeppelin reviewed Mercury Protocol (Global Messaging Token Audit) on 16 Oct 2017: 8 findings, 1 critical; 6 marked fixed, 2 open.
1 critical finding, fixed
Open the reportOpen Mercury Protocol’s security record
Report hosted on blog.openzeppelin.com.
Trustblock does not review code.
Findings8
Statuses are the security firm’s own, from its report.
| Severity | Open | Acknowledged | Fixed |
|---|---|---|---|
| Critical | 0 | 0 | 1 |
| High | 0 | 0 | 0 |
| Medium | 0 | 0 | 1 |
| Low | 2 | 0 | 4 |
No acknowledged finding in this report.
Contracts in scope
No deployed address is recorded for this audit.
The report names a repository or files. Open the report to see its scope.
Repository and files the report names (4)
- contracts/Tokens/StandardToken.sol
- contracts/Safe/GMTSafe.sol
- contracts/Tokens/GMToken.sol
- contracts/Utils/SafeMath.sol
Part of Mercury Protocol’s security record
Mercury ProtocolAudits1 audit by 1 firmLast audit Oct 2017, by OpenZeppelin.
Critical findingsNo open critical findingsIn that report, 1 critical finding was reported. It is marked fixed by the firm that reported it.
Open Mercury Protocol’s security recordSecurity firm
OpenZeppelin67 projects reviewed · 184 reports · latest Aug 2026
See OpenZeppelin’s auditsSomething 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