Cryptomus contract 0x4d47…6589 on Polygon (POS)

0x4d47b90fb03b5c35960ebcdccfe30b1e48e36589

As of 21 Nov 2026, Trustblock’s record holds 0x4d47b90fb03b5c35960ebcdccfe30b1e48e36589 on Polygon (POS) as a contract of Cryptomus. 1 audit report on Trustblock lists this address: CertiK, 2 Apr 2024. 2 findings in it are recorded as open or acknowledged.

Audit reports that list this address1

Each report’s scope as stored on Trustblock names this address on Polygon (POS).

AuditSecurity firmDateCommit named in the reportReport
Cryptomus - AuditCertiKNot recorded (see the report)Open

Open and acknowledged findings in these reports2

1 High, 1 Low. In the firm’s own words; statuses are the firm’s, from each report.

HighCentralization Risks in CRMS.solCryptomus - Audit · CertiKAcknowledged

In the contract `CRMS` 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 mint an arbitrary amount of tokens to any address and pause and unpause the contract. ![](https://accelerator-tasks-prod.acc.corp.certik.com/11ee-9e8a-643c6860-9778-7f6ffc64b287/diagrams/centralization_CRMS-CRMS-_owner.svg)

The audit on Trustblock · Open the report
LowUnused InterfaceCryptomus - Audit · CertiKAcknowledged

The smart contract contains one or more inteface definitions that are not used, which can lead to unnecessary complexity and reduced maintainability. ```solidity=189 interface IERC721Errors { ``` - `IERC721Errors` is declared but never used. --- ```solidity=247 interface IERC1155Errors { ``` - `IERC1155Errors` is declared but never used.

The audit on Trustblock · Open the report

The Cryptomus security record · Every Cryptomus address · This address on the explorer