DAIKOKUTEN SAMA

DAIKOKUTEN SAMA

Date
Auditor
April 2023
Hacksafe
View on Github
Download PDF

Audit Details

Audited project

DAIKOKUTEN SAMA

Deployer address

0xC904988723de486C38be9d8FcD82710eaE6267A7

Client contacts

DAIKOKUTEN SAMA team

Blockchain

Binance smart chain

Disclaimer

This is a limited report on our findings based on our analysis, in accordance with good industry practice as at the date of this report, in relation to cybersecurity vulnerabilities and issues in the framework and algorithms based on smart contracts, the details of which are set out in this report. In order to get a full view of our analysis, it is crucial for you to read the full report. While we have done our best in conducting our analysis and producing this report, it is important to note that you should not rely on this report and cannot claim against us on the basis of what it says or doesn’t say, or how we produced it, and it is important for you to conduct your own independent investigations before making any decisions. We go into more detail on this in the below disclaimer below – please make sure to read it in full.
DISCLAIMER: By reading this report or any part of it, you agree to the terms of this disclaimer. If you do not agree to the terms, then please immediately cease reading this report, and delete and destroy any and all copies of this report downloaded and/or printed by you. This report is provided for information purposes only and on a non-reliance basis, and does not constitute investment advice. No one shall have any right to rely on the report or its contents, and TechRate and its affiliates (including holding companies, shareholders, subsidiaries, employees, directors, officers and other representatives) (HackSafe) owe no duty of care towards you or any other person, nor does HackSafe make any warranty or representation to any person on the accuracy or completeness of the report. The report is provided “as is”, without any conditions, warranties or other terms of any kind except as set out in this disclaimer, and HackSafe hereby excludes all representations, warranties, conditions and other terms (including, without limitation, the warranties implied by law of satisfactory quality, fitness for purpose and the use of reasonable care and skill) which, but for this clause, might have effect in relation to the report. Except and only to the extent that it is prohibited by law, HackSafe hereby excludes all liability and responsibility, and neither you nor any other person shall have any claim against HackSafe, for any amount or kind of loss or damage that may result to you or any other person (including without limitation, any direct, indirect, special, punitive, consequential or pure economic loss or damages, or any loss of income, profits, goodwill, data, contracts, use of money, or business interruption, and whether in delict, tort (including without limitation negligence), contract, breach of statutory duty, misrepresentation (whether innocent or negligent) or otherwise under any claim of any nature whatsoever in any jurisdiction) in any way arising from or connected with this report and the use, inability to use or the results of use of this report, and any reliance on this report
The analysis of the security is purely based on the smart contracts alone. No applications or operations were reviewed for security. No product code has been reviewed.

Procedure

Step 1 - In-Depth Manual Review

Manual line-by-line code reviews to ensure the logic behind each function is sound and safe from various attack vectors. This is the most important and lengthy portion of the audit process (as automated tools often cannot find the nuances that lead to exploits such as flash loan attacks).

Step 2 - Automated Testing

Simulation of a variety of interactions with your Smart Contract on a test blockchain leveraging a combination of automated test tools and manual testing to determine if any security vulnerabilities exist.

Step 3 – Leadership Review

The engineers assigned to the audit will schedule meetings with our leadership team to review the contracts, any comments or findings, and ask questions to further apply adversarial thinking to discuss less common attack vectors.

Step 4 - Resolution of Issues

Consulting with the team to provide our recommendations to ensure the code’s security and optimize its gas efficiency, if possible. We assist project team’s in resolving any outstanding issues or implementing our recommendations.

Step 5 - Published Audit Report

Boiling down results and findings into an easy-to-read report tailored to the project. Our audit reports highlight resolved issues and any risks that exist to the project or its users, along with any remaining suggested remediation measures. Diagrams are included at the end of each report to help users understand the interactions which occur within the project.

Background

HackSafe was commissioned by DAIKOKUTEN SAMA to perform an audit of smart contracts:

  • https://bscscan.com/token/0x834613c64522725b23b458aF04ED1590D189962F#code

The purpose of the audit was to achieve the following:

  • Ensutre that the smart contract functions as intended.
  • Identify potential security issues with the smart contract.
The information in this report should be understand the risk exposure of the smart contract, and as a guide to improve the security posture of the smart contract by remediating the issues that were identified.

Contracts Details

Token contract details for 05.04.2023

Type

: Utility

Contract name

: DKKS

Contract address

: 0x834613c64522725b23b458aF04ED1590D189962F

Total supply

: 1,000,000,000,000,000

Token ticker

: DKKS

Decimals

: 9

Token Holders

: 8,418

Transactions count

: 26,090

Compiler version

: v0.8.4+commit.c7e474f2

Contract deployer address

: 0xC904988723de486C38be9d8FcD82710eaE6267A7

Owner address

: 0Xc904988723de486c38be9d8fcd82710eae6267a7

Audit Summary

