The variable `_percent` which type is `uint256` is always no less than zero.

Tautology or Contradiction Issue

`tx.origin` check will be no longer valid after EIP-3074 is added in the coming months. EIP3074 introduces two EVM instructions AUTH and AUTHCALL. The first sets a context variable authorized based on an ECDSA signature. The second sends a call as the authorized. This essentially delegates control of the EOA to a smart contract. This means there will be a way for smart contracts to send transactions in the context of an Externally Owned Account, thus bypassing this check.

Also tx.origin is widely discourage as there are possible phishing attempts.

Dangerous Usage of `tx.origin`

The return values of function  `addLiquidityETH` is not properly handled.

Return Value Not Handled

The linked variables do not conform to the standard naming convention of Solidity whereby functions and variable names utilize the format unless variables are declared as constant in which case they utilize the format.

- Function IUniswapV2Pair.DOMAIN_SEPARATOR() (ChiaotzuInu.sol#127) is not in mixedCase
- Function IUniswapV2Pair.PERMIT_TYPEHASH() (ChiaotzuInu.sol#128) is not in mixedCase
- Function IUniswapV2Pair.MINIMUM_LIQUIDITY() (ChiaotzuInu.sol#145) is not in mixedCase
- Function IUniswapV2Router01.WETH() (ChiaotzuInu.sol#818) is not in mixedCase

- Event ChiaotzuInumarketingWalletUpdated(address,address) (ChiaotzuInu.sol#1037) is not in CapWords
- Event ChiaotzuInudevWalletUpdated(address,address) (ChiaotzuInu.sol#1039) is not in CapWords

- Parameter ChiaotzuInu.updateBuyFees(uint256,uint256,uint256)._marketingFee (ChiaotzuInu.sol#1134) is not in mixedCase
- Parameter ChiaotzuInu.updateBuyFees(uint256,uint256,uint256)._liquidityFee (ChiaotzuInu.sol#1134) is not in mixedCase
- Parameter ChiaotzuInu.updateBuyFees(uint256,uint256,uint256)._devFee (ChiaotzuInu.sol#1134) is not in mixedCase
- Parameter ChiaotzuInu.updateSellFees(uint256,uint256,uint256)._marketingFee (ChiaotzuInu.sol#1142) is not in mixedCase
- Parameter ChiaotzuInu.updateSellFees(uint256,uint256,uint256)._liquidityFee (ChiaotzuInu.sol#1142) is not in mixedCase
- Parameter ChiaotzuInu.updateSellFees(uint256,uint256,uint256)._devFee (ChiaotzuInu.sol#1142) is not in mixedCase
- Parameter ChiaotzuInu.setAutoLPBurnSettings(uint256,uint256,bool)._frequencyInSeconds (ChiaotzuInu.sol#1391) is not in mixedCase
- Parameter ChiaotzuInu.setAutoLPBurnSettings(uint256,uint256,bool)._percent (ChiaotzuInu.sol#1391) is not in mixedCase
- Parameter ChiaotzuInu.setAutoLPBurnSettings(uint256,uint256,bool)._Enabled (ChiaotzuInu.sol#1391) is not in mixedCase
- Parameter ChiaotzuInu.setPenaltyFee(uint256,uint256)._earlySellMarketingFee (ChiaotzuInu.sol#1450) is not in mixedCase
- Parameter ChiaotzuInu.setPenaltyFee(uint256,uint256)._earlySellLiquidityFee (ChiaotzuInu.sol#1450) is not in mixedCase
- Parameter ChiaotzuInu.setReflectionFee(uint256,uint256)._buyReflectionFee (ChiaotzuInu.sol#1462) is not in mixedCase
- Parameter ChiaotzuInu.setReflectionFee(uint256,uint256)._sellReflectionFee (ChiaotzuInu.sol#1462) is not in mixedCase
- Parameter ChiaotzuInu.manageBots(address[],bool)._addresses (ChiaotzuInu.sol#1528) is not in mixedCase
- Parameter ChiaotzuInu.manageBots(address[],bool)._isBot (ChiaotzuInu.sol#1528) is not in mixedCase

- Constant ChiaotzuInu._tTotal (ChiaotzuInu.sol#957) is not in UPPER_CASE_WITH_UNDERSCORES
- Constant ChiaotzuInu.deadAddress (ChiaotzuInu.sol#967) is not in UPPER_CASE_WITH_UNDERSCORES

- Variable ChiaotzuInu._penaltyFeeTime (ChiaotzuInu.sol#1007) is not in mixedCase
- Variable ChiaotzuInu._isExcludedMaxTransactionAmount (ChiaotzuInu.sol#1025) is not in mixedCase


Variable Naming Convention

The linked addresses should be checked before assignment to make sure it is not zero addresses. 

Missing Zero Address Validation

The linked variables could be declared as `constant` since these state variables are never modified.

Variables That Could Be Declared As `constant`

The linked functions that affect the status of sensitive variables should be able to emit events as notifications to users.

Missing Emit Events

The following functions are declared as `public`, contain array function arguments, 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. 

Function Visibility Optimization

The contract is serving as the underlying entity to interact with third-party DEX protocols. The scope of the audit treats 3rd party entities as black boxes and assumes their functional correctness. However, in the real world, 3rd parties can be compromised and this may lead to lost or stolen assets. In addition, upgrades of 3rd parties can possibly create severe impacts.

Third Party Dependencies

The library `SafeMathInt` and `SafeMathUint` are never used within the project and thus can be removed.

Unused Libraries

The owner is exempt from fees and transaction limits by default. Yet when ownership is reset through `renounceOwnership()` or `transferOwnership()`, the exemptions are not granted to the new owner nor are they revoked from the previous owner.

Privilege not Revoked or Transferred

There are many hardcode addresses in this codebase.

Hardcode Addresses

A sandwich attack might happen when an attacker observes a transaction swapping tokens or adding liquidity without setting restrictions on slippage or minimum output amount. The attacker can manipulate the exchange rate by front-running (before the transaction is attacked) a transaction to purchase one of the assets and make profits by back-running (after the transaction is attacked) a transaction to sell the asset.

The following functions are called without setting restrictions on slippage or minimum output amount, so transactions triggering these functions are vulnerable to sandwich attacks, especially when the input amount is large:

- `uniswapV2Router.swapExactTokensForETHSupportingFeeOnTransferTokens()`
- `uniswapV2Router.addLiquidityETH()`

Potential Sandwich Attacks

All of the `ChiaotzuInu` tokens are sent to the contract deployer when deploying the contract. This could be a centralization risk as the deployer can distribute `ChiaotzuInu` tokens without obtaining the consensus of the community.

Initial Token Distribution

Half the amount of liquidity tokens are not swapped, therefore the denominator `totalTokensToSwap` does not correspond to the actual ETH balance change. 

The resulting `ethForMarketing` and `ethForDev` will be a little less than deserved and `ethForLiquidity` will be more than what should be when `amountToSwapFroETH` is used as the denominator.

Incorrect Calculation

The circulating supply decreases as tokens are transferred to a dead address, while the updates of the transaction limit, wallet maximum, and swapping threshold always use the `_totalSupply` as the reference.

Discussion for Transaction Limit

It seems that when neither the sender nor receiver are pairs or exempt from limits, the transaction amount would not be subject to the `maxTransactionAmount` or `maxWallet`.

Incomplete Restriction

The linked statements do not affect the functionality of the codebase.

Redundant Codes

The `if` branches describe three fee schemes yet they may overlap in current logic. In such a scenario, fees are overwritten in each snippet yet `tokensForMarketing`, `tokensForLiquidity`, and `tokensForDev` are tallied.

In particular, if there are both sell fees and penalty fees, `tokensForMarketing`, `tokensForLiquidity`, and `tokensForDev` will be tallied twice according to each fee. However, `fees` will be overwritten in the penalty fee snippet and only applied to the transfer amount once.

Overlapping Fee Schemes

The linked code snippet add all receiver to `bots` in the first 6 blocks after launch. This seems unnecessarily harsh.

Automatic Blacklisting

A portion of tokens on pair is automatically burnt during transfer. This will change the ratio of tokens on the pair and liquidity providers may have to pay more to withdraw less.

Automatic Burning on Pair

`tokensForLiquidity` has been reset therefore the logged value would always be zero.

Incorrect Log

In the contract `ChiaotzuInu` the role `_owner` has authority over the functions shown in the diagram below.

![](https://accelerator-tasks-prod.s3.amazonaws.com/7426bb995e0a4b0bb5a88f916fab7e19/diagrams/centralization-ChiaotzuInu-_owner.svg)

In the contract `Ownable` the role `_owner` has authority over the functions shown in the diagram below.

![](https://accelerator-tasks-prod.s3.amazonaws.com/7426bb995e0a4b0bb5a88f916fab7e19/diagrams/centralization-Ownable-_owner.svg)

Exchange	Pair	Price	Spread	24H Volume	24H Vol USD	Volume %

No Data

Tx Hash	Caller	Contract	Function	Timestamp

No Data

Chiaotzu Inu

Highlights & Alerts

Positive Community Sentiment (top 25%)

A Highly Centralized Project

Code Audit History

23

0

15

2

6

Skynet

Sentiment Analysis

Market Volatility

Governance & Autonomy