Bitgain audit reports

BNB Chainbitgain.ai

Bitgain has 1 public audit report from CertiK; dated 13 Sep 2023; no critical findings reported. It also holds 1 deployed contract on 1 chain.

Critical findings
No open critical findings
In 1 report.
Open the latest report
Your label, live
Get the label for your site

Last updated . It holds audits and findings, contracts and incidents up to Nov 2026. Trustblock does not review code.

Open findings across every firm9

Statuses are the security firms’ own

9 findings are still open or acknowledged in the firms’ reports: 2 high, 7 low (7 open, 2 acknowledged).

High
2
Low
7
  • High Acknowledged

    Centralization Risks in StandardToken.sol

    Bitgain · CertiK · 13 Sep 2023 · Report ↗

  • High Acknowledged

    Initial Token Distribution

    Bitgain · CertiK · 13 Sep 2023 · Report ↗

  • Low Open

    Check Allowance Before Transfer

    Bitgain · CertiK · 13 Sep 2023 · Report ↗

  • Low Open

    Commented Out Code

    Bitgain · CertiK · 13 Sep 2023 · Report ↗

  • Low Open

    Missing input validation for `amount`

    Bitgain · CertiK · 13 Sep 2023 · Report ↗

  • Low Open

    Missing Zero Address Validation

    Bitgain · CertiK · 13 Sep 2023 · Report ↗

  • Low Open

    Pull-Over-Push Pattern

    Bitgain · CertiK · 13 Sep 2023 · Report ↗

  • Low Open

    Unnecessary Use of SafeMath

    Bitgain · CertiK · 13 Sep 2023 · Report ↗

  • Low Open

    Usage of `transfer` for Sending Native Tokens

    Bitgain · CertiK · 13 Sep 2023 · Report ↗

Audits1

Newest first

ReportSecurity firmDateScopeCritical findingsFindingsSource
BitgainSecurity firm: CertiKDate: Scope: 1 address on BNB ChainNone openFindings: 2 high · 7 low
2 acknowledged · 7 open
skynet.certik.com ↗

Findings9

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

SeverityOpenAcknowledgedFixed
Critical000
High020
Medium000
Low700
LowCheck Allowance Before TransferBitgain · CertiK · 13 Sep 2023Open

In the function `transferFrom()`, the function transfers tokens before checking if the message sender has enough of an allowance. ```solidity=541 _transfer(sender, recipient, amount); _approve(sender, _msgSender(), _allowances[sender][_msgSender()].sub(amount, "TOKEN20: transfer amount exceeds allowance")); ``` It would be better to validate the allowance first to reduce gas costs in case it reverts.

Open the report
LowCommented Out CodeBitgain · CertiK · 13 Sep 2023Open

Commented out code is redundant and can be misleading.

Open the report
LowMissing input validation for `amount`Bitgain · CertiK · 13 Sep 2023Open

The mentioned functions lack the zero check for the parameter `amount`. When `amount == 0`, these functions won't make any changes in the contract.

Open the report
LowMissing Zero Address ValidationBitgain · CertiK · 13 Sep 2023Open

Addresses are not validated before assignment or external calls, potentially allowing the use of zero addresses and leading to unexpected behavior or vulnerabilities. For example, transferring tokens to a zero address can result in a permanent loss of those tokens. ```solidity=477 payable(serviceFeeReceiver_).transfer(serviceFee_); ``` - `serviceFeeReceiver_` is not zero-checked before being used.

Open the report
LowPull-Over-Push PatternBitgain · CertiK · 13 Sep 2023Open

The contract `StandardToken` inherits functionalities from the `Ownable` contract such as the `transferOwnership()` that allows setting the new `owner` without guaranteeing the designated account is able to actuate transactions on-chain.

Open the report
LowUnnecessary Use of SafeMathBitgain · CertiK · 13 Sep 2023Open

The `SafeMath` library is used unnecessarily. With Solidity compiler versions 0.8.0 or newer, arithmetic operations will automatically revert in case of integer overflow or underflow.

Open the report
LowUsage of `transfer` for Sending Native TokensBitgain · CertiK · 13 Sep 2023Open

It is not recommended to use Solidity's `transfer()` and `send()` functions for transferring native tokens, since some contracts may not be able to receive the funds. Those functions forward only a fixed amount of gas (2300 specifically) and the receiving contracts may run out of gas before finishing the transfer. Also, EVM instructions' gas costs may increase in the future. Thus, some contracts that can receive now may stop working in the future due to the gas limitation. ```solidity=477 payable(serviceFeeReceiver_).transfer(serviceFee_); ``` - `StandardToken.constructor` uses `transfer()`.

Open the report

Contracts1

AddressChainSource code
0x957fa93b3e131229305bad9a9a4a280b30fab7d1Chain: BNB ChainSource code: Verified source

Bitgain: questions

Is Bitgain audited?

Trustblock holds 1 public audit report for Bitgain, dated 13 Sep 2023. The latest is by CertiK (“Bitgain”).

Who audited Bitgain?

CertiK wrote the report Trustblock holds for Bitgain.

Are there open findings in Bitgain’s audits?

9 findings are still open or acknowledged in the firms’ reports: 2 high, 7 low (7 open, 2 acknowledged). No critical finding is reported. Statuses are the security firms’ own.

Show this on your site

Is this your project? Show this record on your own website. The label states what the record holds, links to this page and updates by itself. It is free and needs no sign-in.

Content

Facts

Automatic: the three strongest facts of this project’s own record (its last audit and two more), highlighted. They update with the record. Picking a fact turns Automatic off.

Fixed as
Language

Style

Layout
Theme
Accent
Corners

Format

Size
Date
Embed as
HTML
<head>
<script src="https://widget.trustblock.run/project-widget.min.js" defer></script>
</head>
<body>
<div
data-tb-project-widget
data-tb-project-slug="bitgain"
></div>
</body>

Paste the code where the label should appear. It uses no API credit and updates by itself.

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