DOE on SOL audit reports

DOE on SOL has 2 public audit reports from CertiK; the latest is CertiK, 14 Mar 2023; 3 critical findings, all marked fixed by the firms. It also holds 3 deployed contracts on 1 chain.

Critical findings
No open critical findings
Across the 2 reports, 6 critical findings were reported. Each is marked fixed by the firm that reported it. See the findings
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 (all open).

High
2
Low
9
  • High Open

    Centralization Risks in DOEStaking.sol

    Kudoe - Audit · CertiK · 14 Mar 2023 · Report ↗

  • High Open

    Initial Token Distribution

    Kudoe - Audit · CertiK · 14 Mar 2023 · Report ↗

  • Low Open

    `gDOEstakers` Status in `withdraw()`

    Kudoe - Audit · CertiK · 14 Mar 2023 · Report ↗

  • Low Open

    Incompatibility With Deflationary Tokens

    Kudoe - Audit · CertiK · 14 Mar 2023 · Report ↗

  • Low Open

    Missing Emit Events

    Kudoe - Audit · CertiK · 14 Mar 2023 · Report ↗

  • Low Open

    Missing Error Messages

    Kudoe - Audit · CertiK · 14 Mar 2023 · Report ↗

  • Low Open

    Potential Incorrect Checks for Fee Ratios

    Kudoe - Audit · CertiK · 14 Mar 2023 · Report ↗

  • Low Open

    Potential Incorrect Hardcode Address

    Kudoe - Audit · CertiK · 14 Mar 2023 · Report ↗

  • Low Open

    Potential Insufficient Reward

    Kudoe - Audit · CertiK · 14 Mar 2023 · Report ↗

  • Low Open

    Return Values Not Handled

    Kudoe - Audit · CertiK · 14 Mar 2023 · Report ↗

All 11 open and acknowledged findings

Audits2

Newest first

ReportSecurity firmDateScopeCritical findingsFindingsSource
Kudoe AuditSecurity firm: CertiKDate: Scope: 3 addresses on Ethereum3 critical findings, fixedFindings: 3 critical · 3 high · 12 low
7 fixed · 11 open
skynet.certik.com ↗
Kudoe - AuditSecurity firm: CertiKDate: Scope: 3 addresses on Ethereum3 critical findings, fixedFindings: 3 critical · 3 high · 12 low
7 fixed · 11 open
skynet.certik.com ↗

Findings18

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

SeverityOpenAcknowledgedFixed
Critical003
High201
Medium000
Low903
HighCentralization Risks in DOEStaking.solKudoe - Audit · CertiK · 14 Mar 2023Open

