BNBFactory Audit By Codeum

  • 0
  • January 10, 2022

audit Description

Disclaimer: This report does not indicate the participation of codeum in the project. The report only applies to the contract address mentioned and is meant to be used only for the specified project.
Email: [email protected]

Overal contract details:

The way this works is that you put some BNB and that hire a specific number of virtual workers (number of eggs)/EGGS_TO_HATCH_1MINERS. Here EGGS_TO_HATCH_1MINERS is a uint256 constant set at the top of the contract:

contract BNBFactory {
using SafeMath for uint256;

/** base parameters **/
uint256 public EGGS_TO_HIRE_1MINERS = 1080000;
uint256 public EGGS_TO_HIRE_1MINERS_COMPOUND = 864000;

In the code above, EGGS_TO_HATCH_1MINERS has a value of 1080000. So, in this miner, the number of eggs you receive from say 1 BNB is immediately converted to workers by dividing the number of eggs by 1080000.

Each worker will produce 1 new egg per second. There are 86400 seconds per day, so the number of new eggs in your cart at the end of a day =(number of miners)*(86400).

So basic daily ROI is 86400/1080000= 0.08

Other variables in the contract start at below basic parameters:

Basic ROI is 8% per day it is calculated by eggs(miners) so it could be less depending on the total eggs(workers) and contract balance.

Basic Referral is 10% which is calculated by eggs(miners) so it could be less.

The compound bonus is 3% per day up to 10 days.

1% of each deposit or compound is going to the lottery pot. For every 0.005 BNB deposit or compound, the user will automatically be given 1 ticket to the current lottery, up to 50 tickets max per user.  The lottery will randomly choose the winner every 24 hours or when reach 100 users. 90% of the lottery pot will be added to the users balance.
 /** whale control features **/
uint256 public CUTOFF_STEP = 24 * 60 * 60; /** 24 hours **/
uint256 public MIN_INVEST = 5 * 1e15; /** 0.005 BNB **/
uint256 public WITHDRAW_COOLDOWN = 4 * 60 * 60; /** 4 hours **/
uint256 public WITHDRAW_LIMIT = 10 ether; /** 10 BNB **/
uint256 public WALLET_DEPOSIT_LIMIT = 200 ether; /** 200 BNB **/

The minimum deposit to play the game is 0.005 BNB and the maximum deposit is 200BNB every 24 hours users can decide to either compound or withdraw.  Users can withdraw every 4 hours and the limit for withdrawal every 4 hours is 10 BNB.

The owner fee is total 8% (PARTNER 3% – PROJECT 4% – PROJECT_SELL 0.5% -MARKETING_SELL 0.5%).

NOTE: The system used is called ROI and it is considered HIGH-RISK. The system will pay dividends from deposits of other users. Users can get dividends and referral commission. Do always invest with proper knowledge and investigation.

Write Contract on BSCScan is designed to assist users in interacting with any smart contract deployed onto the BSC. The function and nature of the smart contract are defined by the developers of the smart contract respectively.

 

Write Contract:

1.buyEGGS: Deposit(Buy EGGS) in the contract

Usage: Depositing(buying eggs) into the smart contract

Who can use this function: Everybody

2.chooseWinner: Choosing the lottery winner

Usage: This function will be used to choose the lottery winner.

Who can use this function: Owner

3.hatchEggs: Compound Eggs

Usage: Using this function user can use his/her withdrawable amount to buy eggs.

Who can use this function: Users who bought eggs/ Refferer user

4.sellEggs: Selling eggs

Usage: Withdraw profit

Who can use this function: Only players( deposited wallets)

 

*In the website

Buying Eggs= Hire workers

Hatch Eggs= Compound

Selling Eggs = Withdraw

 

 

 

CRITICAL ISSUES (critical, high severity): 0

Bugs and vulnerabilities that enable theft of funds, lock access to funds without possibility to restore it, or lead to any other loss of funds to be transferred to any party; high priority unacceptable bugs for deployment at mainnet; critical warnings for owners, customers or investors.

ERRORS AND BUGS (medium, low severity): 0

Bugs that can trigger a contract failure, with further recovery only possible through manual modification of the contract state or contract replacement altogether; lack of necessary security precautions; other warnings.

OPTIMIZATION POSSIBILITIES (very low severity): 0

Possibilities to decrease cost of transactions and data storage of Smart-Contracts.

NOTES AND RECOMMENDATIONS (very low severity): 0

Tips and tricks, all other issues and recommendations, as well as errors that do not affect the functionality of the Smart-Contract.

 

Conclusion:

In the BNBfactory.org Smart-Contract were found no vulnerabilities and no backdoors. The code was manually reviewed for all commonly known and more specific vulnerabilities.