Chancer - Audit

CertiKFiles named in the report

CertiK reviewed Chancer (Chancer - Audit) on 30 May 2023: 10 findings, 0 critical; 6 marked fixed, 1 acknowledged, 3 open.

No open critical findings
Open the reportOpen Chancer’s security record

Report hosted on skynet.certik.com.

Trustblock does not review code.

Findings10

Statuses are the security firm’s own, from its report.

SeverityOpenAcknowledgedFixed
Critical000
High302
Medium001
Low013
HighCentralization Risks in CHRPresale.solOpen

In the contract `CHRPresale` the role `_owner` has authority over the functions shown in the diagram below. Any compromise to the `_owner` account may allow the hacker to take advantage of this authority. ![](https://accelerator-tasks-prod.acc.corp.certik.com/91464524b30c4cc9a2a4d5b367f5f4d7/diagrams/centralization_CHRPresale-CHRPresale-_owner.svg)

HighInitial Token DistributionOpen

All `_initialSupply` amount of CHR tokens are sent to the contract deployer when deploying the contract. This is a potential centralization risk as the deployer can distribute CHR tokens without the consensus of the community.

HighLack of Checks for Presale Token SupplyOpen

The CHRPresale contract will transfer to users their purchase CHR tokens in function `claim`. However, the `IERC20(saleToken).balanceOf(CHRPresale)` is only checked in function `configureClaim`. The CHRPresale contract might not have enough sale token balance for users to claim, as the tokens can still be sold after the `claimStartTime` is configured.

Contracts in scope

No deployed address is recorded for this audit.

The report names a repository or files. Open the report to see its scope.

Repository and files the report names (2)

  • contracts/CHRPresale.sol
  • contracts/CHRToken.sol

Part of Chancer’s security record

Chancer
Audits1 audit by 1 firmLast audit May 2023, by CertiK.
Critical findingsNo open critical findingsIn 1 report.
Open Chancer’s security record

Security firm

CertiK

1,044 projects reviewed · 1,375 reports · latest May 2025

See CertiK’s audits

Something wrong on this page? A missing report, a wrong date, a finding that was fixed since. Tell us and we check it against its source.

Tell us