TTX Games contract 0x5783…f2c1 on Ethereum

0x578300cc8db63f871643307d553e485982e4f2c1

As of 21 Nov 2026, Trustblock’s record holds 0x578300cc8db63f871643307d553e485982e4f2c1 on Ethereum as a contract of TTX Games. 1 audit report on Trustblock lists this address: CertiK, 30 Aug 2022. 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
KENKA METAVERSE - 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.

HighInitial Token DistributionKENKA METAVERSE - Audit · CertiKAcknowledged

All of the tokens are sent to the contract deployer when deploying the contract. This could be a centralization risk as the deployer can distribute tokens without obtaining the consensus of the community.

The audit on Trustblock · Open the report
LowThird Party DependencyKENKA METAVERSE - Audit · CertiKAcknowledged

The contract is serving as the underlying entity to interact with one or more third party protocols. The scope of the audit treats third party entities as black boxes and assume their functional correctness. However, in the real world, third parties can be compromised and this may lead to lost or stolen assets. In addition, upgrades of third parties can possibly create severe impacts, such as increasing fees of third parties, migrating to new LP pools, etc. ```solidity=577 constructor(address payable receiver, string memory serviceName) payable { ``` - The function `ServicePayer.constructor` interacts with third party contract with `IPayable` interface via `receiver`.

The audit on Trustblock · Open the report

The TTX Games security record · Every TTX Games address · This address on the explorer