Baked Pizza
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.
Owner privileges
Comments
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.
Audit Scope
This audit covered the following files listed below with a SHA-1 Hash. The above token Team provided us with the files that needs to be tested.
We will verify the following claims:- Correct implementation of Token standard
- Deployer cannot mint any new tokens
- Deployer cannot burn or lock user funds
- Deployer cannot pause the contract
- Overall checkup (Smart Contract Security)
- Review of the specifications, sources, and instructions provided to SolidProof to make sure we understand the size, scope, and functionality of the smart contract.
- Manual review of code, which is the process of reading source code line-by-line in an attempt to identify potential vulnerabilities.
- Comparison to specification, which is the process of checking whether the code does what the specifications, sources, and instructions provided to SolidProof describe.
- Test coverage analysis, which is the process of determining whether the test cases are actually covering the code and how much code is exercised when we run those test cases.
- Symbolic execution, which is analysing a program to determine what inputs causes each part of a program to execute.
- Best practices review, which is a review of the smart contracts to improve efficiency, effectiveness, clarify, maintainability, security, and control based on the established industry and academic practices, recommendations, and research.
- Specific, itemized, actionable recommendations to help you take steps to secure your smart contracts.
A file with a different Hash has been modified, intentionally or otherwise, after the security review. A different Hash could be (but not necessarily) an indication of a changed condition or potential vulnerability that was not within the scope of this review.
Functions
public
14
State variables
public
8
Total lines
of code
142
Capabilities
Hover on items
Audit Details
Throughout the review process, care was taken to evaluate the repository for security-related issues, code quality, and adherence to speciïŹcation and best practices. To do so, reviewed line-by-line by our team of expert pentesters and smart contract developers, documenting any issues as there were discovered.
Risk represents the probability that a certain source-threat will exploit vulnerability, and the impact of that event on the organization or system. Risk Level is computed based on CVSS version 3.0.
low Issues
Pending
#1 Issue
Old Solidity Version
L1
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 Issue
Missing error message
L21
L41
L52
L80
Add a 'require' failed error message.
Pending
#3 Issue
Forced reinvestment
L51-59
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 Issue
Missing SPDX License
L1
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 Issue
Unused amount after substracting.
L51-59
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.
informational Issues
Pending
#1 Issue
Conformity to Solidity naming conventions (naming-convention)
L7
L8
L9
Follow the Solidity [naming convention](https://solidity.readthedocs.io/en/v0.4.25/style-guide.html#naming-conventions).
optimization Issues
Pending
#1 Issue
State variables that could be declared constant (constable-states)
L7
L8
L9
Add the `constant` attributes to state variables that never change.
Pending
#2 Issue
Public function that could be declared external (external-function)
L40-50
L51-59
L72-74
L78-83
L84-86
L87-89
Use the `external` attribute for functions never called from the contract.
Disclaimer
SolidProof.io reports are not, nor should be considered, an âendorsementâ or âdisapprovalâ of any particular project or team. These reports are not, nor should be considered, an indication of the economics or value of any âproductâ or âassetâ created by any team. SolidProof.io do not cover testing or auditing the integration with external contract or services (such as Unicrypt, Uniswap, PancakeSwap etcâ...)
SolidProof.io Audits do not provide any warranty or guarantee regarding the absolute bug- free nature of the technology analyzed, nor do they provide any indication of the technology proprietors. SolidProof Audits should not be used in any way to make decisions around investment or involvement with any particular project. These reports in no way provide investment advice, nor should be leveraged as investment advice of any sort.
SolidProof.io Reports represent an extensive auditing process intending to help our customers increase the quality of their code while reducing the high level of risk presented by cryptographic tokens and blockchain technology. Blockchain technology and cryptographic assets present a high level of ongoing risk. SolidProofâs position is that each company and individual are responsible for their own due diligence and continuous security. SolidProof in no way claims any guarantee of security or functionality of the technology we agree to analyze.