H2O contract 0xaf32…cd82 on BNB Chain

0xaf3287cae99c982586c07401c0d911bf7de6cd82

As of 21 Nov 2026, Trustblock’s record holds 0xaf3287cae99c982586c07401c0d911bf7de6cd82 on BNB Chain as a contract of H2O. 1 audit report on Trustblock lists this address: CertiK, 3 May 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 BNB Chain.

AuditSecurity firmDateCommit named in the reportReport
H2O DAOCertiKNot 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 DistributionH2O DAO · CertiKOpen

All of the H2O tokens are sent to the contract deployer when deploying the contract. This could be a centralization risk as the anonymous deployer can distribute tokens without obtaining the consensus of the community. Any compromise to the deployer account may allow the attacker to steal and sell tokens on the market, resulting in severe damage to the project.

The audit on Trustblock · Open the report
LowUnlocked Compiler VersionH2O DAO · CertiKAcknowledged

The contract has unlocked compiler version. An unlocked compiler version in the source code of the contract permits the user to compile it at or above a particular version. This, in turn, leads to differences in the generated bytecode between compilations due to different compiler versions. This can lead to an ambiguity when debugging as compiler specific bugs may occur in the codebase that would be hard to identify over a span of multiple compiler versions rather than a specific one.

The audit on Trustblock · Open the report

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