Baked Pizza Info

The Leading DeFi on Binance Smart Chain up to 10% daily return and 15% referral bonus Fully Verified and Audited Contract. Pizza does not have a set price. Higher TVL, more Pizza per BNB. Lower TVL, less Pizza. This creates a level playing field so no user can be late. There is NO calculator available to work this out.

Baked Pizza Logo

TrustNet Score

The TrustNet Score evaluates crypto projects based on audit results, security, KYC verification, and social media presence. This score offers a quick, transparent view of a project's credibility, helping users make informed decisions in the Web3 space.

78.77
PoorExcellent

Real-Time Threat Detection

Real-time threat detection, powered by Cyvers.io, is currently not activated for this project.

This advanced feature provides continuous monitoring and instant alerts to safeguard your assets from potential security threats. Real-time detection enhances your project's security by proactively identifying and mitigating risks. For more information, click here.

TrustNet DataPulse

Loading...
Mobula Logo Data provided by mobula.io. Need data? Get your API.
Loading...

We are presently engaged in detailed discussions with our partners to finalize the arrangements. Information regarding presales will be made available on this platform in the near future. We appreciate your patience and look forward to sharing the upcoming opportunities with you soon!

We are currently in discussions with our partners to finalize the details. Information on token locking and vesting schedules will be provided on this platform soon. We appreciate your patience and look forward to sharing these upcoming opportunities with you shortly.

In the meantime, we’ve already integrated the LP lock overview from UNCX.network. Please visit the CEX/DEX tab for more information.

Security Assessments

Static AnalysisDynamic AnalysisSymbolic ExecutionSWC CheckManual Review
Contract address
0xaEf1...6A38
Network
BNB Smart Chain - Mainnet
License N/A
Compiler N/A
Type N/A
Language Solidity
Onboard date 2023/08/07
Revision date In progress

Summary and Final Words

No crucial issues found

The contract does not contain issues of high or medium criticality. This means that no known vulnerabilities were found in the source code.

Contract owner cannot mint

It is not possible to mint new tokens.

Contract owner cannot blacklist addresses.

It is not possible to lock user funds by blacklisting addresses.

Contract owner cannot set high fees

The fees, if applicable, can be a maximum of 25% or lower. The contract can therefore not be locked. Please take a look in the comment section for more details.

Contract cannot be locked

Owner cannot lock any user funds.

Token cannot be burned

There is no burn function within the contract.

Ownership is not renounced

Contract can be manipulated by owner functions.

Scope of Work

This audit encompasses the evaluation of the files listed below, each verified with a SHA-1 Hash. The team referenced above has provided the necessary files for assessment.

The auditing process consists of the following systematic steps:

  1. Specification Review: Analyze the provided specifications, source code, and instructions to fully understand the smart contract's size, scope, and functionality.
  2. Manual Code Examination: Conduct a thorough line-by-line review of the source code to identify potential vulnerabilities and areas for improvement.
  3. Specification Alignment: Ensure that the code accurately implements the provided specifications and intended functionalities.
  4. Test Coverage Assessment: Evaluate the extent and effectiveness of test cases in covering the codebase, identifying any gaps in testing.
  5. Symbolic Execution: Analyze the smart contract to determine how various inputs affect execution paths, identifying potential edge cases and vulnerabilities.
  6. Best Practices Evaluation: Assess the smart contracts against established industry and academic best practices to enhance efficiency, maintainability, and security.
  7. Actionable Recommendations: Provide detailed, specific, and actionable steps to secure and optimize the smart contracts.

A file with a different Hash has been intentionally or otherwise modified after the security review. A different Hash may indicate a changed condition or potential vulnerability that was not within the scope of this review.

Final Words

The following provides a concise summary of the audit report, accompanied by insightful comments from the auditor. This overview captures the key findings and observations, offering valuable context and clarity.


Ownership Privileges
  • The ceoAddress cannot set the marketEggs value after initiation.
  • The withdrawal and deposit fee is sent to ceoAddress. 
  • The bakePizza function will auto-reinvest some amount of tokens which will be calculated according to the deposit and withdrawal of tokens.

Note - This Audit report consists of a security analysis of the Baked Pizza smart contract. This analysis did not include functional testing (or unit testing) of the contract’s logic. Moreover, we only audited one contract for the Baked Pizza team. Other contracts associated with the project were not audited by our team. We recommend investors do their own research before investing.

Files and details

Functions
public

/

State variables
public

/

Total lines
of code

/

Capabilities
Hover on items

/

Findings and Audit result

low Issues | 5 findings

Pending

#1 low Issue
Old Solidity Version
BakedPizza.sol
L1
Description

When deploying contracts, you should use the latest released version of Solidity. Apart from exceptional cases, only the latest version receives security fixes. Furthermore, breaking changes, as well as new features, are introduced regularly. It is recommended to add the latest solidity version to resolve these issues.

Pending

#2 low Issue
Missing error message
BakedPizza.sol
L21
L41
L52
L80
Description

Add a 'require' failed error message.

Pending

#3 low Issue
Forced reinvestment
BakedPizza.sol
L51-59
Description

Some amount of tokens will be reinvested back without the users permission. In extreme scenarios, if the percentage of re-investment is high then the user will have to reinvest a high amount of tokens which is not recommended.

Pending

#4 low Issue
Missing SPDX License
BakedPizza.sol
L1
Description

There must be a license identifier present in the contract. Add "SPDX-License-Identifier" as SPDX allows the expression of components, licenses, copyrights, security references, and other metadata relating to software.

Pending

#5 low Issue
Unused amount after substracting.
BakedPizza.sol
L51-59
Description

The users have to call the "bakePizza" function with an arbitrary amount of BNB. The deposited amount cannot be withdrawn by the sender. The caller has to call the "eatPizza" over and over again to get the ROI. 5% of the msg.value will be sent to the ceoAddress directly and the rest will be deposited in the contract itself. Also, In the bakePizza function there is a devFee(eggsBought) which will substracted from the eggsBought variable. The devFee(eggsBought) amount will never be used after substraction. Using this value is recommended otherwise, remove the devFee(eggsBought) and use the whole eggsBought.

optimization Issues | 2 findings

Pending

#1 optimization Issue
State variables that could be declared constant (constable-states)
BakedPizza.sol
L7
L8
L9
Description

Add the `constant` attributes to state variables that never change.

Pending

#2 optimization Issue
Public function that could be declared external (external-function)
BakedPizza.sol
L40-50
L51-59
L72-74
L78-83
L84-86
L87-89
Description

Use the `external` attribute for functions never called from the contract.

informational Issues | 1 findings

Pending

#1 informational Issue
Conformity to Solidity naming conventions (naming-convention)
BakedPizza.sol
L7
L8
L9
Description

Follow the Solidity [naming convention](https://solidity.readthedocs.io/en/v0.4.25/style-guide.html#naming-conventions).