Lucky Cat – BSC
Contract Link –https://bscscan.com/address/0xb50e74A6b82F59c4058b5D798E3D9C9D9B8c6e16#code
Compiler version – v0.8.9+commit.e5eed63a
Optimization Enabled – No with 200 runs
Start block – 16782143
Contract deployer’s address – 0xdf0833c041db53856380cf1e64cd6428a9e41d3d
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 Lucky Cat smart contract? Why this contract over any other?
We wanted to make a fork of baked beans with low fees with multi chain and multi token support.
Is your team renouncing ownership? Explain why or why not, and how it would be beneficial.
Renouncing ownership is not required because there are no functions specifically for the owner.
Does your team have experience within the DeFi environment? Are you prepared to run this project diligently?
The LuckyCat team has over a year of experience in running DeFi projects. We are fully prepared to support LuckyCat across 6 chains.
Lucky Cat – BSC