VANITY Token Logo

VNY [VANITY] Token

About VNY

Listings

Token 16 months
CoinMarketCap 18 months
[CoinGecko] alert: Vanity migrated to new token address. For more information, please read https://twitter.com/vanitytoken/status/1417841090565136389.
white paper

Vanity is a token that is intended to fully revolutionize the current system with boring old wallet addresses. How do Vanity intend to do this? The team is able to generate custom addresses based on your own preference utilizing GPU Hash Calculation Power to get a match with your request. Keep in mind this project requires high calculation power, so in order to make it a stable service, the team has already purchased GPU Servers being able to hold the upcoming requests!
Vanity Token was born to take place in the BSC Network, aiming to change repetitive copy-paste meme tokens. The idea of the project is providing a Marketplace for custom addresses based on Vanity Token, which will be the only payment method for the service.

The user will generate a Private and a public key, using one of Vanity’s tools (Disconnected from the internet). Now the user needs to keep this private key to themselves, and send us the Public key. This is a key that cannot grant anyone access to your wallet, only the private key is able to do this. Now when the team has the public key, they can generate any custom address you want. The team will send you back the generated hash, and combined with your private key, those can be merged in your desired address, making you the sole holder of the private key as well.

Laser Scorebeta Last Audit: 30 November 2021

report
Token seems to be (relatively) fine. It still become a scam, but probability is moderate.

