- Home
- Security Audits
- Risedle
Web3 · Smart Contract Audit
Risedle Security Audit
softstack completed a smart contract audit of Risedle's Leverage Protocol in February 2022, reporting 8 findings (1 medium, 4 low and 3 informational). The full report is published in the softstack public audit archive.
Key facts
- Client
- Risedle
- Completed
- Chains
- Ethereum
- Languages
- Solidity
- Commit
cab10fbeb9af
About the project
Risedle was a leveraged token protocol for Ethereum and other EVM-compatible chains. It let holders take leveraged exposure to ERC-20 assets through tokens that managed the underlying position, rather than requiring manual collateral management. The risedle.com domain now redirects to an unrelated site and the protocol appears to be discontinued.
Scope
Source repositorygithub.com/risedle/etfsComponents reviewed
3 modules · 3 files- RisedleVault.sol
- RiseTokenVault.sol
- RisedleTokenVault.sol
Findings
0 of 8 findings resolved before the final report.
| ID | Title | Severity | Status |
|---|---|---|---|
5.1.1 | Overpowered Owner rights Code Snippet Result/Recommendation Owners can perform privileged activities like minting and burning tokens. The auditor has not recognized any multi- sig structure. NA It is recommended to use multisig for owner privileges. | Medium | acknowledged |
5.1.2 | Use arrays for gas efficiency Code Snippet Result/Recommendation A function with many arguments can be less efficient. Line 61 function create( bool isETH, // True if the collateral is ETH address tokenRiseAddress, // ERC20 token address that only RiseTokenVault can… | Low | acknowledged |
5.1.3 | Variables that can be made constant Code Snippet Result/Recommendation In the current implementation several variables already declared and initialized can be made constant with UPPER_CASE_UNDERSCOR E naming convention. | Low | acknowledged |
5.1.4 | Public functions should be declared as external Code Snippet Result/Recommendation In the current implementation several functions are declared as public where they could be external. | Low | acknowledged |
5.1.5 | State visibility is not set Code Snippet Result/Recommendation State variables without visibility set. mapping(address => RiseTokenMetadata) riseTokens;(RiseTokenVault.sol line 42) State variable must be declared internal, private or public. | Low | acknowledged |
5.1.6 | Floating compiler version Code Snippet Result/Recommendation The current pragma solidity directive is floating. It is recommended to specify a fixed compiler version to | Informational | acknowledged |
5.1.7 | ABIEncoder v2 Code Snippet Result/Recommendation Solidity 0.8.0 has ABI Encoder V2 activated by default. You can activate the old encoder using pragma abicoder v1, or explicitly select v2 using pragma abicoder v2 which has the same effect as pragam… | Informational | acknowledged |
5.1.8 | Unused imports Code Snippet Result/Recommendation In the current implementation this contract has an unused imported file. Line 10 import { RisedleERC20 } from "./tokens/RisedleERC20.sol"; Remove unused imports to reduce contract size. | Informational | acknowledged |
About this engagement
A smart contract audit reviews on-chain code for flaws an attacker could exploit. Engineers trace how assets move through the contracts, check who can call privileged functions, and test the arithmetic, external calls and upgrade paths. Each finding is rated by severity, and fixes are re-checked before the final report.
How softstack runs smart contract auditsMethodology
Review process
Scoping and threat modelling
The commit hash is frozen and the attack surface is mapped: asset flows, trust assumptions, privileged roles and the external systems the code depends on.
Automated analysis
Static analysers sweep the full codebase to surface known weakness patterns, unreachable states and deviations from established conventions.
Manual code review
Independent engineers read the code line by line, concentrating on business logic, access control, arithmetic and the handling of external calls.
Adversarial testing
Property-based fuzzing and invariant tests attack the assumptions the protocol relies on, targeting states that ordinary unit tests never reach.
Reporting
Every finding is documented with a severity rating, its impact, the steps to reproduce it and a concrete remediation the team can act on.
Remediation verification
Submitted fixes are re-reviewed against the original finding, and the final report records the resolved state of each one.
Standards and references
- SWC RegistrySmart Contract Weakness Classification
- CWECommon Weakness Enumeration
FAQ
Risedle was audited by softstack GmbH, a German Web3 security and software company based in Flensburg and certified to ISO/IEC 27001 by TÜV SÜD. softstack completed a smart contract audit for Risedle in February 2022. The full report is linked on this page and published in the softstack public audit archive.
The review reported 8 findings: 1 medium, 4 low and 3 informational. 0 of 8 were resolved or mitigated before the final report.
3 source files were reviewed in github.com/risedle/etfs at commit cab10fb. The published report lists every file covered.
This report covers the code as reviewed in February 2022 at commit cab10fb. Any code changed after that point is outside the reviewed scope.
Related audits
Browse all security auditsDisclaimer
This audit represents a point-in-time security assessment of the reviewed codebase and is intended for informational purposes only. While Softstack applies industry-standard security review methodologies, no audit can guarantee the absence of vulnerabilities, bugs, or other security risks. This report does not constitute financial, legal, regulatory, or investment advice, nor does it endorse the project, its business model, products, or services. Security is an ongoing process, and we strongly recommend conducting a new assessment following any material code changes or at least every 6 months to address newly emerging threats, vulnerabilities, and ecosystem developments.