Baby Pancake – BSC


Total Supply – 100,000,000,000

Contract Link –

Compiler version – v0.6.12+commit.27d51765

Optimization Enabled – Yes, 200 runs

Start block – 9552060

Contract deployer’s address – 0x099a6605557a0670d0ed74602f7365b7430d1a76

Marketing wallet – 0x087087D8D9210A7e92181f7eb9d0994A0eC6cD6A

Security Issues:

High severity: None

Medium severity:

Any address could be stopped from making transactions through function blacklistAddress. Team specificed this was to prevent and stop snipers.

Low severity:

Marketing fees could be adjusted by developers at any moment through function setMarketingFee. Developer is immune to chese changes through function function excludeFromFees.


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

19. 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 Baby Pancake smart contract? Why this contract over any other?

The Smart Contract we chose for our project had the best functions in terms of holders rewards, manageability and upscaling we could have. We also implemented a max wallet function to have a fair distribution upon launch.

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

We think that renouncing ownership would cut our own legs in terms of future plans.
Here’s a list of things that we wouldn’t be able to do after renouncing:
-Adjust fees and change reward amounts if the community asks for it.
-Whitelist future Exchange Hot wallets.
-Reduce claiming time for rewards (always, listening to the community).
-Any fixes or minor changes that might be needed after the Audits.
-Prove to listing partners such as Coinmarketcap the ownership of the whole project.

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

We’ve been in the DeFi world for quite sometime, learning from others and doing our research in the meantime. We wanted to give to people like us who struggled to find a decent Project, something to trust and believe in, and we are fully committed to make it happen!

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

We as core members kept a minimal share of tokens (3% split in 6 people), then we reserved an unlocked 1.5% in case we need to supply liquidity to exchanges, and lastly we locked another 1.5% as team tokens (on Team.Finance ), to make sure the whole team is as dedicated as possible to move forward and keep working hard! We wrote all of this on our website FAQ’s for full transparency before launch!

Hope this answered your questions! 



Baby Pancake – BSC


Please send us any questions or concerns whatsoever.