- Home
- Security Audits
- EverRise
Web3 · Smart Contract Audit
EverRise Security Audit
softstack completed a smart contract audit of EverRise's Protocol Token & Staking v3 in April 2022, reporting 7 findings (2 medium, 3 low and 2 informational), of which 5 were resolved or mitigated before the final report. The full report is published in the softstack public audit archive.
Key facts
- Client
- EverRise
- Completed
- Languages
- Solidity
- Commit
b92f0971db70- Market cap
- $1M as of 2026-09-30
About the project
EverRise is a blockchain technology company that builds security and multi-chain tooling for decentralised finance. Its ecosystem includes EverRevoke for reviewing token approvals, EverBridge for cross-chain transfers, EverSwap, EverLock and NFT staking. The dApps run on Ethereum, BNB Chain, Polygon, Avalanche and Fantom, with the RISE token at the centre.
Scope
Components reviewed
3 modules · 3 files- EverRise_flat.sol
- nftEverRise_flat.sol
- StakingnftEverRise_flat.sol
Findings
5 of 7 findings resolved before the final report.
| ID | Title | Severity | Status |
|---|---|---|---|
5.1.1 | Overpowered onlyOwner rights Code Snippet Result/Recommendation EverRise_flat.sol contract contains onlyOwner functions that set _setEverBridgeVaultAddress _setStakingAddress _setSwapEnabled _transferOwnership and Roles for Limits, Fees, BuyBack, NFTs, Exchanges,… | Medium | fixed |
5.1.2 | Exclude addresses Code Snippet Result/Recommendation The owner can exclude an account from the rewards and include it back later. Abusing this mapping can cause distribution of rewards only to specific addresses and exclude others. | Medium | fixed |
5.1.3 | Variables initialized as their types default value Code Snippet Result/Recommendation State variables do not need to be initialized to their default variables. | Low | fixed |
5.1.4 | Variables that can be made constant or immutable Code Snippet Result/Recommendation State variables that do not change during lifetime or are set at construction and never change, can be made constant or immutable. | Low | fixed |
5.1.5 | Hardcoded address Code Snippet Result/Recommendation Hardcoded values like addresses can impact the life time of the contract, as they may change in the future. | Informational | fixed |
5.1.6 | Missing test cases Code Snippet Result/Recommendation The current implementation has no unit-tests. NA It is highly recommended to write test cases for every function and control the behaviour at any time of contract executions. | Informational | acknowledged |
5.1.7 | Missing natspec documentation Code Snippet Result/Recommendation Solidity contracts can use a special form of comments to provide rich documentation for function, return variables, and more. | 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
EverRise 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 EverRise in April 2022. The full report is linked on this page and published in the softstack public audit archive.
The review reported 7 findings: 2 medium, 3 low and 2 informational. 5 of 7 were resolved or mitigated before the final report.
3 source files were reviewed at commit b92f097. The published report lists every file covered.
This report covers the code as reviewed in April 2022 at commit b92f097. 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.