SKYPlay contract 0x4c66…3d15 on Polygon (POS)

0x4c665bbafd28ec9e5d792345f470ebfca21e3d15

As of 21 Nov 2026, Trustblock’s record holds 0x4c665bbafd28ec9e5d792345f470ebfca21e3d15 on Polygon (POS) as a contract of SKYPlay. 1 audit report on Trustblock lists this address: CertiK, 9 Nov 2022. 3 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
Skyplay - auditCertiKNot recorded (see the report)Open

Open and acknowledged findings in these reports3

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

LowFunction Should Be Declared ExternalSkyplay - audit · CertiKOpen

The functions which are never called internally within the contract should have external visibility for gas optimization. --- ```solidity=17 function deposit() payable public { ```

The audit on Trustblock · Open the report
LowLocked EtherSkyplay - audit · CertiKOpen

The contract has one or more payable functions, but does not have a function to withdraw the fund. ```solidity=17 function deposit() payable public { ```

The audit on Trustblock · Open the report
LowUnknown purpose of the "Deposit" functionSkyplay - audit · CertiKOpen

The "SKPERC20" contract has the "deposit" function that allows the caller to send the native Chain token into the contract. However, the contract doesn't have any logic related to the deposit token and doesn't have a function to withdraw deposited native chain tokens from the contract. It's unsure why the contract needs to have such a function.

The audit on Trustblock · Open the report

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