Suzume audit reports

Suzume has 1 public audit report from CertiK; dated 20 Jan 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 firm7

Statuses are the security firms’ own

7 findings are still open or acknowledged in the firms’ reports: 7 low (all open).

Low
7
  • Low Open

    Function Visibility Optimization

    Suzume - Audit · CertiK · 20 Jan 2023 · Report ↗

  • Low Open

    Missing Allowance Reset

    Suzume - Audit · CertiK · 20 Jan 2023 · Report ↗

  • Low Open

    Recommended Compiler Version

    Suzume - Audit · CertiK · 20 Jan 2023 · Report ↗

  • Low Open

    Redundant Condition Checks

    Suzume - Audit · CertiK · 20 Jan 2023 · Report ↗

  • Low Open

    Redundant Statements

    Suzume - Audit · CertiK · 20 Jan 2023 · Report ↗

  • Low Open

    Third Party Dependencies

    Suzume - Audit · CertiK · 20 Jan 2023 · Report ↗

  • Low Open

    Variables That Could Be Declared as `constant`

    Suzume - Audit · CertiK · 20 Jan 2023 · Report ↗

Audits1

Newest first

ReportSecurity firmDateScopeCritical findingsFindingsSource
Suzume - AuditSecurity firm: CertiKDate: Scope: 1 address on EthereumNone openFindings: 1 high · 1 medium · 9 low
4 fixed · 7 open
skynet.certik.com ↗

Findings11

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

SeverityOpenAcknowledgedFixed
Critical000
High001
Medium001
Low702
LowFunction Visibility OptimizationSuzume - Audit · CertiK · 20 Jan 2023Open

The following functions are declared as `public` and are not invoked in any of the contracts contained within the project's scope. The functions that are never called internally within the contract should have external visibility. - `approveMax()` - `isExcludedFromReward()` - `isExcludedFromFee()` - `setSwapAndLiquifyEnabled()` - `totalFees()` - `enableTrading()`

Open the report
LowMissing Allowance ResetSuzume - Audit · CertiK · 20 Jan 2023Open

When updating `dexRouter` via function `setNewRouter()`, the new router is approved the maximum allowance from the `Suzume` contract. But the allowance for the old `dexRouter` is still greater than 0.

Open the report
LowRecommended Compiler VersionSuzume - Audit · CertiK · 20 Jan 2023Open

Contract `Suzume` is not using SafeMath, and it allows for compiler version between 0.6.0 and 0.9.0. If the contract is compiled with compiler version earlier than 0.8.0, then SafeMath would be needed to prevent overflow and underflow of arithmetic operation.

Open the report
LowRedundant Condition ChecksSuzume - Audit · CertiK · 20 Jan 2023Open

Some of the *if* and *require* statements are not unnecessary, as the condition check always returns the same value. - Since the startingSupply is hardcoded to 10^12, the condition check on line 365 will always pass. ```solidity=364 startingSupply = 1_000_000_000_000; if (startingSupply < 10000000000000) { _decimals = 18; _decimalsMul = _decimals; } else { _decimals = 9; _decimalsMul = _decimals; } ``` - In function `setTaxesBuy()`, `setTaxesSell()` and `setTaxesTransfer()`, the require statement `require(reflect + liquidity + marketing <= 4900);` will always pass, since the upper limits of the three values add up to 4200. - The *else if* statement on line 613 is not necessary, and can be replaced by a single *else*. ```solidity=605 function setExcludedFromReward(address account, bool enabled) public onlyOwner { if (enabled == true) { require(!_isExcluded[account], "Account is already excluded."); if(_rOwned[account] > 0) { _tOwned[account] = tokenFromReflection(_rOwned[account]); } _isExcluded[account] = true; _excluded.push(account); } else if (enabled == false) { ... ``` - State variable `sameBlockActive` is set to true and cannot be changed. The *if* statement on line 663 will always be true. ```solidity=663 if (sameBlockActive) { if (lpPairs[from]){ require(lastTrade[to] != block.number); lastTrade[to] = block.number; } else { require(lastTrade[from] != block.number); lastTrade[from] = block.number; } } ``` - Condition check on line 729 is unnecessary, as `contractTokenBalance - toLiquify` will always be larger than 0. - The !_hasLiqBeenAdded check on line 778 is redundant. ```solidity=776 if (!_hasLiqBeenAdded) { _checkLiquidityAdd(from, to); if (!_hasLiqBeenAdded && _hasLimits(from, to)) { revert("Only owner can transfer at this time."); } } ```

Open the report
LowRedundant StatementsSuzume - Audit · CertiK · 20 Jan 2023Open

The linked statements do not affect the functionality of the codebase and appear to be either leftovers from test code or older functionality. 1. Library Address is never used. 2. State variable `_liqAddBlock` on line 302 is never used. 3. State variable `_liqAddStamp` on line 303 will be updated, but its value is never used. As a private variable, it cannot be viewed either. 4. State variable `Planted` on line 316 will be updated in function `intializeContract()`, but its value is never used. As a private variable, it cannot be viewed either. 5. Function `getOwner()` on line 453 serves the same purpose of public function `owner()` on line 416. 6. Line 378 updates the allowance of this contract to `dexRouter` address, while line 387 already makes the same approval. 7. When transferring owner, line 430 approves the new owner with the old owner's balance, while this balance will be directly transferred to the new owner as per line 432.

Open the report
LowThird Party DependenciesSuzume - Audit · CertiK · 20 Jan 2023Open

The contract is serving as the underlying entity to interact with third party UniSwap protocols. The scope of the audit would treat those 3rd party entities as black boxes and assume their functional correctness. However in the real world, 3rd parties may be compromised that led to assets lost or stolen.

Open the report
LowVariables That Could Be Declared as `constant`Suzume - Audit · CertiK · 20 Jan 2023Open

The linked variables could be declared as `constant` since these state variables are never modified. ```solidity=256 uint256 private maxReflectFee = 1000; uint256 private maxLiquidityFee = 1000; uint256 private maxMarketingFee = 2200; ``` ```solidity=263 uint256 private masterTaxDivisor = 10000; ``` ```solidity=282 address public DEAD = 0x000000000000000000000000000000000000dEaD; address public ZERO = 0x0000000000000000000000000000000000000000; ``` ```solidity=304 bool private sameBlockActive = true; ```

Open the report

Contracts1

AddressChainSource code
0x0b452278223d3954f4ac050949d7998e373e7e43Chain: EthereumSource code: Verified source

Suzume: questions

Is Suzume audited?

Trustblock holds 1 public audit report for Suzume, dated 20 Jan 2023. The latest is by CertiK (“Suzume - Audit”).

Who audited Suzume?

CertiK wrote the report Trustblock holds for Suzume.

Are there open findings in Suzume’s audits?

7 findings are still open or acknowledged in the firms’ reports: 7 low (all open). 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="suzume"
></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