Web3 · Smart Contract Audit
Amun Security Audits
softstack has completed 2 smart contract audits for Amun between July 2021 and October 2021, reporting 7 findings in total (3 low and 4 informational). Every report is published in the softstack public audit archive.
Key facts
- Client
- Amun
- Audits completed
- 2
- First audited
- Latest audit
- Languages
- Solidity
About the project
Amun DeFi was a set of Ethereum-based tools that helped users pursue returns across decentralised finance protocols through lending and staking. It integrated with established DeFi platforms and also supported Polygon. The amun.com domain now hosts an unrelated business, so the product appears to be discontinued under that name.
Findings
Combined across all 2 reviews softstack has completed for Amun. Each report is broken out below.
0 of 7 findings resolved before the final reports.
Reports
Newest first. Every report covers its own scope and commit.
Basket & Safe Polygon smart contract audit
0Critical0High0Medium2Low4Informational0 of 6 resolved
Scope
Source repositorygithub.com/amun/contractsComponents reviewed
10 modules · 10 files- IChildAmunWeth.sol
- IInvestmentSafe.sol
- IPolygonERC20Wrapper.sol
- ISingleNativeTokenExitV2.sol
- IsingleTokenJoinV2.sol
- InvestmentSafe.sol
- InvestmentSafeFactory.sol
- SingleTokenJoinV2.sol
- SingleNativeTokenExitV2.sol
- EthSingleTokenJoinV2.sol
All 6 findings
ID Title Severity Status 5.1.1SPDX license identifier not provided Code Snippet Result/Recommendation SPDX license identifier not provided in source file. - Before publishing, consider adding a comment containing "SPDX-License-Identifier: <SPDX-License>" to each source file.
Low acknowledged 5.1.2Missing natspec documentation Code Snippet Result/Recommendation Solidity contracts can use a special form of comments to provide rich documentation for functions, return variables and more.
Low acknowledged 5.1.3Fix Spelling and Grammatical Errors Code Snippet Result/Recommendation Language mistakes were identified in the codebase. Fixing these mistakes can help improve the end-user experience by providing clear information on errors encountered, and improve the maintainability and…
Informational acknowledged 5.1.4A floating pragma is set Code Snippet Result/Recommendation The current pragma Solidity directive is "^0.7.5". It is recommended to specify a fixed compiler version to
Informational acknowledged 5.1.5ABIEncoder v2 Code Snippet Result/Recommendation The second change since solidity 0.8.0 that is very visible is that the ABI coder v2 is activated by default.
Informational acknowledged 5.1.6Public functions could be external Code Snippet Result/Recommendation In the current implementation several functions are declared as public where they could be external.
Informational acknowledged Rebalance Manager smart contract audit
0Critical0High0Medium1Low0Informational0 of 1 resolved
Scope
Source repositorygithub.com/amun/contractsComponents reviewed
14 modules · 17 files- PangolinRebalanceManager.sol
- RebalanceManager.sol
- RebalanceManagerV2.sol
- DepositLogicDecimalWrapper.sol
- IDecimalWrapper.sol
- MockDecimalWrapper.sol
- RebalanceManageV2.sol
- IPangolinRebalanceManager.sol
- IRebalanceManager.sol
- IRebalanceManagerV2.sol
- IUniswapV2Factory.sol
- IUniswapV2Pair.sol
- IUniswapV2Router01.sol
- IUniswapV2Router02.sol
All 1 findings
ID Title Severity Status 5.1.1No package.json Code Snippet Result/Recommendation In the current implementation, and repository is no package.json included to correctly install the needed dependencies.
Low 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
Amun 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 has completed 2 smart contract audits for Amun between July 2021 and October 2021. The published reports are linked on this page and in the softstack public audit archive.
2 separate reviews, the first in July 2021 and the most recent in October 2021. Each one covers its own scope and commit, and is listed individually on this page.
7 findings across all 2 reviews: 3 low and 4 informational. 0 of 7 were resolved or mitigated before the final reports.
Each report covers the code as it stood at the commit it names, the most recent in October 2021. 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.