Omniscia Criptan Audit
Wallet Implementation Security Audit
Audit Overview
We were tasked with performing an audit of the Criptan codebase and in particular their minimalistic wallet implementation meant to allow the creation of multiple receiver addresses deterministically allowing a user to receive funds in addresses whose ownership hasn't been revealed yet.
Over the course of the audit, we identified a potential issue in the support of ERC-20 tokens that can cause certain ones such as Tether (USDT) to remain permanently locked in the contract.
Overall, the codebase has been developed to a very high standard and we advise the Criptan team to integrate all the findings we identified in the report to ensure the codebase is fit for production.
Post-Audit Conclusion
The Criptan team promptly remediated all findings identified in the report and applied the gas optimizations exactly as we advised.
The codebase can be considered of a very high standard and to be conformant to the latest security standards and practices.
Contracts Assessed
| Files in Scope | Repository | Commit(s) |
|---|---|---|
| Wallet.sol (WAL) | wallet-contracts | 45ac888a96, c9d6b6be93 |
| WalletFactory.sol (WFY) | wallet-contracts | 45ac888a96, c9d6b6be93 |
Audit Synopsis
| Severity | Identified | Alleviated | Partially Alleviated | Acknowledged |
|---|---|---|---|---|
 | 0 | 0 | 0 | 0 |
 | 1 | 1 | 0 | 0 |
 | 1 | 1 | 0 | 0 |
 | 3 | 3 | 0 | 0 |
During the audit, we filtered and validated a total of 1 findings utilizing static analysis tools as well as identified a total of 4 findings during the manual review of the codebase. We strongly recommend that any minor severity or higher findings are dealt with promptly prior to the project's launch as they introduce potential misbehaviours of the system as well as exploits.
The list below covers each segment of the audit in depth and links to the respective chapter of the report: