Open Meta City contract 0xd7d9…4676 on Ethereum

0xd7d9babf56a66daff2ac5dc96f7e886c05124676

As of 21 Nov 2026, Trustblock’s record holds 0xd7d9babf56a66daff2ac5dc96f7e886c05124676 on Ethereum as a contract of Open Meta City. 1 audit report on Trustblock lists this address: CertiK, 5 Dec 2023. 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 Ethereum.

AuditSecurity firmDateCommit named in the reportReport
Open Meta CityCertiKNot recorded (see the report)Open

Open and acknowledged findings in these reports2

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

HighCentralization Risks in OMZ.solOpen Meta City · CertiKOpen

In the contract `OpenMetaCity` the role `_owner` has authority over the functions shown in the diagram below. ![](https://accelerator-tasks-prod.acc.corp.certik.com/11ee-8b11-043a0440-b18f-bfabb12c2880/diagrams/centralization_OMZ-OpenMetaCity-_owner.svg) Any compromise to the `_owner` account may allow the hacker to take advantage of this authority and allow/prevent external user access to sensitive functionalities controlled by the `whenNotPaused` modifier.

The audit on Trustblock · Open the report
HighInitial Token DistributionOpen Meta City · CertiKOpen

All of the `OMZ` tokens are sent to the contract deployer or one or several externally-owned account (EOA) addresses. This is a centralization risk because the deployer or the owner(s) of the EOAs can distribute tokens without obtaining the consensus of the community. Any compromise to these addresses may allow a hacker to steal and sell tokens on the market, resulting in severe damage to the project.

The audit on Trustblock · Open the report

The Open Meta City security record · Every Open Meta City address · This address on the explorer