Benji Bananas: PRIMATE Token

CertiK4 Apr 2022Files named in the report

CertiK reviewed Benji Bananas (Benji Bananas: PRIMATE Token) on 4 Apr 2022: 5 findings, 0 critical; 1 marked fixed, 4 acknowledged.

No open critical findings

Open the report Open Benji Bananas’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	Acknowledged	Fixed
Critical	0	0
High	2	0
Medium	0	1
Low	2	0

HighCentralization Related RisksAcknowledged

In the contract `PrimateCoin`, the role `owner` has authority over the following functions: - function setTokenURI() Any compromise to the `owner` account may allow a hacker to take advantage of this authority.

HighInitial Token DistributionAcknowledged

A part of the `PRIMATE` tokens is sent to the given recipients when deploying the contract. This could be a centralization risk as the deployer can distribute `PRIMATE` tokens without obtaining the consensus of the community.

LowDiscussion about variable `_tokenURI`Acknowledged

The state variable `_tokenURI` is not declared and used in the audit scope. Why would the team modify this variable in this contract?

LowUnlocked Compiler VersionAcknowledged

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 different compiler versions. 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.