Coinhound audit reports

Ethereumcoinhound.io

Coinhound has 1 public audit report from CertiK; dated 5 May 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 firm12

Statuses are the security firms’ own

12 findings are still open or acknowledged in the firms’ reports: 3 high, 1 medium, 8 low (8 open, 4 acknowledged).

High
3
Medium
1
Low
8
  • High Acknowledged

    All minted LP tokens are controlled by owner

    Coinhound · CertiK · 5 May 2023 · Report ↗

  • High Acknowledged

    Centralization Related Risks

    Coinhound · CertiK · 5 May 2023 · Report ↗

  • High Acknowledged

    Incorrect Distribution Of Fees

    Coinhound · CertiK · 5 May 2023 · Report ↗

  • Medium Acknowledged

    If `buy` Fees Are Set To 0 Tokens May Not Be Able

    Coinhound · CertiK · 5 May 2023 · Report ↗

  • Low Open

    Any ETH Accidentally Sent To Contract May Be Dist

    Coinhound · CertiK · 5 May 2023 · Report ↗

  • Low Open

    Miscalculation For `maxTokenPerWallet`

    Coinhound · CertiK · 5 May 2023 · Report ↗

  • Low Open

    Missing Emit Events

    Coinhound · CertiK · 5 May 2023 · Report ↗

  • Low Open

    Potential Reentrancy

    Coinhound · CertiK · 5 May 2023 · Report ↗

  • Low Open

    Solidity Version Not Recommended

    Coinhound · CertiK · 5 May 2023 · Report ↗

  • Low Open

    Too Many Digits

    Coinhound · CertiK · 5 May 2023 · Report ↗

All 12 open and acknowledged findings

Audits1

Newest first

ReportSecurity firmDateScopeCritical findingsFindingsSource
CoinhoundSecurity firm: CertiKDate: Scope: 1 address on EthereumNone openFindings: 3 high · 1 medium · 8 low
4 acknowledged · 8 open
skynet.certik.com ↗

Findings12

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

SeverityOpenAcknowledgedFixed
Critical000
High030
Medium010
Low800
LowAny ETH Accidentally Sent To Contract May Be DistCoinhound · CertiK · 5 May 2023Open

In the function `_transfer()`, the difference in the contracts ETH before and after the swap are not checked, causing any ETH that has accidentally been sent to the contract to be included in the distribution of fees.

Open the report
LowMiscalculation For `maxTokenPerWallet`Coinhound · CertiK · 5 May 2023Open

The `amount` that is added to the balance of the `recipient` to check that it does not exceed the `maxTokenPerWallet` does not take into account the fees. If fee is taken on the transfer, then the amount transferred will be `amount - allFee` so that the transaction may fail stating that the `maxTokenPerWallet` was exceeded, when it will not be.

Open the report
LowMissing Emit EventsCoinhound · CertiK · 5 May 2023Open

There should always be events emitted in the sensitive functions that are controlled by centralization roles. The following functions do not emit events: - `excludeFromFee()`; - `excludeFromMaxTokenPerWallet()`; - `migrateETH()`

Open the report
LowPotential ReentrancyCoinhound · CertiK · 5 May 2023Open

A reentrancy attack can occur when the contract creates a function that makes an external call to another untrusted contract before resolving any effects. If the attacker can control the untrusted contract, they can make a recursive call back to the original function, repeating interactions that would have otherwise not run after the external call resolved the effects. **We mark this as informational considering reentrancy is only possible if the development wallet is set as a contract that makes external calls** If the `developmentWallet` is set as a contract that makes an external call in its `fallback()` or `receive()` function, then when ether is transffered to the contract, the external call may be used in order to re-enter the contract. ### External call(s) ```solidity=221 payable(developmentWallet).transfer(developmentPart); ``` ### State variables written after the call(s) ```solidity=223 swapping = false; ``` ```solidity=228 super._transfer(sender, recipient, amount); ``` * This function call executes the following assignment(s). * In `ERC20._transfer`, * `_balances[from] = fromBalance - amount` * In `ERC20._transfer`, * `_balances[to] += amount` ```solidity=235 super._transfer(sender, address(this), allFee); ``` * This function call executes the following assignment(s). * In `ERC20._transfer`, * `_balances[from] = fromBalance - amount` * In `ERC20._transfer`, * `_balances[to] += amount` *Note: Only a sample of 3 assignments (out of 4) are shown above.*

Open the report
LowSolidity Version Not RecommendedCoinhound · CertiK · 5 May 2023Open

The contract `Coinhound` uses an old solidity version. ```solidity=20 pragma solidity 0.8.2; ```

Open the report
LowToo Many DigitsCoinhound · CertiK · 5 May 2023Open

Literals with many digits are difficult to read and review. ```solidity=87 maxTokenPerWallet = 5000000 * (10 ** 18); ``` --- ```solidity=88 maxTokenPerTxn = 10000000 * (10 ** 18); ``` --- ```solidity=89 swapTokensAtAmount = 100000 * (10 ** 18); ``` --- ```solidity=94 _mint(msg.sender, 1000000000 * (10 ** 18)); ```

Open the report
LowUnnecessary ChecksCoinhound · CertiK · 5 May 2023Open

In the function `_transfer()` the following checks are performed: ```solidity require(sender != address(0), "ERC20: transfer from the zero address"); require(recipient != address(0), "ERC20: transfer to the zero address"); ``` However, it any case `super._transfer(sender, recipient, amount)` or `super._transfer(sender, recipient, amount - allFee)` will be called. The `_transfer()` function in Openzeppelin's `ERC20` contract preforms these checks making it unnecessary to check them again.

Open the report
LowUsage of `transfer`/`send` for sending EtherCoinhound · CertiK · 5 May 2023Open

It is not recommended to use Solidity's `transfer()` and `send()` functions for transferring Ether, 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. The following lines use solidities `transfer()` function for transferring Ether. ```solidity=221 payable(developmentWallet).transfer(developmentPart); ``` ```solidity=277 recipient.transfer(address(this).balance); ```

Open the report

Contracts1

AddressChainSource code
0xec505c81d6a7567b5bde804870b1038832fe6da1Chain: EthereumSource code: Verified source

Coinhound: questions

Is Coinhound audited?

Trustblock holds 1 public audit report for Coinhound, dated 5 May 2023. The latest is by CertiK (“Coinhound”).

Who audited Coinhound?

CertiK wrote the report Trustblock holds for Coinhound.

Are there open findings in Coinhound’s audits?

12 findings are still open or acknowledged in the firms’ reports: 3 high, 1 medium, 8 low (8 open, 4 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="coinhound"
></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