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
LowInefficient `memory` & `storage` UsageFixed

The Gas consumption of `memory` is not very significant as compared to the gas consumption of `storage`. In the linked pieces of code, `memory` could be used instead of `storage` since the object is never meant to be modified.

LowOptimizable FunctionsFixed

- `_foundation()` - `_tech()` - `_partners()` - `_ecosystem()` - `_marketing()` - `_liquidity()` has a similar logical implementation but minor change in the value of `lock`, the value of `length`, and the value of `addTime`. Merging these functions can increase gas efficiency and reusability

LowOptimizable FunctionsFixed

`_seed()` and `_private` has similar logical implementation but minor change in value of `token` and value of `initRelease`. Merging these two functions can increase gas efficiency and reusability

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