LandRocker contract 0xfb7f…b16c on Polygon (POS)

0xfb7f8a2c0526d01bfb00192781b7a7761841b16c

As of 21 Nov 2026, Trustblock’s record holds 0xfb7f8a2c0526d01bfb00192781b7a7761841b16c on Polygon (POS) as a contract of LandRocker. 1 audit report on Trustblock lists this address: CertiK, 18 Jun 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
LandRocker - 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 LRT.solLandRocker - Audit · CertiKAcknowledged

In the contract `LRT` the role `_distributor` has authority over the functions shown in the diagram below. Any compromise to the `_distributor` account may allow the hacker to take advantage of this authority and distribute tokens from the contract to any address. ![](https://accelerator-tasks-prod.acc.corp.certik.com/11ef-26da-4c3480d0-897f-fde25e8edac8/diagrams/centralization_LRT-LRT-_distributor.svg)

The audit on Trustblock · Open the report
LowThird-Party Dependency UsageLandRocker - Audit · CertiKAcknowledged

The contract is serving as the underlying entity to interact with one or more out of scope protocols. The scope of the audit treats these entities as black boxes and assumes their functional correctness. However, in the real world, those contracts can be compromised and this may lead to lost or stolen assets. I ```solidity=26 IAccessRestriction public immutable accessRestriction; ``` - The contract `LRT` interacts with out of scope contract with `IAccessRestriction` interface via `accessRestriction`.

The audit on Trustblock · Open the report

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