- Home
- Security Audits
- MemeWars
Web3 · Smart Contract Audit
MemeWars Security Audit
softstack completed a smart contract audit of MemeWars's Token and Game in November 2021, reporting 8 findings (4 low and 4 informational). The full report is published in the softstack public audit archive.
Key facts
- Client
- MemeWars
- Completed
- Chains
- BNB Chain
- Languages
- Solidity
About the project
MemeWars was a blockchain game on BNB Chain whose logic ran entirely on-chain, with no off-chain components. It was designed to be permissionless and to keep running autonomously after deployment without intervention from its developers. The memewars.finance domain no longer resolves and the game appears to be discontinued.
Scope
Components reviewed
14 modules · 22 files- interfaces/IMintable.sol
- interfaces/IPancakePair.sol
- interfaces/IWETH.sol
- interfaces/IPancakeRouter02.sol
- interfaces/IPancakeRouter01.sol
- interfaces/IBurnable.sol
- interfaces/ITokenPresenter.sol
- interfaces/IPancakeFactory.sol
- MemeWarsPresenter.sol
- utils/CoinDexTools.sol
- utils/Adminable.sol
- utils/EmergencyWithdraw.sol
- utils/AntiWhale.sol
- utils/TradingGuard.sol
Findings
0 of 8 findings resolved before the final report.
| ID | Title | Severity | Status |
|---|---|---|---|
5.1.1 | Unused function Code Snippet Result/Recommendation In the current implementation is an internal function declared, which is not used in any contract. Line 180-182: _burnByDeadAddress() It is recommended to remove the unused code to | Low | acknowledged |
5.1.2 | Missing zero address validation on owner functions Code Snippet Result/Recommendation In the current implementation several owner functions are not checking for zero addresses. Setting an address to the zero address can result in unintended behavior. | Low | acknowledged |
5.1.3 | Uninitialized state variables Code Snippet Result/Recommendation In the current implementation two state variables are not initialized with a default value, which can lead to unintended behavior during contract execution. | Low | acknowledged |
5.1.4 | Weak randomness Code Snippet Result/Recommendation Generation of randomness with the block timestamp can be affected by the miners and can be predicted by some degree. | Low | acknowledged |
5.1.5 | Public functions should be declared external Code Snippet Result/Recommendation In the current implementation several functions are declared as public where they could be external. | Informational | acknowledged |
5.1.6 | Variables using too many digits Code Snippet Result/Recommendation In the current implementation are hard to read literals with too many digits. The use of hard to read literals can be error-prone. | Informational | acknowledged |
5.1.7 | A floating pragma is set Code Snippet Result/Recommendation The current pragma Solidity directive is "^0.8.4". It is recommended to specify a Line 1: pragma solidity ^0.8.4; It is recommended to follow the latter example, as future compiler versions may handle… | Informational | acknowledged |
5.1.8 | Check for boolean equality Code Snippet Result/Recommendation In the current implementation several require checks are using a comparison to a Boolean constant. This leads to unnecessary gas consumption. | 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
MemeWars 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 MemeWars in November 2021. The full report is linked on this page and published in the softstack public audit archive.
The review reported 8 findings: 4 low and 4 informational. 0 of 8 were resolved or mitigated before the final report.
22 source files were reviewed. The published report lists every file covered.
This report covers the code as reviewed in November 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.