SOS Hero

SOS Hero – ETH
Total Supply – 1,000,000,000,000
Contract Link – Compiler version – v0.8.7+commit.e28d00a7
Optimization Enabled – Yes with 200 runs
Start block – 13882795
Contract deployer’s address – 0x36c3981371c7b8c8250ff18b48f47de2a8d7b6b6

High severity:


Medium severity:

The max transaction can be changed by the owner.

Low severity:



This is a fork of Kiba Inu. 

Issue Checking Status:

1. Compiler errors: Passed

2. Race conditions/Reentrancy: Passed

3. Possible delays in data delivery: Passed

4. Front running vulnerability: Passed

5. Timestamp dependence: Passed

6. Integer Overflow and Underflow: Passed

7. DoS with revert: Passed

8. DoS with blocklimit: Passed

9. Methods execution platform: Passed

10. Economy model of smart contract: Passed

11. Impact and exchange rate of logic: Passed

12. Private user data leaks: Passed

13. Malicious event log: Passed

14. Hidden malicious functions: Passed

15. Scoping and declaration: Passed

16. Uninitialized storage pointers: Passed

17. Arithmetic accuracy: Passed

18. Design logic: Passed

19. Cross-fall race conditions: Passed

20. Proper openzeppelin contract implementation and usage: Passed

21. Fallback function safety: Passed

What was the thought process behind the SOS Hero smart contract? Why this contract over any other?

As with nearly every token, our contract is a fork of another token with some adjustments. We value provable safety, tested durability, and simplicity (no functions or fees that unnecessarily increase gas) most of all. In this vein, we decided to fork the Kiba Inu contract, with some slight adjustments. The Kiba Inu contract covers all bases that we value most – namely, ownership can be renounced without problem, there are no functions that have been shown to be problematic, and the gas fees associated with the contract are standard if not below average. The contract also includes an increased fee for first time buyers IF they decide to dump the token within 24 hours of buying, which we found to be an excellent strategy. The adjustments we made were to change the 10% fee used by Kiba (1% reflection 9% marketing) to a 9% fee (2% reflection 7% marketing), and an increased initial transaction cooldown from 30 seconds to 45 seconds. 

Is your team renouncing ownership? Explain why or why not, and how it would be beneficial.

We are renouncing ownership after ensuring that the contract is a problematic and ready to be renounced. We are renouncing as an added showing of safety to our investors, as our contract does have a “setMaxTx” function that technically could be used nefariously. We are a trusted team in the BSC and have proven ourselves to be legitimate, but we value safety & the peace of mind of our investors over all. 

Does your team have experience within the DeFi environment? Are you prepared to run this project diligently?

SOS Hero was created by the DoxedBoyDev team as a branch out from the Binance Smart Chain to the Ethereum Network. The team wanted to explore a new challenge after accomplishing major feats on the BSC, including project listings on CoinMarket- Cap and CoinGecko, materializing a Play-to-Earn game after filling a $200,000 presale, collaborating with every major chain influencer, and providing investors returns up to 1,000X — the best of which boasted a $2,000 market cap to $2,000,000 market cap. We are certainly prepared to run this project diligently, with a phenomenal marketing strategy, global team for 24/7 project oversight, and as much preparation as can be done for a fair launch token like this. 

Please explain your team’s choices in distributing SOS Hero upon launch and how you believe it will be beneficial to the project.

The initial liquidity is 100% provided by the dev, with 100% of the total supply of tokens going to liquidity. We structured our distribution this way in order to preclude any concern about presale dumpers or team/dev tokens. 



SOS Hero – ETH