Kawaii Kiba Token Logo

KIBA [Kawaii Kiba] Token

ALERT: rug pull scam

About KIBA

Listings

Token 10 months
CoinMarketCap 10 months

Long term, our vision for $KIBA token is to develop multiple eventual utilities. Our first being the start of development for our metaverse integration, which we aim to begin during Q1.

What is play-to-earn and why choose this?

With some estimations predicting the global gaming market reaching a value of $256 billion by 2025, online gaming has indisputably become a phenomenon that can no longer be ignored. Today, millions of people across the world play a variety of games, where they create communities and interact with each other. Thus, the Kawaii Kiba project, with its intrinsic community-centric focus, is well aligned with the concept of creating a parallel ecosystem where our members can escape reality, interact with one another in a fun and light-hearted manner, and earn a little $KIBA along the way. Play-to-earn is exactly what it sounds like, you play a game and earn cryptocurrency while doing so. It is a powerful psychological model that combines both entertainment and earning money, giving our users a real life reward for playing our game.

Why launch a token first?

There are a few reasons for this, the first being raising funds to support the development costs of the metaverse, the second being to build a community prior to the launch of the game so that there is more hype around the launch and we can use the opinions of the community during testing to improve the game.

Social

Laser Scorebeta Last Audit: 30 November 2021

report
Token seems to be a scam (type: rug pull scam).

Anti-Scam

Links


Unable to find manual contract audit (e.g. Certik, PeckShield, Solidity...)

