tEXO is the platform governance token that allows token holders to vote on proposals and approve new asset listings on ExoniumDEX. After initial equitable distribution of tEXO via a seed staking pool, tEXO will be the yield token to incentivise liquidity providers on ExoniumDEX. tEXO holders will be entitled to fees accrued on the platform for all the services provided. tEXO will also be one of the key collateral for tDollar - ExoniumDEX’s stable coin.
tEXO will conceptually derive its market value based on market forces and ecosystem size.
ExoniumDEX aims for tEXO fair distribution to a community with vested interest in the long term goals and success of ExoniumDEX.
After mainnet launch of Exonium, tEXO holders would qualify for a share of additional transactional fees of swapping within ExoniumDEX as well as fees resulting from the usage of the ExoniumDEX satellite network inclusive of ExoniumBridge and ExoniumOracles.
Use-cases for tEXO -
Governance on platform's development and new implementation
Collateral for tDOLLAR - Platform's native stablecoin
Yield reward
Performance fee sharing to tEXO token holders from ExoniumDEX services offered in the present and future (not limited to) -
1) Synthetic Assets
2) Decentralised Exchange (AMM)
3) Yield Optimiser
4) Non-native farming
5) Airdrop new partner tokens
6) EXO-Launch
7) ExoniumBridge
8) ExoniumOracles
Currently, $tEXO does not have a maximum supply due to the need for a wide distribution of tokens to accommodate for utility within the range of DeFi product suites planned within the upcoming development roadmap.
Multiple deflationary mechanism plans are in place to reduce supply and to maintain constant upwards price pressure:
Buyback & Burn
Taxation
Further deflationary mechanics to be introduced for $tEXO ecosystem to become deflationary
Unable to verify that contract auditor is trusted: Certik, Quantstamp, Hacken, Solidity, Paladinsec, Openzeppelin, Verichains
TEXOToken._writeCheckpoint(address,uint32,uint256,uint256) (TEXOToken.sol#223-241) uses a dangerous strict equality:
- nCheckpoints > 0 && checkpoints[delegatee][nCheckpoints - 1].fromBlock == blockNumber (TEXOToken.sol#233)
Don't use strict equality to determine if an account has enough Ether or tokens.
Additional information: link
Pragma version>=0.4.0 (SafeMath.sol#3) allows old versions
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
BEP20._approve(address,address,uint256).owner (BEP20.sol#296) shadows:
- Ownable.owner() (Ownable.sol#36-38) (function)
Rename the local variables that shadow another component.
Additional information: link
TEXOToken.delegateBySig(address,uint256,uint256,uint8,bytes32,bytes32) (TEXOToken.sol#89-130) uses timestamp for comparisons
Dangerous comparisons:
- require(bool,string)(now <= expiry,TEXO::delegateBySig: signature expired) (TEXOToken.sol#128)
Avoid relying on block.timestamp.
Additional information: link
TEXOToken.getChainId() (TEXOToken.sol#248-252) uses assembly
- INLINE ASM (TEXOToken.sol#250)
Do not use evm assembly.
Additional information: link
Different versions of Solidity is used:
- Version used: ['0.6.12', '>=0.4.0', '^0.6.0', '^0.6.2']
- ^0.6.2 (Address.sol#3)
- >=0.4.0 (BEP20.sol#3)
- >=0.4.0 (Context.sol#3)
- >=0.4.0 (IBEP20.sol#3)
- >=0.4.0 (Ownable.sol#3)
- ^0.6.0 (SafeBEP20.sol#3)
- >=0.4.0 (SafeMath.sol#3)
- 0.6.12 (TEXOToken.sol#7)
Use one Solidity version.
Additional information: link
SafeMath.sqrt(uint256) (SafeMath.sol#177-188) is never used and should be removed
Remove unused functions.
Additional information: link
Low level call in Address._functionCallWithValue(address,bytes,uint256,string) (Address.sol#134-160):
- (success,returndata) = target.call{value: weiValue}(data) (Address.sol#143)
Avoid low-level calls. Check the call success. If the call is meant for a contract, check for code existence
Additional information: link
Variable TEXOToken._delegates (TEXOToken.sol#31) is not in mixedCase
Follow the Solidity naming convention.
Additional information: link
Redundant expression "this (Context.sol#25)" inContext (Context.sol#15-29)
Remove redundant statements if they congest code but offer no value.
Additional information: link
mint(address,uint256) should be declared external:
- TEXOToken.mint(address,uint256) (TEXOToken.sol#19-22)
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
Unable to find token on CoinGecko
Additional information: link
Unable to find token on CoinMarketCap
Additional information: link
Unable to verify that token and website are owned by the same team (no listings + unable to find contract on website)
Unable to verify token contract address on the website
Unable to find token on CoinHunt
Additional information: link
Unable to find code repository for the project
Young tokens have high risks of scam / price dump / death
Token has no active CoinGecko listing / rank
Token has no active CoinMarketCap listing / rank
Token has a considerable age, but social accounts / website are missing or have few users
Token has a considerable age, but average PancakeSwap 30d trading volume is low
Young tokens have high risks of price dump / death
Twitter account link seems to be invalid
Telegram account has relatively few subscribers
Unable to find Youtube account
Unable to find Discord account