Stasis Info
Stasis Network is an on-chain mutual fund, with a deflationary token as its medium of exchange. This yield-bearing treasury will supercharge automated and customizable passive income for users.
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 can set high fees
Contract owner is able to set fees above 25%. Very high fees can also prevent token transfer.
Token transfer can be locked
Owner can lock user funds with owner functions.
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.
Owner privileges
- The owner can
- update
- Fees up to 100%
- in summary, the treasury, staking, and yield fees can be set up to 100%. Not all of them at the same time 100%.
- Treasury, staking, and yield address
- Minimum trigger amount
- Fees up to 100%
- withdraw
- native tokens
- ERC20 tokens
- update
- The trigger function will not work when any treasury, staking, or yield address is set to zero/dead address. This can restrict the functionality of the contract and lock to call the trigger function.
- This contract is similar to the "BuyReceiver" contract of the project.
Note - This Audit report consists of a security analysis of the Stasis 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 Stasis team, other contracts associated with the project were not audited by our team. We recommend investors to do their own research before investing.
Files and details
Functions
public
/
State variables
public
/
Total lines
of code
/
Capabilities
Hover on items
/
Functions
public
/
State variables
public
/
Total lines
of code
/
Capabilities
Hover on items
/
Findings and Audit result
low Issues | 3 findings
Pending
#1 low Issue
Missing zero/dead address check
Check whether the token address is zero/dead address or not. Otherwise, the owner has to create a new BuyReceiver contract because he cannot update the token address after deploying.
Pending
#2 low Issue
Check balance before calling the trigger function
Consider checking the balance before calling the "depositRewards" functions in the trigger function because the owner can set the percentage to 100% in sum for staking, treasury, and yield address. For example, the treasury can be set to 100% while the other two addresses are set to 0. That means the contract should not call the deposit function when the amount is 0.
Pending
#3 low Issue
Emit events
It is recommended to emit an event after updating a variable or withdrawing token/native tokens.
optimization Issues | 1 findings
Pending
#1 optimization Issue
Type
Adjust the "uint" type to the "uint256" type.
informational Issues | 2 findings
Pending
#1 informational Issue
Comment
Adjust the comment to Stasis instead of MDB.
Pending
#2 informational Issue
Require Error message is missing
Please provide an error message to the "require" statement to notify the caller what happened, if an error occurred.