BTTY token audit

CertiK1 address on BNB Chain

CertiK reviewed Bitcointry (BTTY token audit) on 21 May 2024: 6 findings, 0 critical; 2 acknowledged, 4 open.

No open critical findings
Open the reportOpen Bitcointry’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
Low400
LowCan't `initialize()` if AMM pair existsOpen

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.

LowLocked Blockchain Native TokensOpen

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 {} ```

LowUnused functionalityOpen

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.

LowUsage of Magic NumbersOpen

Different magic numbers are used as-is in code.

Contracts in scope1

AddressChainSource code
0x2024b9be6b03f2a57d3533ae33c7e1d0b0b4be47Chain: BNB ChainSource code: Verified source

Part of Bitcointry’s security record

Bitcointry
Audits2 audits by 2 firmsLast audit May 2024, by CertiK.
Critical findingsNo open critical findingsAcross 2 reports.
Open Bitcointry’s security record

Security firm

CertiK

1,045 projects reviewed · 1,376 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