Fandom CrtrToken

CertiKCode version: not recorded (see the report)

CertiK reviewed Fandom (Fandom CrtrToken) on 30 Nov 2022: 5 findings, 0 critical; 3 marked fixed, 2 acknowledged.

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

Report hosted on skynet.certik.com.

Trustblock does not review code.

Findings5

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

SeverityOpenAcknowledgedFixed
Critical000
High020
Medium000
Low003
HighCentralization Risks in master.solAcknowledged

In the contract `CrtrToken` the role `DEFAULT_ADMIN_ROLE` has authority over the functions shown below. - `lockToAddress()` Any compromise to the `DEFAULT_ADMIN_ROLE` account may allow the hacker to take advantage of this authority and update the sensitive settings and execute sensitive functions of the project.

HighInaccurate Lock Token Cliff ConfigurationAcknowledged

`lock` / 1 + `lock` / 2 + ... + `lock` / 15 is greater than value of `lock` In the following functions: - `_seed()` - `_private()` - `_foundation()` - `_tech()` - `_partners()` - `_ecosystem()` - `_marketing()` - `_liquidity()` The cliff of the token distribution has been configured to reduce gradually following the below pattern: ```md `lock` / 1 + `lock` / 2 + ... + `lock` / length ``` However, the sum of the above pattern will always be greater than the value of `lock`, which will cause the actual total number of the `lock` token is more significant than it should be.

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.

Part of Fandom’s security record

Fandom
Audits2 audits by 1 firmLast audit Aug 2023, by CertiK.
Critical findingsNo open critical findingsAcross 2 reports.
Open Fandom’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