Reentrancy in KIBA._transfer(address,address,uint256) (#995-1039):
External calls:
- swapAndLiquify(contractTokenBalance) (#1026)
- uniswapV2Router.addLiquidityETH{value: ethAmount}(address(this),tokenAmount,0,0,owner(),block.timestamp) (#1087-1094)
- uniswapV2Router.swapExactTokensForETHSupportingFeeOnTransferTokens(tokenAmount,0,path,address(this),block.timestamp) (#1073-1079)
External calls sending eth:
- swapAndLiquify(contractTokenBalance) (#1026)
- uniswapV2Router.addLiquidityETH{value: ethAmount}(address(this),tokenAmount,0,0,owner(),block.timestamp) (#1087-1094)
State variables written after the call(s):
- _tokenTransfer(from,to,amount,takeFee) (#1038)
- _rOwned[address(this)] = _rOwned[address(this)].add(rLiquidity) (#951)
- _rOwned[sender] = _rOwned[sender].sub(rAmount) (#1129)
- _rOwned[sender] = _rOwned[sender].sub(rAmount) (#1120)
- _rOwned[sender] = _rOwned[sender].sub(rAmount) (#1140)
- _rOwned[sender] = _rOwned[sender].sub(rAmount) (#867)
- _rOwned[recipient] = _rOwned[recipient].add(rTransferAmount) (#1121)
- _rOwned[recipient] = _rOwned[recipient].add(rTransferAmount) (#1131)
- _rOwned[recipient] = _rOwned[recipient].add(rTransferAmount) (#1141)
- _rOwned[recipient] = _rOwned[recipient].add(rTransferAmount) (#869)
- _tokenTransfer(from,to,amount,takeFee) (#1038)
- _rTotal = _rTotal.sub(rFee) (#906)
- _tokenTransfer(from,to,amount,takeFee) (#1038)
- _tOwned[address(this)] = _tOwned[address(this)].add(tLiquidity) (#953)
- _tOwned[sender] = _tOwned[sender].sub(tAmount) (#1139)
- _tOwned[sender] = _tOwned[sender].sub(tAmount) (#866)
- _tOwned[recipient] = _tOwned[recipient].add(tTransferAmount) (#1130)
- _tOwned[recipient] = _tOwned[recipient].add(tTransferAmount) (#868)
Apply the check-effects-interactions pattern.

Additional information: link

KIBA.addLiquidity(uint256,uint256) (#1082-1095) ignores return value by uniswapV2Router.addLiquidityETH{value: ethAmount}(address(this),tokenAmount,0,0,owner(),block.timestamp) (#1087-1094)
Ensure that all the return values of the function calls are used.

Additional information: link

KIBA._approve(address,address,uint256).owner (#987) shadows:
- Ownable.owner() (#419-421) (function)
Rename the local variables that shadow another component.

Additional information: link

KIBA.setMaxTxPercent(uint256) (#891-895) should emit an event for:
- _maxTxAmount = _tTotal.mul(maxTxPercent).div(10 ** 2) (#892-894)
Emit an event for critical parameter changes.

Additional information: link

Reentrancy in KIBA.transferFrom(address,address,uint256) (#792-796):
External calls:
- _transfer(sender,recipient,amount) (#793)
- uniswapV2Router.addLiquidityETH{value: ethAmount}(address(this),tokenAmount,0,0,owner(),block.timestamp) (#1087-1094)
- uniswapV2Router.swapExactTokensForETHSupportingFeeOnTransferTokens(tokenAmount,0,path,address(this),block.timestamp) (#1073-1079)
External calls sending eth:
- _transfer(sender,recipient,amount) (#793)
- uniswapV2Router.addLiquidityETH{value: ethAmount}(address(this),tokenAmount,0,0,owner(),block.timestamp) (#1087-1094)
State variables written after the call(s):
- _approve(sender,_msgSender(),_allowances[sender][_msgSender()].sub(amount,ERC20: transfer amount exceeds allowance)) (#794)
- _allowances[owner][spender] = amount (#991)
Apply the check-effects-interactions pattern.

Additional information: link

Reentrancy in KIBA.transferFrom(address,address,uint256) (#792-796):
External calls:
- _transfer(sender,recipient,amount) (#793)
- uniswapV2Router.addLiquidityETH{value: ethAmount}(address(this),tokenAmount,0,0,owner(),block.timestamp) (#1087-1094)
- uniswapV2Router.swapExactTokensForETHSupportingFeeOnTransferTokens(tokenAmount,0,path,address(this),block.timestamp) (#1073-1079)
External calls sending eth:
- _transfer(sender,recipient,amount) (#793)
- uniswapV2Router.addLiquidityETH{value: ethAmount}(address(this),tokenAmount,0,0,owner(),block.timestamp) (#1087-1094)
Event emitted after the call(s):
- Approval(owner,spender,amount) (#992)
- _approve(sender,_msgSender(),_allowances[sender][_msgSender()].sub(amount,ERC20: transfer amount exceeds allowance)) (#794)
Apply the check-effects-interactions pattern.

Additional information: link

Ownable.unlock() (#466-471) uses timestamp for comparisons
Dangerous comparisons:
- require(bool,string)(now > _lockTime,Contract is locked until 7 days) (#468)
Avoid relying on block.timestamp.

Additional information: link

Address._functionCallWithValue(address,bytes,uint256,string) (#364-385) uses assembly
- INLINE ASM (#377-380)
Do not use evm assembly.

Additional information: link

SafeMath.mod(uint256,uint256,string) (#232-235) is never used and should be removed
Remove unused functions.

Additional information: link

KIBA._previousLiquidityFee (#714) is set pre-construction with a non-constant function or state variable:
- _liquidityFee
Remove any initialization of state variables via non-constant state variables or function calls. If variables must be set upon contract deployment, locate initialization in the constructor instead.

Additional information: link

Low level call in Address._functionCallWithValue(address,bytes,uint256,string) (#364-385):
- (success,returndata) = target.call{value: weiValue}(data) (#368)
Avoid low-level calls. Check the call success. If the call is meant for a contract, check for code existence

Additional information: link

Variable KIBA._maxTxAmount (#722) is not in mixedCase
Follow the Solidity naming convention.

Additional information: link

Redundant expression "this (#244)" inContext (#238-247)
Remove redundant statements if they congest code but offer no value.

Additional information: link

Variable KIBA._getRValues(uint256,uint256,uint256,uint256).rTransferAmount (#927) is too similar to KIBA._transferFromExcluded(address,address,uint256).tTransferAmount (#1138)
Prevent variables from having similar names.

Additional information: link

KIBA.slitherConstructorVariables() (#688-1151) uses literals with too many digits:
- numTokensSellToAddToLiquidity = 3000000000000 * 10 ** 1 * 10 ** 9 (#723)
Use: Ether suffix, Time suffix, or The scientific notation

Additional information: link

KIBA.numTokensSellToAddToLiquidity (#723) should be constant
Add the constant attributes to state variables that never change.

Additional information: link

isExcludedFromFee(address) should be declared external:
- KIBA.isExcludedFromFee(address) (#983-985)
Use the external attribute for functions never called from the contract.

Additional information: link

Holders:


Number of Binance Smart Chain (BSC) token holders is less than 100. Token is either dead or inactive. Ignore for presale.


Average PancakeSwap trading volume, liqudity, number of swaps are extremely low. Token seems to be dead.


Token is deployed only at one blockchain


Token has only one trading pair


Unable to find PancakeSwap trading pair to compute liquidity.


Unable to find PancakeSwap trading pair to compute volume.


Unable to find PancakeSwap trading pair to compute number of swaps.


Twitter account link seems to be invalid


Telegram account has relatively few subscribers


Unable to find Blog account (Reddit or Medium)


Unable to find Youtube account


Unable to find Discord account


Unable to find website, listings and other project-related information


Young tokens have high risks of price dump / death


Token has no active CoinGecko listing / rank


Token has no active CoinMarketCap listing / rank

Price for KIBA