Citrus contract 0x6d44…465c on BNB Chain

0x6d445f44fa904c21981df8a9f2e80a22dd28465c

As of 21 Nov 2026, Trustblock’s record holds 0x6d445f44fa904c21981df8a9f2e80a22dd28465c on BNB Chain as a contract of Citrus. 1 audit report on Trustblock lists this address: CertiK, 15 Feb 2023. 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 BNB Chain.

AuditSecurity firmDateCommit named in the reportReport
Citrus - AuditCertiKNot recorded (see the report)Open

Open and acknowledged findings in these reports3

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

HighCentralized Control of Contract UpgradeCitrus - Audit · CertiKAcknowledged

TestCitrusV2 are upgradeable contracts, the owner can upgrade the contract without the community's commitment. If an attacker compromises the account, he can change the implementation of the contract and drain tokens from the contract.

The audit on Trustblock · Open the report
HighInitial Token DistributionCitrus - Audit · CertiKAcknowledged

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

The audit on Trustblock · Open the report
LowTransaction revert when `msg.sender == _from`Citrus - Audit · CertiKAcknowledged

In function `transferFrom`, when `msg.sender == _from`, the function would revert.

The audit on Trustblock · Open the report

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