VANITY.addLiquidity(uint256,uint256) (#1165-1178) sends eth to arbitrary user
Dangerous calls:
- uniswapV2Router.addLiquidityETH{value: ethAmount}(address(this),tokenAmount,0,0,owner(),block.timestamp) (#1170-1177)
Ensure that an arbitrary user cannot withdraw unauthorized funds.

Additional information: link

Reentrancy in VANITY._transfer(address,address,uint256) (#1077-1122):
External calls:
- swapAndLiquify(contractTokenBalance) (#1109)
- uniswapV2Router.addLiquidityETH{value: ethAmount}(address(this),tokenAmount,0,0,owner(),block.timestamp) (#1170-1177)
- uniswapV2Router.swapExactTokensForETHSupportingFeeOnTransferTokens(tokenAmount,0,path,address(this),block.timestamp) (#1156-1162)
External calls sending eth:
- swapAndLiquify(contractTokenBalance) (#1109)
- uniswapV2Router.addLiquidityETH{value: ethAmount}(address(this),tokenAmount,0,0,owner(),block.timestamp) (#1170-1177)
State variables written after the call(s):
- _tokenTransfer(from,to,amount,takeFee) (#1121)
- _rOwned[address(this)] = _rOwned[address(this)].add(rLiquidity) (#992)
- _rOwned[MarketingWallet] = _rOwned[MarketingWallet].add(rWallet) (#1013)
- _rOwned[sender] = _rOwned[sender].sub(rAmount) (#1202)
- _rOwned[sender] = _rOwned[sender].sub(rAmount) (#1216)
- _rOwned[recipient] = _rOwned[recipient].add(rTransferAmount) (#1203)
- _rOwned[sender] = _rOwned[sender].sub(rAmount) (#1232)
- _rOwned[sender] = _rOwned[sender].sub(rAmount) (#1247)
- _rOwned[recipient] = _rOwned[recipient].add(rTransferAmount) (#1218)
- _rOwned[recipient] = _rOwned[recipient].add(rTransferAmount) (#1233)
- _rOwned[recipient] = _rOwned[recipient].add(rTransferAmount) (#1249)
- _rOwned[Dead] = _rOwned[Dead].add(rburn) (#1016)
- _tokenTransfer(from,to,amount,takeFee) (#1121)
- _rTotal = _rTotal.sub(rFee) (#945)
- _tokenTransfer(from,to,amount,takeFee) (#1121)
- _tOwned[address(this)] = _tOwned[address(this)].add(tLiquidity) (#994)
- _tOwned[sender] = _tOwned[sender].sub(tAmount) (#1231)
- _tOwned[sender] = _tOwned[sender].sub(tAmount) (#1246)
- _tOwned[recipient] = _tOwned[recipient].add(tTransferAmount) (#1217)
- _tOwned[MarketingWallet] = _tOwned[MarketingWallet].add(walletA) (#1015)
- _tOwned[recipient] = _tOwned[recipient].add(tTransferAmount) (#1248)
- _tOwned[Dead] = _tOwned[Dead].add(burnA) (#1018)
Apply the check-effects-interactions pattern.

Additional information: link


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.

Reentrancy in VANITY.transferFrom(address,address,uint256) (#817-821):
External calls:
- _transfer(sender,recipient,amount) (#818)
- uniswapV2Router.addLiquidityETH{value: ethAmount}(address(this),tokenAmount,0,0,owner(),block.timestamp) (#1170-1177)
- uniswapV2Router.swapExactTokensForETHSupportingFeeOnTransferTokens(tokenAmount,0,path,address(this),block.timestamp) (#1156-1162)
External calls sending eth:
- _transfer(sender,recipient,amount) (#818)
- uniswapV2Router.addLiquidityETH{value: ethAmount}(address(this),tokenAmount,0,0,owner(),block.timestamp) (#1170-1177)
State variables written after the call(s):
- _approve(sender,_msgSender(),_allowances[sender][_msgSender()].sub(amount,BEP20: transfer amount exceeds allowance)) (#819)
- _allowances[owner][spender] = amount (#1073)
Apply the check-effects-interactions pattern.

Additional information: link

VANITY._Wallet(uint256) (#1004-1022) performs a multiplication on the result of a division:
-burnA = (wallet.mul(burn)).div(100) (#1011)
-rburn = burnA.mul(currentRate) (#1012)
Consider ordering multiplication before division.

Additional information: link

VANITY.addLiquidity(uint256,uint256) (#1165-1178) ignores return value by uniswapV2Router.addLiquidityETH{value: ethAmount}(address(this),tokenAmount,0,0,owner(),block.timestamp) (#1170-1177)
Ensure that all the return values of the function calls are used.

Additional information: link

VANITY._approve(address,address,uint256).owner (#1069) shadows:
- Ownable.owner() (#434-436) (function)
Rename the local variables that shadow another component.

Additional information: link

VANITY.setMaxTx(uint256) (#934-937) should emit an event for:
- _maxTxAmount = maxTx (#935)
Emit an event for critical parameter changes.

Additional information: link

VANITY.ChangeMarketingWallet(address).MarketingWalletr (#902) lacks a zero-check on :
- MarketingWallet = MarketingWalletr (#903)
Check that the address is not zero.

Additional information: link

Reentrancy in VANITY.transferFrom(address,address,uint256) (#817-821):
External calls:
- _transfer(sender,recipient,amount) (#818)
- uniswapV2Router.addLiquidityETH{value: ethAmount}(address(this),tokenAmount,0,0,owner(),block.timestamp) (#1170-1177)
- uniswapV2Router.swapExactTokensForETHSupportingFeeOnTransferTokens(tokenAmount,0,path,address(this),block.timestamp) (#1156-1162)
External calls sending eth:
- _transfer(sender,recipient,amount) (#818)
- uniswapV2Router.addLiquidityETH{value: ethAmount}(address(this),tokenAmount,0,0,owner(),block.timestamp) (#1170-1177)
Event emitted after the call(s):
- Approval(owner,spender,amount) (#1074)
- _approve(sender,_msgSender(),_allowances[sender][_msgSender()].sub(amount,BEP20: transfer amount exceeds allowance)) (#819)
Apply the check-effects-interactions pattern.

Additional information: link

VANITY._transfer(address,address,uint256) (#1077-1122) uses timestamp for comparisons
Dangerous comparisons:
- require(bool,string)(block.timestamp >= _timestamp[from],One Sell Per-Day Limit) (#1090)
Avoid relying on block.timestamp.

Additional information: link

Address._functionCallWithValue(address,bytes,uint256,string) (#386-407) uses assembly
- INLINE ASM (#399-402)
Do not use evm assembly.

Additional information: link

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

Additional information: link

VANITY._previousLiquidityFee (#737) 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

solc-0.8.2 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 Address._functionCallWithValue(address,bytes,uint256,string) (#386-407):
- (success,returndata) = target.call{value: weiValue}(data) (#390)
Avoid low-level calls. Check the call success. If the call is meant for a contract, check for code existence

Additional information: link

Variable VANITY.Hodl4Sell (#744) is not in mixedCase
Follow the Solidity naming convention.

Additional information: link

Redundant expression "this (#266)" inContext (#260-269)
Remove redundant statements if they congest code but offer no value.

Additional information: link

Variable VANITY._getValues(uint256).rTransferAmount (#951) is too similar to VANITY._getValues(uint256).tTransferAmount (#950)
Prevent variables from having similar names.

Additional information: link

VANITY.slitherConstructorVariables() (#703-1261) uses literals with too many digits:
- Hodl4Sell = 80000000 * 10 ** 9 (#744)
Use: Ether suffix, Time suffix, or The scientific notation

Additional information: link

VANITY._tTotal (#718) should be constant
Add the constant attributes to state variables that never change.

Additional information: link

isExcludedFromFee(address) should be declared external:
- VANITY.isExcludedFromFee(address) (#1065-1067)
Use the external attribute for functions never called from the contract.

Additional information: link

Holders:


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 number of swaps.


Twitter account link seems to be invalid


Unable to find Blog account (Reddit or Medium)


BscScan page for the token does not contain additional info: website, socials, description, etc.

Additional information: link


Unable to find token on CoinHunt

Additional information: link


Young tokens have high risks of scam / price dump / death


Young tokens have high risks of scam / price dump / death


Token has a considerable age, but social accounts / website are missing or have few users


Young tokens have high risks of price dump / death


Token has relatively low CoinGecko rank


Token has relatively low CoinMarketCap rank

Price for VNY