Fetch Token

CertiK5 Oct 2020Files named in the report

Audit

CertiK reviewed Fetch.ai (Fetch Token) on 5 Oct 2020: 5 findings, 0 critical; all marked fixed.

No open critical findings

Open the report Open Fetch.ai’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.

Severity	Open	Acknowledged	Fixed
Critical	0	0	0
High	0	0	0
Medium	0	0	0
Low	0	0	5

LowFunction visibility can be `external`Fixed

The functions which are never called internally from within the contract should have `external` visibility. The functions on the aforementioned lines have `public` visibility which can be safely changed to `external` .

LowSubstitution of require call with ModifierFixed

The aformentioned `require` call can be converted into a modifier to increase the legibility of the code.

LowSubstitution of require calls with ModifierFixed

The `require` calls on the aforementioned lines can be converted into a modifier to aid readability and maintainability of the code by avoiding code duplication.

LowUnlocked Compiler VersionFixed

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 differing compiler version numbers. 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

Lowvirtual modifier can be removedFixed

The functions on the aforementioned lines have `virtual` modifiers and yet they are the final implementations in the contract's inheritance chain as there are no functions overriding any of them. As these functions are not being overriden, the `virtual` modifiers can be safely removed from each of the functions