Beetchez Info
BEETCHEZ are revolutionizing traditional crypto space with its real-life bee conservation utility and a ridiculous narrative that holds unlimited meme potential. Those who decide to BEETCH aren’t joining yet another brain dead meme community... The more we BEETCH together, the more bees we save!
Team and KYC Verification
The team has securely submitted their personal information to SolidProof.io for verification.
In the event of any fraudulent activities, this information will be promptly reported to the relevant authorities to ensure accountability and compliance.
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.
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.
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 can be burned
There is a function to burn tokens in the contract without any allowances.
Ownership is not renounced
Contract can be manipulated by owner functions.
Contract is not upgradeable
The contract does not use proxy patterns or other mechanisms to allow future upgrades. Its behavior is locked in its current state.
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:
- Specification Review: Analyze the provided specifications, source code, and instructions to fully understand the smart contract's size, scope, and functionality.
- Manual Code Examination: Conduct a thorough line-by-line review of the source code to identify potential vulnerabilities and areas for improvement.
- Specification Alignment: Ensure that the code accurately implements the provided specifications and intended functionalities.
- Test Coverage Assessment: Evaluate the extent and effectiveness of test cases in covering the codebase, identifying any gaps in testing.
- Symbolic Execution: Analyze the smart contract to determine how various inputs affect execution paths, identifying potential edge cases and vulnerabilities.
- Best Practices Evaluation: Assess the smart contracts against established industry and academic best practices to enhance efficiency, maintainability, and security.
- 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 owner can set the governor's contract address only once.
- The owner can update the governance funds address.
- The owner can burn tokens from the governance fund address.
- The owner can transfer the tokens from the governance fund address to the donation address.
- The owner can set the transfer fees to not more than 5%.
- The owner can toggle the fee setting.
- The owner can whitelist wallets from fees.
Note - This Audit report consists of a security analysis of the Beetchez token smart contract. This analysis did not include functional testing (or unit testing) of the contract’s logic. Moreover, we only the mentioned contract for the Beetchez 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
high Issues | 2 findings
Acknowledged
#1 high Issue
Burning of tokens without any allowance.
The function as written allows the governor to burn tokens directly from the address stored in the governanceFund state variable without needing any allowance. This means that if the owner (who controls setGovernanceFund) changes the governanceFund to any arbitrary address—even one that holds tokens belonging to a user—the governor can subsequently call burnFromGovernanceFund to burn tokens from that address without the token holder’s consent. This behavior effectively gives the owner (or a colluding governor) the power to unilaterally burn tokens from any address by first setting that address as the governance fund. If this is not the intended behavior, you may want to consider implementing additional checks or making the governanceFund address immutable once set, to prevent any misuse of the burning functionality.
Acknowledged
#2 high Issue
Owner can transfer tokens without any allowance.
The donateFromGovernanceFund function transfers tokens from the address stored in the governanceFund variable without verifying ownership or requiring allowance. Since the owner can change the governanceFund address arbitrarily via the setGovernanceFund function, a malicious or careless change could set this variable to a user’s address. Once that happens, the governor could call donateFromGovernanceFund and transfer tokens from that user’s account to a donation address without the user’s consent. If the intent is to restrict operations to a dedicated governance fund, you might consider making the governanceFund address immutable once it’s set or adding additional checks to prevent misuse.
medium Issues | 1 findings
Resolved
#1 medium Issue
Missing 'isContract' check.
The contract lacks a validation check to ensure that specific parameters are contract addresses. Without this check, there is a risk that non-contract addresses (such as externally owned accounts, or EOAs) could be mistakenly set for parameters intended to reference other contracts. This could lead to failures in executing critical interactions within the contract, as EOAs do not support contract-specific functions. To mitigate this, Implement a validation check to ensure that parameters designated as contract addresses are verified as such. This can be done using Solidity’s Address library function isContract, which checks if an address has associated contract code.
low Issues | 1 findings
Acknowledged
#1 low Issue
Floating pragma solidity version
Adding the constant version of solidity is recommended, as this prevents the unintentional deployment of a contract with an outdated compiler that contains unresolved bugs.