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 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.
Owner privileges
- withdraw
- ERC20 tokens
- When the contract has native tokens, the owner can pass the own contract address to the withdraw function to get native tokens
- BNB
- ERC20 tokens
- update
- autobuyTrigger
- autoTransferTrigger
- autoSellTrigger
- buyFee
- below/equal 20%
- sellFee
- below/equal 20%
- transferFee
- below/equal 20%
- isLiquidityPool
- isFeeExempt
- swapper
- Launch
- only once
- Any address can sell for other recipients with his balance
- When someone sends native Tokens to the contract directly, the whole address balance will be sent as payable funds to the swapper.buy function with the user who sent the funds as "user" parameter.
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
/
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
In the "buyFor" and the "receive" function, there is no zero/dead address check. This causes, that the funds will be sent to that address and the funds will be lost.
Pending
#2 low Issue
Dead address check
Check also the dead address. Otherwise, if the feeDestination equals the dead address, it is also a valid recipient. The fees will be lost then.
Pending
#3 low Issue
Recipients should be contract addresses
It is recommended to add a "contract" check while updating the fee recipients. Recipients are used in the transfer function and if the trigger is set the IFeeReceiver.trigger function will be called. It will cause a revert when one of the addresses is an EOA.
optimization Issues | 2 findings
Pending
#1 optimization Issue
Naming convention
Private and Internal variables should be started with an underscore. It is recommended to add an underscore to the variables at the beginning. Please make sure to change the variable everywhere else if you change the variable.
Pending
#2 optimization Issue
Add event parameter
Users are able to sell for other recipients. It would be best to add also the recipient to the Transfer event to see who the recipient is. This appears also to the "buyFor" function.
informational Issues | 2 findings
Pending
#1 informational Issue
Exemption revert
While updating the recipients for the transfer fee, buy fee, and sell fee, the addresses are exempted from the fees. The previous address will still be exempted after updating. Including the last address back into the fees while updating the address is recommended.
Pending
#2 informational Issue
Remove Safemath library
SafeMath is unnecessary when the pragma version is above 0.8.x because it handles overflow and underflow by default. Replace all library functions with raw mathematical operations.