Bitcointry audit reports

Bitcointry has 2 public audit reports from CertiK and Cyberscope; the latest is CertiK, 21 May 2024; no critical findings reported. It also holds 1 deployed contract on 1 chain.

Critical findings
No open critical findings
Across 2 reports.
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 firm11

Statuses are the security firms’ own

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

High
2
Low
9
  • High Acknowledged

    Centralization Risks in Token.sol

    BTTY token audit · CertiK · 21 May 2024 · Report ↗

  • High Acknowledged

    Initial Token Distribution

    BTTY token audit · CertiK · 21 May 2024 · Report ↗

  • Low Open

    Can't `initialize()` if AMM pair exists

    BTTY token audit · CertiK · 21 May 2024 · Report ↗

  • Low Open

    Locked Blockchain Native Tokens

    BTTY token audit · CertiK · 21 May 2024 · Report ↗

  • Low Open

    Unused functionality

    BTTY token audit · CertiK · 21 May 2024 · Report ↗

  • Low Open

    Usage of Magic Numbers

    BTTY token audit · CertiK · 21 May 2024 · Report ↗

  • Low Open

    Untitled finding

    Bitcointry Token · Cyberscope · 13 Jan 2024 · Report ↗

  • Low Open

    Untitled finding

    Bitcointry Token · Cyberscope · 13 Jan 2024 · Report ↗

  • Low Open

    Untitled finding

    Bitcointry Token · Cyberscope · 13 Jan 2024 · Report ↗

  • Low Open

    Untitled finding

    Bitcointry Token · Cyberscope · 13 Jan 2024 · Report ↗

All 11 open and acknowledged findings

Audits2

Newest first

ReportSecurity firmDateScopeCritical findingsFindingsSource
BTTY token auditSecurity firm: CertiKDate: Scope: 1 address on BNB ChainNone openFindings: 2 high · 4 low
2 acknowledged · 4 open
skynet.certik.com ↗
Bitcointry TokenSecurity firm: CyberscopeDate: Scope: 1 address on BNB ChainNone openFindings: 5 low
5 open
cyberscope.io ↗

Findings11

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

SeverityOpenAcknowledgedFixed
Critical000
High020
Medium000
Low900
LowCan't `initialize()` if AMM pair existsBTTY token audit · CertiK · 21 May 2024Open

The contract allows the `owner` to `initialize()` and set `routerV2`/`pairV2` values. However, the function will fail if `Pair(address(this), routerV2.WETH()` already exists. That is the only way to set `routerV2` value.

Open the report
LowLocked Blockchain Native TokensBTTY token audit · CertiK · 21 May 2024Open

The contract has a `receive()` function or payable functions, making it able to receive native tokens. However, it does not have a function to withdraw the funds, which can lead to permanently locked tokens within the contract. ```solidity=65 receive() external payable {} ```

Open the report
LowUnused functionalityBTTY token audit · CertiK · 21 May 2024Open

State variable `_swapping` is never set and thus the check `if (!_swapping...` in `_transfer()` is redundant. --- ```sol=161 if (isPair) { } ``` The code in `_setAMMPair()` seems to be leftover. --- `totalFees` always consists of `stakingFees` only. So, transferring the non-`stakingPortion` of fees is redundant: ```sol=134 if (fees > 0) { super._transfer(from, address(this), fees); } ``` Also, the tokens transferred this way to the contract address can't be extracted. There is no need to exclude the contract address from fees: ```sol=55 excludeFromFees(address(this), true); ``` The `totalFees` state field can be eliminated. --- ```sol=65 receive() external payable {} ``` The contract is not supposed to receive native tokens, the `receive()` function is redundant.

Open the report
LowUsage of Magic NumbersBTTY token audit · CertiK · 21 May 2024Open

Different magic numbers are used as-is in code.

Open the report
LowUntitled findingBitcointry Token · Cyberscope · 13 Jan 2024Open

The report gives no description here.

Open the report
LowUntitled findingBitcointry Token · Cyberscope · 13 Jan 2024Open

The report gives no description here.

Open the report
LowUntitled findingBitcointry Token · Cyberscope · 13 Jan 2024Open

The report gives no description here.

Open the report
LowUntitled findingBitcointry Token · Cyberscope · 13 Jan 2024Open

The report gives no description here.

Open the report
LowUntitled findingBitcointry Token · Cyberscope · 13 Jan 2024Open

The report gives no description here.

Open the report

Contracts1

AddressChainSource code
0x2024b9be6b03f2a57d3533ae33c7e1d0b0b4be47Chain: BNB ChainSource code: Verified source

Bitcointry: questions

Is Bitcointry audited?

Trustblock holds 2 public audit reports for Bitcointry, dated 13 Jan 2024 to 21 May 2024. The latest is by CertiK (“BTTY token audit”).

Who audited Bitcointry?

2 security firms wrote the reports Trustblock holds for Bitcointry: CertiK and Cyberscope.

Are there open findings in Bitcointry’s audits?

11 findings are still open or acknowledged in the firms’ reports: 2 high, 9 low (9 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="bitcointry-token"
></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