In the contract `DOEStaking` the role `_owner` has authority over the functions shown in the diagram below. Any compromise to the `_owner` account may allow the hacker to take advantage of this authority and - set the reward, duration, nft reward weight, and maximum NFT eligible for rewards through `setRewardParams()` - enable or disable reward for multiple nfts through `setMultiNftReward()` - set the gDoe address through `setgDOE()` - withdraw all reward tokens through `withdrawReward()` ![](https://accelerator-tasks-prod.acc.corp.certik.com/4a513db872fe489db5a127b8f43f90f7/diagrams/centralization_DOEStaking-DOEStaking-_owner.svg)

Open the report
HighInitial Token DistributionKudoe - Audit · CertiK · 14 Mar 2023Open

All of the `Kudoe` tokens are sent to the contract deployer when deploying the contract. This could be a centralization risk as the deployer can distribute tokens without obtaining the community's consensus. ```solidity=226 _tOwned[_owner] = _tTotal; ``` The designed allocation are explained in the documentation (https://kudoe-tm.gitbook.io/kudoe-tm/kdoe-token/token-allocation). As of 01/27/2023, the project is deployed and `Kudoe` tokens are distributed to multiple addresses. - Approximately 34% are in the `Team Finance Lock` contract. - Approximately 10% are in the `KDOERewards` contract. - Approxmately 10% are in the project's liquidity wallet. - Approximately 2.6% are in the project's staking wallet. - Approximately 2% are in the project's gaming wallet. - Approximately 1% are in the project's team wallet. - Approximately 1% are in the project's development wallet. - Approximately 0.75% are in the project's marketing wallet. The detailed holder list can be found on the Ethereum address [0x5f190f9082878ca141f858c1c90b4c59fe2782c5](https://etherscan.io/token/0x5f190f9082878ca141f858c1c90b4c59fe2782c5#balances)

Open the report
Low`gDOEstakers` Status in `withdraw()`Kudoe - Audit · CertiK · 14 Mar 2023Open

In the current control flow, once the user calls `stakeForgDOE()`, `gDOEstaker` would be set true and cannot be set back to false thus the user will not be able to withdraw `stakedToken` through `withdraw()`.

Open the report
LowIncompatibility With Deflationary TokensKudoe - Audit · CertiK · 14 Mar 2023Open

When transferring standard ERC20 deflationary tokens, the input amount may not be equal to the received amount due to the charged transaction fee. The contract takes the staked token balance into account when calculating the users' reward. An attacker can repeat the process of deposit and withdrawing to lower the token balance in a deflationary token pool and cause the contract to increase the reward amount.

Open the report
LowMissing Emit EventsKudoe - Audit · CertiK · 14 Mar 2023Open

The function that affects the status of sensitive variables should be able to emit events as notifications to users.

Open the report
LowMissing Error MessagesKudoe - Audit · CertiK · 14 Mar 2023Open

The **require** can be used to check for conditions and throw an exception if the condition is not met. It is better to provide a string message containing details about the error that will be passed back to the caller.

Open the report
LowPotential Incorrect Checks for Fee RatiosKudoe - Audit · CertiK · 14 Mar 2023Open

When setting the ratios of fees that will be distributed to liquidity, marketing, development and burn account, the following require statement is applied to ensure the total ratio are smaller than the sum of buy and sell fees. ```solidity=448 function setRatios(uint16 liquidity, uint16 marketing, uint16 development, uint16 burn) external onlyOwner { _ratios.liquidity = liquidity; _ratios.marketing = marketing; _ratios.development = development; _ratios.burn = burn; _ratios.totalSwap = liquidity + marketing + development; uint256 total = _taxRates.buyFee + _taxRates.sellFee; require(_ratios.totalSwap + _ratios.burn <= total, "Cannot exceed sum of buy and sell fees."); } ``` However, the `_ratios` represent the portion of the **charged fees** that will be distributed to different addresses, rather than the portion of the transferred amount. Therefore, the `require` statement is not reasonable and may lead to unexpected revert when changing ratios. For example, the current ratio is set as ```text liquidity: 400 marketing: 200 development: 400 burn: 200 totalSwap: 1000 ``` and the fee is: ```text buyFee: 700 sellFee: 700 transferFee: 0 ``` If both the buy fee and sell fee are decreased to 500, the ratio number of burn and totalSwap will become invalid. Thus, if the team wants to keep the same ratio, both the burn ratio and the total swap ratio need to be changed accordingly.

Open the report
LowPotential Incorrect Hardcode AddressKudoe - Audit · CertiK · 14 Mar 2023Open

In the contract's `constructor()` function, Kudoe is initialized to exclude the fee for PinkLock and Unicrypt (ETH). However, there is no similar logic to check the `block.chainid` for these three lock address. - PinkLock([0x407993575c91ce7643a4d4cCACc9A98c36eE1BBE](https://bscscan.com/address/0x407993575c91ce7643a4d4ccacc9a98c36ee1bbe#code)) was deployed in the Binance Smart Chain, while in the Ethereum, [0x407993575c91ce7643a4d4cCACc9A98c36eE1BBE]{https://etherscan.io/address/0x407993575c91ce7643a4d4ccacc9a98c36ee1bbe} is an EOA address - Unicrypt ([0x663A5C229c09b049E36dCc11a9B0d4a8Eb9db214]{https://etherscan.io/address/0x663a5c229c09b049e36dcc11a9b0d4a8eb9db214}) was deployed in the Ethereum, while in the Binance Smart Chain, it's an EOA address. Same situation with another Unicrypt address (0xDba68f07d1b7Ca219f78ae8582C213d975c25cAf)

Open the report
LowPotential Insufficient RewardKudoe - Audit · CertiK · 14 Mar 2023Open

According to the code logic, the calculation of nft rewards is based on the number of reward tokens acquired and the number of nft staked by the user, and this part of the calculation can be difficult to predict. There may be a shortage of reward tokens, and particularly users may suffer losses if the reward tokens and staked tokens are the same.

Open the report
LowReturn Values Not HandledKudoe - Audit · CertiK · 14 Mar 2023Open

The return values of the low-level calls to transfer ETH are not properly handled. ```solidity=589 if (ratios.marketing > 0) { (success,) = _taxWallets.marketing.call{value: marketingBalance, gas: 35000}(""); } if (ratios.development > 0) { (success,) = _taxWallets.development.call{value: developmentBalance, gas: 35000}(""); } if (ratios.liquidity > 0) { (success,) = _taxWallets.liquidity.call{value: liquidityBalance, gas: 35000}(""); } ``` Therefore, if the call fails to transfer ETH to the corresponding address, it may result in the loss of some ETH as a fee for the corresponding address.

Open the report
Show 1 more
LowWithdrawing `stakedToken` through `gDOE`Kudoe - Audit · CertiK · 14 Mar 2023Open

`_gDOEstakers` may get extra `stakedToken` through `withdrawForgDOE()`.

Open the report

Contracts3

AddressChainSource code
0x5f190f9082878ca141f858c1c90b4c59fe2782c5Chain: EthereumSource code: Verified source
0xef732cd262076e3cec7a1d4e96b052d57b383e69Chain: EthereumSource code: Verified source
0xf541ab2f4dba2071b12da99a9ee83b0c4b719d95Chain: EthereumSource code: Verified source

DOE on SOL: questions

Is DOE on SOL audited?

Trustblock holds 2 public audit reports for DOE on SOL, dated 14 Mar 2023 to 14 Mar 2023. The latest is by CertiK (“Kudoe Audit”).

Who audited DOE on SOL?

CertiK wrote the 2 reports Trustblock holds for DOE on SOL.

Are there open findings in DOE on SOL’s audits?

11 findings are still open or acknowledged in the firms’ reports: 2 high, 9 low (all open). Of 3 critical findings: all marked fixed by the firms. 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="dogs-of-elon"
></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