According to the standard audit assessment, Customer`s solidity smart contracts are “Secure”. This token contract does contain owner control, which do not make it fully decentralized as owner does have control over smart contract.

Secure

We used various tools like Slither, Mythril and Remix IDE. At the same time this finding is based on critical analysis of the manual audit. All issues found during automated analysis were manually reviewed and applicable vulnerabilities are presented in the issues checking status.
We found 0 critical, 0 high, 0 medium and 0 low and some very low-level issues. These issues are not critical ones.

DAIKOKUTEN SAMA Token Distribution

DAIKOKUTEN-SAMA

DAIKOKUTEN SAMA Token Top 20 Token Holders

DAIKOKUTEN-SAMA1

DAIKOKUTEN SAMA Contract Overview

DAIKOKUTEN-SAMA2

Contract functions details

+Context

  • [Int] _msgSender
  • [Int] _msgData

+[Int] IERC20

  • [Ext] totalSupply
  • [Ext] balanceOf
  • [Ext] transfer #
  • [Ext] allowance
  • [Ext] approve #
  • [Ext] transferFrom #

+[Lib] SafeMath

  • [Int] add
  • [Int] sub
  • [Int] sub
  • [Int] mul
  • [Int] div
  • [Int] div
  • [Int] mod
  • [Int] mod

+[Lib] Address

  • [Int] isContract
  • [Int] sendValue #
  • [Int] functionCall #
  • [Int] functionCall #
  • [Int] functionCallWithValue #
  • [Int] functionCallWithValue #
  • [Pvt] _functionCallWithValue #

+Ownable (Context)

  • [Pub] < Constructor > #
  • [Pub] owner
  • [Pub] renounceOwnership #
    - modifiers: onlyOwner
  • [Pub] transferOwnership #
    - modifiers: onlyOwner
  • [Pub] getUnlockTime
  • [Pub] getTime
  • [Pub] lock #
    - modifiers: onlyOwner
  • [Pub] unlock #

+[Int] IUniswapV2Factory

  • [Ext] feeTo
  • [Ext] feeToSetter
  • [Ext] getPair
  • [Ext] allPairs
  • [Ext] allPairsLength
  • [Ext] createPair #
  • [Ext] setFeeTo #
  • [Ext] setFeeToSetter #

+[Int] IUniswapV2Pair

  • [Ext] name
  • [Ext] symbol
  • [Ext] decimals
  • [Ext] totalSupply
  • [Ext] balanceOf
  • [Ext] allowance
  • [Ext] approve #
  • [Ext] transfer #
  • [Ext] transferFrom #
  • [Ext] DOMAIN_SEPARATOR
  • [Ext] PERMIT_TYPEHASH
  • [Ext] nonces
  • [Ext] permit #
  • [Ext] MINIMUM_LIQUIDITY
  • [Ext] factory
  • [Ext] token0
  • [Ext] token1
  • [Ext] getReserves
  • [Ext] price0CumulativeLast
  • [Ext] price1CumulativeLast
  • [Ext] kLast
  • [Ext] mint #
  • [Ext] burn #
  • [Ext] swap #
  • [Ext] skim #
  • [Ext] sync #
  • [Ext] initialize #

+[Int] IUniswapV2Router01

  • [Ext] factory
  • [Ext] WETH
  • [Ext] addLiquidity #
  • [Ext] addLiquidityETH ($)
  • [Ext] removeLiquidity #
  • [Ext] removeLiquidityETH #
  • [Ext] removeLiquidityWithPermit #
  • [Ext] removeLiquidityETHWithPermit #
  • [Ext] swapExactTokensForTokens #
  • [Ext] swapTokensForExactTokens #
  • [Ext] swapExactETHForTokens ($)
  • [Ext] swapTokensForExactETH #
  • [Ext] swapExactTokensForETH #
  • [Ext] swapETHForExactTokens ($)
  • [Ext] quote
  • [Ext] getAmountOut
  • [Ext] getAmountIn
  • [Ext] getAmountsOut
  • [Ext] getAmountsIn

+[Int] IUniswapV2Router02 (IUniswapV2Router01)

  • [Ext] removeLiquidityETHSupportingFeeOnTransferTokens #
  • [Ext] removeLiquidityETHWithPermitSupportingFeeOnTransferTokens #
  • [Ext] swapExactTokensForTokensSupportingFeeOnTransferTokens #
  • [Ext] swapExactETHForTokensSupportingFeeOnTransferTokens ($)
  • [Ext] swapExactTokensForETHSupportingFeeOnTransferTokens #

+DKKS (Context, IERC20, Ownable)

  • [Pub] < Constructor > #
  • [Pub] name
  • [Pub] symbol
  • [Pub] decimals
  • [Pub] totalSupply
  • [Pub] balanceOf
  • [Pub] transfer #
  • [Pub] allowance
  • [Pub] approve #
  • [Pub] transferFrom #
  • [Pub] increaseAllowance #
  • [Pub] decreaseAllowance #
  • [Pub] isExcludedFromReward
  • [Pub] totalFees
  • [Pub] minimumTokensBeforeSwapAmount
  • [Pub] deliver #
  • [Pub] reflectionFromToken
  • [Pub] tokenFromReflection
  • [Pub] excludeFromReward #
    - modifiers: onlyOwner
  • [Ext] includeInReward #
    - modifiers: onlyOwner
  • [Pvt] _approve #
  • [Pvt] _transfer #
  • [Pvt] swapTokens #
    - modifiers: lockTheSwap
  • [Pvt] swapTokensForEth #
  • [Pvt] swapETHForTokens #
  • [Pvt] addLiquidity #
  • [Pvt] _tokenTransfer #
  • [Pvt] _transferStandard #
  • [Pvt] _transferToExcluded #
  • [Pvt] _transferFromExcluded #
  • [Pvt] _transferBothExcluded #
  • [Pvt] _reflectFee #
  • [Pvt] _getValues
  • [Pvt] _getTValues
  • [Pvt] _getRValues
  • [Pvt] _getRate
  • [Pvt] _getCurrentSupply
  • [Pvt] _takeLiquidity #
  • [Pvt] calculateTaxFee
  • [Pvt] calculateLiquidityFee
  • [Pvt] removeAllFee #
  • [Pvt] restoreAllFee #
  • [Pub] isExcludedFromFee
  • [Pub] excludeFromFee #
    - modifiers: onlyOwner
  • [Pub] includeInFee #
    - modifiers: onlyOwner
  • [Ext] setBuyTaxFeePercent #
    - modifiers: onlyOwner
  • [Ext] setSellTaxFeePercent #
    - modifiers: onlyOwner
  • [Ext] setBuyLiquidityFeePercent #
    - modifiers: onlyOwner
  • [Ext] setSellLiquidityFeePercent #
    - modifiers: onlyOwner
  • [Ext] setMaxTxAmount #
    - modifiers: onlyOwner
  • [Ext] setMarketingDivisor #
    - modifiers: onlyOwner
  • [Ext] setNumTokensSellToAddToLiquidity #
    - modifiers: onlyOwner
  • [Ext] setMaxTokenHolder #
    - modifiers: onlyOwner
  • [Ext] setMarketingAddress #
    - modifiers: onlyOwner
  • [Pub] changeRouterVersion #
    - modifiers: onlyOwner
  • [Pub] setSwapAndLiquifyEnabled #
    - modifiers: onlyOwner
  • [Ext] prepareForPreSale #
    - modifiers: onlyOwner
  • [Ext] goLive #
    - modifiers: onlyOwner
  • [Pub] transferBatch #
  • [Pvt] transferToAddressETH #
  • [Ext] < Fallback > ($)

($) = payable function

# = non-constant function

Issues Checking Status

No
Title
Status
1.
Unlocked Compiler Version
Passed
2.
Missing Input Validation
Passed
3.
Race conditions and Reentrancy. Cross-function race conditions.
Passed
4.
Possible delays in data delivery
Passed
5.
Oracle calls.
Passed
6.
Timestamp dependence.
Passed
7.
Integer Overflow and Underflow
Passed
8.
DoS with Revert.
Passed
9.
DoS with block gas limit.
Passed
10.
Methods execution permissions.
Passed
11.
Economy model of the contract
Passed
12.
Private user data leaks.
Passed
13.
Malicious Event log
Passed
14.
Scoping and Declarations.
Passed
15.
Uninitialized storage pointers.
Passed
16.
Arithmetic accuracy.
Passed
17.
Design Logic.
Passed
18.
Safe Open Zeppelin contracts implementation and usage.
Passed
19.
Incorrect Naming State Variable
Passed
20.
Too old version
Passed

Severity Definitions

Risk Level
Description
Critical
Critical vulnerabilities are usually straightforward to exploit and can lead to assets loss or data manipulations.
High
High-level vulnerabilities are difficult to exploit; however, they also have a significant impact on smart contract execution, e.g., public access to crucial functions
Medium
Medium-level vulnerabilities are important to fix; however, they can't lead to assets loss or data manipulations.
Low
Low-level vulnerabilities are mostly related to outdated, unused, etc. code snippets that can't have a significant impact on execution.

Security Issues

Critical Severity Issues

No critical severity issue found.

High Severity Issues

No high severity issue found.

Medium Severity Issues

No Medium severity issues found.

Low Severity Issues

No low severity issue found.

Centralization

Owner privileges (In the period when the owner is not renounced) :

  • DAIKOKUTEN SAMA Contract:
  • Owner can change buy/sell tax and liquidity fees.
  • Owner can change maximum transaction amount.
  • Owner can exclude from the fee.
  • Owner can change marketingDivisor.
  • Owner can change minimum number of tokens to add to liquidity.
  • Owner can change _ maxTokenHolder value.
  • Owner can change marketing address.
  • Owner can change router address.
  • Owner can lock and unlock. By the way, using these functions the owner could retake privileges even after the ownership was renounced.
  • Owner can enable presale and live setting presets.

Conclusion

Smart contract contains no medium severity issues! Liquidity pair contract’s security is not checked due to out of scope.
HackSafe note: Please check the disclaimer above and note, the audit makes no statements or warranties on business model, investment attractiveness or code sustainability. The report is provided for the only contract mentioned in the report and does not include any other potential contracts deployed by Owner.

Send your project now

Fill the details to be connected with our experts.

Send your project now

Fill the details to be connected with our experts.