Baby Boom Token - Addendum

CertiKFiles named in the report

CertiK reviewed BabyBoomToken (BBT) (Baby Boom Token - Addendum) on 25 Mar 2024: 4 findings, 0 critical; none marked fixed.

No open critical findings
Open the reportOpen BabyBoomToken (BBT)’s security record

Report hosted on skynet.certik.com.

Trustblock does not review code.

Findings4

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

SeverityOpenAcknowledgedFixed
Critical000
High200
Medium000
Low200
HighCentralization Related RisksOpen

In the contract `BBT` the role `_owner` has authority over the following functions: - `mint()` allows function owner to mint BBT tokens when total supply is less than the max supply. - `stop()` and `start()` function allows the owner to pause/unpause the contract Any compromise to the `_owner` account may allow the hacker to take advantage of this authority and mint tokens to arbitrary accounts.

HighInitial Token DistributionOpen

All of the `Baby Boom` tokens are sent to the contract deployer on deployment. This is a centralization risk because the contract deployer can distribute tokens without obtaining the consensus of the community. Any compromise to these addresses may allow a hacker to steal and sell tokens on the market, resulting in severe damage to the project.

LowRedundant Use of ModifierOpen

As the function `setMaxSupply()` is set as `internal` and can only be called from the constructor function, the use of the `onlyOwner` modifier is redundant. ```solidity=34 function setMaxSupply(uint256 amount) internal onlyOwner { _maxSupply = amount; } ```

LowVariables That Could Be Declared as ImmutableOpen

The linked variables assigned in the constructor can be declared as `immutable`. Immutable state variables can be assigned during contract creation but will remain constant throughout the lifetime of a deployed contract. A big advantage of immutable variables is that reading them is significantly cheaper than reading from regular state variables since they will not be stored in storage.

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.

Repository and files the report names (1)

  • BbtToken.sol

Part of BabyBoomToken (BBT)’s security record

BabyBoomToken (BBT)
Audits1 audit by 1 firmLast audit Mar 2024, by CertiK.
Critical findingsNo open critical findingsIn 1 report.
Open BabyBoomToken (BBT)’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