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.

Stasis Logo

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.

0.93
Poor Excellent

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

Select the audit
Static Analysis Dynamic Analysis Symbolic Execution SWC Check Manual Review
Contract address
0xDb49...ABCc
Network
BNB Smart Chain - Testnet
License N/A
Compiler N/A
Type N/A
Language Solidity
Onboard date 2023/06/01
Revision date In progress

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.

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:

  1. Specification Review: Analyze the provided specifications, source code, and instructions to fully understand the smart contract's size, scope, and functionality.
  2. Manual Code Examination: Conduct a thorough line-by-line review of the source code to identify potential vulnerabilities and areas for improvement.
  3. Specification Alignment: Ensure that the code accurately implements the provided specifications and intended functionalities.
  4. Test Coverage Assessment: Evaluate the extent and effectiveness of test cases in covering the codebase, identifying any gaps in testing.
  5. Symbolic Execution: Analyze the smart contract to determine how various inputs affect execution paths, identifying potential edge cases and vulnerabilities.
  6. Best Practices Evaluation: Assess the smart contracts against established industry and academic best practices to enhance efficiency, maintainability, and security.
  7. 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.


This contract is similar to the StasisFarm contract of the project.

Owner privileges

  • update
    • currentMultiClaimHolerIndex to 0
    • set min pending rewards for auto claim as high as he wants
    • set staking fee
      • up to 50%
    • set reflect fee
      • up to 50%
    • set inelligibleClaimsCheck
      • without any limitation
    • customized rewards address
    • min holdings for autoclaim
  • withdraw
    • foreign token
    • native tokens
  • The transfer and the "transferFrom" function are the same. Also, the "claimRewards" function is similar to those.

 

  • The owner has the same privileges as in the staking contract. Additionally, to those privileges, he is able to
    • update
      • feeRecipient
      • isFeeExempt
    • roll over dust into rewards (STS)
      • swapping STSPlus tokens to reward tokens and sending them to the contract itself and adding the difference of the rewards (After - before) to everyone's pending rewards

TaxlessWithdrawContract privileges

  • Can withdraw the tokens for an arbitrary address

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

/

Findings and Audit result

low Issues | 2 findings

Pending

#1 low Issue
Missing zero/dead address validation
STSMATICFARM.sol
L577
Description

Checking the address dead address is also recommended.

Pending

#2 low Issue
Emit events
-
Description

Emitting events for updating variables, depositing, claiming, staking, etc., is recommended.

optimization Issues | 1 findings

Pending

#1 optimization Issue
Type
STSMATICFARM.sol
L662
L725
L728-729
L744
L801
L853
L855
Description

Adjust the "uint" type to "uint256"