Shin [Shinomics] Token
About Shin
Listings
Website
The token has an ambitious plan, it is not just planning to stay as a meme token. It is looking to develop and include more features and products that investors and users can gain from. The plans include the launching of the first NFT cards, and mobile game development during phase three. There are also plans to build a partnership, launch big promotions including NFT card giveaway as well as brand Shinomics. In phase four, Shinomics developers are planning to launch Beta Game, conduct the second audit with Cetrik, carry out a website redesign and publish the mobile game. There is also a ShinSwap that is scheduled to launch soon. Reviews have described the token as highly promising based on its performance in the market a few days after its launch as well as the planned features.
The team behind Shinomics
According to crypto token analysts, one of the factors that investors look at while selecting a token to invest in is the team behind its development. The analyst points out that the team needs to be well experienced in blockchain as well as running the token. Shinomics as pointed out by its developers meet this threshold. Behind Shinomics is an experienced team that prides itself on the knowledge that is required to build a successful project. The team has mobile core developers with loads of experience in the field.
The token’s audit
TechRate, a company that specializes in free smart contract checks performed an audit of Shinomics smart contract where it sought to ascertain whether it was functioning as intended as well as identify potential security issues. From this audit, the token passed in all the 21 issues that were checked including compiler errors, possible delays in data delivery, front running, timestamp dependence, integer overflow and underflow, methods execution permissions, Oracle calls, design logic, fallback function security, and malicious event log among others. A second audit is scheduled during Phase 4 of the project development. It will be conducted by Cetrik, a leading security-based ranking platform that analyses and monitors blockchain protocols and DeFi projects.
Social
Laser Scorebeta Last Audit: 30 November 2021
Shinomics.swapBack() (#546-585) sends eth to arbitrary user
Dangerous calls:
- (success) = address(marketingFeeReceiver).call{gas: 30000,value: amountBNBMarketing}() (#571)
Ensure that an arbitrary user cannot withdraw unauthorized funds.
Additional information: link
Reentrancy in Shinomics._transferFrom(address,address,uint256) (#479-501):
External calls:
- swapBack() (#484)
- router.swapExactTokensForETHSupportingFeeOnTransferTokens(amountToSwap,0,path,address(this),block.timestamp) (#557-563)
- distributor.deposit{value: amountBNBReflection}() (#570)
- (success) = address(marketingFeeReceiver).call{gas: 30000,value: amountBNBMarketing}() (#571)
- router.addLiquidityETH{value: amountBNBLiquidity}(address(this),amountToLiquify,0,0,autoLiquidityReceiver,block.timestamp) (#575-582)
- triggerAutoBuyback() (#485)
- router.swapExactETHForTokensSupportingFeeOnTransferTokens{value: amount}(0,path,to,block.timestamp) (#623-628)
External calls sending eth:
- swapBack() (#484)
- distributor.deposit{value: amountBNBReflection}() (#570)
- (success) = address(marketingFeeReceiver).call{gas: 30000,value: amountBNBMarketing}() (#571)
- router.addLiquidityETH{value: amountBNBLiquidity}(address(this),amountToLiquify,0,0,autoLiquidityReceiver,block.timestamp) (#575-582)
- triggerAutoBuyback() (#485)
- router.swapExactETHForTokensSupportingFeeOnTransferTokens{value: amount}(0,path,to,block.timestamp) (#623-628)
State variables written after the call(s):
- _balances[sender] = _balances[sender].sub(amount,Insufficient Balance) (#489)
- _balances[recipient] = _balances[recipient].add(amountReceived) (#492)
- amountReceived = takeFee(sender,recipient,amount) (#491)
- _balances[address(this)] = _balances[address(this)].add(feeAmount) (#533)
- triggerAutoBuyback() (#485)
- inSwap = true (#424)
- inSwap = false (#424)
Apply the check-effects-interactions pattern.
Additional information: link
DividendDistributor.distributeDividend(address) (#321-332) ignores return value by SHIB.transfer(shareholder,amount) (#327)
Use SafeERC20, or ensure that the transfer/transferFrom return value is checked.
Additional information: link
Unable to verify that contract auditor is trusted: Certik, Quantstamp, Hacken, Solidity, Paladinsec, Openzeppelin, Verichains
Combination 1: Reentrancy vulnerabilities + Functions that send Ether to arbitraty destination. Usual for scams. May be justified by some complex mechanics (e.g. rebase, reflections). DYOR & manual audit are advised.
Combination 2: Unchecked transfer + Functions that send Ether to arbitraty destination. Usual for scams. May be justified by some complex mechanics (e.g. rebase, reflections). DYOR & manual audit are advised.
Combination 3: Reentrancy vulnerabilities + Unchecked transfer vulnerability. Usual for scams. May be justified by some complex mechanics (e.g. rebase, reflections). DYOR & manual audit are advised.
Reentrancy in DividendDistributor.setShare(address,uint256) (#254-268):
External calls:
- distributeDividend(shareholder) (#256)
- SHIB.transfer(shareholder,amount) (#327)
State variables written after the call(s):
- shares[shareholder].amount = amount (#266)
- shares[shareholder].totalExcluded = getCumulativeDividends(shares[shareholder].amount) (#267)
Apply the check-effects-interactions pattern.
Additional information: link
Shinomics.swapBack() (#546-585) ignores return value by router.addLiquidityETH{value: amountBNBLiquidity}(address(this),amountToLiquify,0,0,autoLiquidityReceiver,block.timestamp) (#575-582)
Ensure that all the return values of the function calls are used.
Additional information: link
Shinomics.setTargetLiquidity(uint256,uint256) (#698-701) should emit an event for:
- targetLiquidity = _target (#699)
- targetLiquidityDenominator = _denominator (#700)
Emit an event for critical parameter changes.
Additional information: link
Shinomics.setFeeReceivers(address,address)._marketingFeeReceiver (#688) lacks a zero-check on :
- marketingFeeReceiver = _marketingFeeReceiver (#690)
Check that the address is not zero.
Additional information: link
Reentrancy in Shinomics.triggerManualBuyback(uint256,bool) (#595-601):
External calls:
- buyTokens(amount,DEAD) (#596)
- router.swapExactETHForTokensSupportingFeeOnTransferTokens{value: amount}(0,path,to,block.timestamp) (#623-628)
State variables written after the call(s):
- buybackMultiplierTriggeredAt = block.timestamp (#598)
Apply the check-effects-interactions pattern.
Additional information: link
Reentrancy in Shinomics.triggerManualBuyback(uint256,bool) (#595-601):
External calls:
- buyTokens(amount,DEAD) (#596)
- router.swapExactETHForTokensSupportingFeeOnTransferTokens{value: amount}(0,path,to,block.timestamp) (#623-628)
Event emitted after the call(s):
- BuybackMultiplierActive(buybackMultiplierLength) (#599)
Apply the check-effects-interactions pattern.
Additional information: link
Shinomics.isOverLiquified(uint256,uint256) (#733-735) uses timestamp for comparisons
Dangerous comparisons:
- getLiquidityBacking(accuracy) > target (#734)
Avoid relying on block.timestamp.
Additional information: link
DividendDistributor.process(uint256) (#290-314) has costly operations inside a loop:
- currentIndex ++ (#311)
Use a local variable to hold the loop computation result.
Additional information: link
Shinomics.swapThreshold (#422) is set pre-construction with a non-constant function or state variable:
- _totalSupply / 200
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
solc-0.8.7 is not recommended for deployment
Deploy with any of the following Solidity versions: 0.5.16 - 0.5.17, 0.6.11 - 0.6.12, 0.7.5 - 0.7.6 Use a simple pragma version that allows any of these versions. Consider using the latest version of Solidity for testing.
Additional information: link
Low level call in Shinomics.swapBack() (#546-585):
- (success) = address(marketingFeeReceiver).call{gas: 30000,value: amountBNBMarketing}() (#571)
Avoid low-level calls. Check the call success. If the call is meant for a contract, check for code existence
Additional information: link
Variable Shinomics._allowances (#381) is not in mixedCase
Follow the Solidity naming convention.
Additional information: link
Variable IDEXRouter.addLiquidity(address,address,uint256,uint256,uint256,uint256,address,uint256).amountADesired (#151) is too similar to IDEXRouter.addLiquidity(address,address,uint256,uint256,uint256,uint256,address,uint256).amountBDesired (#152)
Prevent variables from having similar names.
Additional information: link
Shinomics.slitherConstructorVariables() (#365-741) uses literals with too many digits:
- distributorGas = 500000 (#419)
Use: Ether suffix, Time suffix, or The scientific notation
Additional information: link
Shinomics.SHIB (#368) is never used in Shinomics (#365-741)
Remove unused state variables.
Additional information: link
Shinomics._totalSupply (#377) should be constant
Add the constant attributes to state variables that never change.
Additional information: link
getUnpaidEarnings(address) should be declared external:
- Shinomics.getUnpaidEarnings(address) (#716-718)
Use the external attribute for functions never called from the contract.
Additional information: link
Average PancakeSwap trading volume, liqudity, number of swaps are extremely low. Token seems to be dead.
Number of Binance Smart Chain (BSC) token holders is low.
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.
BscScan page for the token does not contain additional info: website, socials, description, etc.
Additional information: link
Young tokens have high risks of price dump / death
Young tokens have high risks of scam / price dump / death
Young tokens have high risks of scam / price dump / death
Young tokens have high risks of price dump / death
Token has relatively low CoinGecko rank
Token has relatively low CoinMarketCap rank
Price for Shin
LASER DESK beta
Twitter account link seems to be invalid
Unable to find Blog account (Reddit or Medium)
Unable to find Youtube account
Unable to find Discord account