A Kid Called Beast

CertiK26 Jan 20231 address on Ethereum

Audit

CertiK reviewed a KID called BEAST on 26 Jan 2023: 5 findings, 0 critical; 1 marked fixed, 3 acknowledged, 1 open.

No open critical findings

Open the report Open a KID called BEAST’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	1	0	0
Low	0	3	1

LowFunction `mintReserves()` of the Contract May FaiAcknowledged

The function `mintReserves()` reverts if the difference between Male/Female supply and amount is lower than a threshold. Assuming a new round is started, and the first 40 MALES and 10 FEMALES got minted, the reserved address cannot mint anymore.

LowMissing Error MessagesAcknowledged

The **require** can be used to check for conditions and throw an exception if the condition is not met. It is better to provide a string message containing details about the error that will be passed back to the caller.

LowPotential Missing Root Hash Update for the New RoAcknowledged

The function `setNewRound()` allows the project owner to setup new configurations for a new round. However, the updates of "verification hash" (the root hash) may not be updated in the time since the `setVerificationHash()` is a separate function call. This means that the old verification hash might still be used, potentially causing unexpected consequences. For example, if Alice was included in the previous round but not in the next round, and the owner first calls `setNewRound()` to set up a new round (also increasing the limit of tokens each one can hold) and then updates the verification hash. Alice could potentially mint new AKCB tokens before the verification hash is updated.