- Home
- Security Audits
- MakiSwap
Web3 · Smart Contract Audit
MakiSwap Security Audit
softstack completed a smart contract audit of MakiSwap's AMM in May 2021, reporting 7 findings (1 medium, 2 low and 4 informational). The full report is published in the softstack public audit archive.
Key facts
- Client
- MakiSwap
- Completed
- Languages
- Solidity
- Commit
a816f17ad3f5
About the project
MakiSwap was an automated market maker and yield farming platform built on Huobi Eco Chain by the UniLayer team. It was intended to extend UniLayer's DeFi tooling beyond Ethereum and to support interoperability between the two networks. The makiswap.com site no longer returns a working application.
Scope
Source repositorygithub.com/MakiSwap-Protocol/makiswap-protocolComponents reviewed
7 modules · 7 files- SoyBar.sol
- MasterChef.sol
- MakiBar.sol
- MakiToken.sol
- swapV2Factory.sol
- swapV2Router02.sol
- WHT.sol
Findings
| ID | Title | Severity | Status |
|---|---|---|---|
5.1.1 | Linter parse error (()) Code Snippet Result/Recommendation The contract is using names, which are used within the Binance Smart Chain ecosystem and smart contract structure. Most probably fractions from the fork process. | Medium | fixed |
5.1.2 | Wrong import of OpenZeppelin library Code Snippet Result/Recommendation In the current implementation, OpenZeppelin files are added directly into the | Low | fixed |
5.1.3 | Multiple code lines with the same functions Code Snippet Result/Recommendation It is not necessary to have two times or more the same functions inside different files. | Low | fixed |
5.1.4 | Fractions from BSC / Pancakeswap Fork Code Snippet Result/Recommendation The contract is using names, which are used within the Binance Smart Chain ecosystem and smart contract structure. Most probably fractions from the fork process. | Informational | fixed |
5.1.5 | Interfaces are inside the main code Code Snippet Result/Recommendation Interfaces are always better to separate into different files. Line: 3 - 17 interface IMakiFactory Line: 19 - 68 interface IMakiPair For more interfaces see 4.2 It is best practice to have interfaces not… | Informational | fixed |
5.1.6 | Two files have almost the same code Code Snippet Result/Recommendation Same content in two files Line: 263 diff: hex'd0d4c4cd0848c93cb4fd1f498d7013ee6bfb25783ea 21593d5834f5d250ece66' // init code hash Remove that file from repo, as duplicated code 5.1.7 Use of different… | Informational | fixed |
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
MakiSwap 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 MakiSwap in May 2021. The full report is linked on this page and published in the softstack public audit archive.
The review reported 7 findings: 1 medium, 2 low and 4 informational.
7 source files were reviewed in github.com/MakiSwap-Protocol/makiswap-protocol at commit a816f17. The published report lists every file covered.
This report covers the code as reviewed in May 2021 at commit a816f17. 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.