- Home
- Security Audits
- Dispatch
Web3 · Smart Contract Audit
Dispatch Security Audit
softstack completed a smart contract audit of Dispatch's Core in August 2022, reporting 3 findings (3 informational), of which 3 were resolved or mitigated before the final report. The full report is published in the softstack public audit archive.
Key facts
- Client
- Dispatch
- Completed
- Languages
- Solidity
About the project
Dispatch was a decentralised community engagement platform that delivered on-chain messages to token and NFT holders. It let projects send notifications to self-custody wallets as well as centralised platforms, and segment and target wallet audiences from one interface. Its contracts were deployed on Ethereum and Polygon.
Scope
Components reviewed
2 modules · 2 files- Admin.sol
- Messenger.sol
Findings
3 of 3 findings resolved before the final report.
| ID | Title | Severity | Status |
|---|---|---|---|
6.2.1 | Floating And Different Pragma Versions Identified Code Snippet Result/Recommendation The current pragma solidity directive is "^0.8.7" and “^0.8.13”. | Informational | fixed |
6.2.2 | Consistent Naming Of TokenOrg Code Snippet Result/Recommendation The usage of TokenOrg is not consistently used and can confuse the reader. | Informational | fixed |
6.2.3 | Specific EVM Event Message Code Snippet Result/Recommendation The usage of specific event messages for each EVM is required or use generic. | 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
Dispatch 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 Dispatch in August 2022. The full report is linked on this page and published in the softstack public audit archive.
The review reported 3 findings: 3 informational. 3 of 3 were resolved or mitigated before the final report.
2 source files were reviewed. The published report lists every file covered.
This report covers the code as reviewed in August 2022. 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.