BitDCA

CertiKFiles named in the report

CertiK reviewed BitDCA on 19 Feb 2025: 6 findings, 0 critical; 3 marked fixed, 3 acknowledged.

No open critical findings
Open the reportOpen BitDCA’s security record

Report hosted on skynet.certik.com.

Trustblock does not review code.

Findings6

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

SeverityOpenAcknowledgedFixed
Critical000
High020
Medium000
Low013
HighCentralization Related RisksAcknowledged

### BDCAVesting In the contract `BDCAVesting`, the role `_owner` has authority over the functions shown in the diagram below. Any compromise to the `_owner` account may allow the hacker to take advantage of this authority and transfer or renounce ownership, and set vesting schedules and allocations for multiple addresses once. ![](https://accelerator-tasks-prod.acc.corp.certik.com/11ef-b2a0-188ba090-8b19-e50a22e89fa2/diagrams/centralization_BDCAVesting-BDCAVesting-_owner.svg) ### BDCAVestingCEX In the contract `BDCAVestingCEX`, the role `_manager` has authority over the functions shown in the diagram below. Any compromise to the `_manager` account may allow the hacker to take advantage of this authority and start the vesting process allowing the user to claim tokens. ![](https://accelerator-tasks-prod.acc.corp.certik.com/11ef-b2a0-188ba090-8b19-e50a22e89fa2/diagrams/centralization_BDCAVestingCEX-BDCAVestingCEX-_manager.svg) ---- In the contract `BDCAVestingCEX`, the role `_owner` has authority over the functions shown in the diagram below. Any compromise to the `_owner` account may allow the hacker to take advantage of this authority and transfer or renounce ownership, set the manager address as long as the contract is not activated, and set vesting allocations for multiple addresses once as long as the contract is not activated. ![](https://accelerator-tasks-prod.acc.corp.certik.com/11ef-b2a0-188ba090-8b19-e50a22e89fa2/diagrams/centralization_BDCAVestingCEX-BDCAVestingCEX-_owner.svg)

HighInitial Token DistributionAcknowledged

All of the `BDCA Token` tokens are sent to the contract deployer. This is a centralization risk because the 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.

LowInconsistent Solidity VersionsAcknowledged

The codebase contains multiple Solidity versions, which can lead to unexpected behavior, potential vulnerabilities, difficulties in maintaining the code, and inconsistencies in the execution of the smart contract. Using different versions may also result in increased complexity during code auditing, as different security features and bug fixes are present in different versions of the compiler. Versions used: `^0.8.20`, `^0.8.9` ```solidity=3 pragma solidity ^0.8.20; ``` `^0.8.20` is used in contracts/BDCAVestingCEX.sol file. ```solidity=3 pragma solidity ^0.8.20; ``` ```solidity=2 pragma solidity ^0.8.9; ``` `^0.8.9` is used in contracts/BDCA.sol file. ```solidity=2 pragma solidity ^0.8.9; ```

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 (3)

  • contracts/BDCA.sol
  • contracts/BDCAVesting.sol
  • contracts/BDCAVestingCEX.sol

Part of BitDCA’s security record

BitDCA
Audits1 audit by 1 firmLast audit Feb 2025, by CertiK.
Critical findingsNo open critical findingsIn 1 report.
Open BitDCA’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