Solarmine ($SOLAR) is the first bitcoin mining operation that truly rewards its investors, all while reducing our carbon footprint. Solarmine will send 25% of all Bitcoin mined to its holders in the form of BNB each month. 75% of all Bitcoin mined will be used on expansion and expenses to enable Solarmine to have month on month, year on year growth. Solarmine will launch on the Binance Smart Chain (BSC) blockchain network to keep gas fees low and there will be no tax to buy/swap/sell tokens.
Unable to find manual contract audit (e.g. Certik, PeckShield, Solidity...)
Rewards.notifyRewards() (#1169-1197) sends eth to arbitrary user
Dangerous calls:
- (success) = holders[i_scope_0].call{gas: 3000,value: share}() (#1191)
Ensure that an arbitrary user cannot withdraw unauthorized funds.
Additional information: link
Reentrancy in Rewards.processBatch() (#1108-1139):
External calls:
- (success) = _batchHolders[_batchCurrentIndex].call{gas: 3000,value: share}() (#1123-1126)
State variables written after the call(s):
- _batchCurrentIndex ++ (#1116)
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.
Rewards.initiateBatch(uint256).i (#1090) is a local variable never initialized
Initialize all the variables. If a variable is meant to be initialized to zero, explicitly set it to zero to improve code readability.
Additional information: link
SolarmineCoin.constructor(uint256,string,string).symbol (#884) shadows:
- ERC20.symbol() (#223-225) (function)
- IERC20Metadata.symbol() (#123) (function)
Rename the local variables that shadow another component.
Additional information: link
Rewards.constructor(address,address).blacklistAddress (#1062) lacks a zero-check on :
- _blacklisted = blacklistAddress (#1064)
Check that the address is not zero.
Additional information: link
Rewards.notifyRewards() (#1169-1197) has external calls inside a loop: (success) = holders[i_scope_0].call{gas: 3000,value: share}() (#1191)
Favor pull over push strategy for external calls.
Additional information: link
Reentrancy in Rewards.processBatch() (#1108-1139):
External calls:
- (success) = _batchHolders[_batchCurrentIndex].call{gas: 3000,value: share}() (#1123-1126)
Event emitted after the call(s):
- ReceiverRefusedReward(_batchHolders[_batchCurrentIndex]) (#1128-1130)
Apply the check-effects-interactions pattern.
Additional information: link
EnumerableSet.values(EnumerableSet.UintSet) (#857-866) uses assembly
- INLINE ASM (#861-863)
Do not use evm assembly.
Additional information: link
Rewards.processBatch() (#1108-1139) has costly operations inside a loop:
- _batchCurrentIndex ++ (#1116)
Use a local variable to hold the loop computation result.
Additional information: link
EnumerableSet.values(EnumerableSet.UintSet) (#857-866) is never used and should be removed
Remove unused functions.
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 Rewards.notifyRewards() (#1169-1197):
- (success) = holders[i_scope_0].call{gas: 3000,value: share}() (#1191)
Avoid low-level calls. Check the call success. If the call is meant for a contract, check for code existence
Additional information: link
Variable Rewards._batchCurrentIndex (#1057) is not in mixedCase
Follow the Solidity naming convention.
Additional information: link
Redundant expression "success (#1163)" inRewards (#1047-1199)
Remove redundant statements if they congest code but offer no value.
Additional information: link
notifyRewards() should be declared external:
- Rewards.notifyRewards() (#1169-1197)
Use the external attribute for functions never called from the contract.
Additional information: link
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.
Unable to crawl data from the website
BscScan page for the token does not contain additional info: website, socials, description, etc.
Additional information: link
Token was delisted from CoinGecko
Additional information: link
Unable to find token/project description on the website or on BscScan, CoinMarketCap
Unable to find token contract audit
Unable to verify token contract address on the website
Unable to find audit link on the website
Unable to find whitepaper link on the website
Unable to find Telegram link on the website
Unable to find Twitter link on the website
Unable to find token on CoinHunt
Additional information: link
Young tokens have high risks of price dump / death
Token has no active CoinGecko listing / rank
Young tokens have high risks of price dump / death
Token has relatively low CoinMarketCap rank
Telegram account link seems to be invalid
Twitter account link seems to be invalid
Unable to find Youtube account