BaseHaven Staking Info
BaseHaven is more than just an ecosystem, we’re an ever evolving technological hub dedicated to providing the most advanced and user-friendly DAPPs to the base blockchain. Providing accessibility to all of the top industry defi tools, BaseHaven ecosystem expands into all sectors in defi.
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.
Security Assessments
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 burning within the contract without any allowances
Ownership is not renounced
The owner retains significant control, which could potentially be used to modify key contract parameters.
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 any arbitrary value as the staking and pool fee in the contract
Note - This Audit report consists of a security analysis of the Basehaven smart contract. This analysis did not include functional testing (or unit testing) of the contract’s logic. Moreover, we only audited one token contract for the Basehaven 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
medium Issues | 4 findings
Pending
#1 medium Issue
Missing allowance check.
The contract contains the functionality to stake tokens in the contract, which will be transferred from the user’s wallet to the contract address. However, this function does not contain the functionality to process the token allowance before transferring the tokens to the contract, which is not recommended as without this, the contract cannot transfer the tokens without the tokens allowance.
Pending
#2 medium Issue
Missing ‘Non-reentrant’ check.
The contract does not use a non-reentrancy check in the stake and claim function, which is important as If a non-reentrant modifier is used, it should normally be on all non-view methods. Keep in mind that non-reentrant does not protect the contract system — only each contract individually
Pending
#3 medium Issue
Redundant code
The contract contains the functionality in which the final balance and initial balance will be collected in the amount, but here the amount is not initialized in the contract, and this will change the value of the initial parameter, which is set by the user. Instead, a variable should be added to the contract to process all the calculations so that the initial value will not be changed from the contract.
Pending
#4 medium Issue
The owner can set fees more than 25%.
The contract contains the functionality in which the owner of the contract can set any arbitrary value as the staking and pool fees in the contract which is not recommended as this can fail the transactions in the contract if the amount is set to an excessive number in the contract.
low Issues | 2 findings
Pending
#1 low Issue
Missing visibility.
It is recommended to add the ‘public’, ‘private’, ‘internal’ visibility during the declaration or initialization of a state variable or a mapping in the contract.
Pending
#2 low Issue
Missing events arithmetic.
It is recommended to emit all the critical parameter changes.