- Home
- Security Audits
- Curio Cards
Web3 · Smart Contract Audit
Curio Cards Security Audit
softstack completed a smart contract audit of Curio Cards's Nft Wrapper in September 2021, reporting 3 findings (1 medium, 1 low and 1 informational), of which 1 was resolved or mitigated before the final report. The full report is published in the softstack public audit archive.
Key facts
- Client
- Curio Cards
- Completed
- Chains
- Ethereum
- Languages
- Solidity
About the project
Curio Cards is an online art show and permanent gallery on Ethereum that launched on May 9, 2017. The project issued a series of numbered digital art cards and is cited as one of the earliest Ethereum art collectibles, predating the ERC-721 standard. Crypto commentator Thomas Hunt is credited among its creators.
Scope
Components reviewed
1 module · 1 file- CurioERC1155Wrapper.sol
Findings
1 of 3 findings resolved before the final report.
| ID | Title | Severity | Status |
|---|---|---|---|
5.1.1 | Big number of tokens are still hold by owner Code Snippet Result/Recommendation The creator and owner of the contract is still holding a decent number of tokens by themself. Which can cause by a hack or dump a decrease in price on the market. | 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 | acknowledged |
5.1.3 | Storing metadata via IPFS Code Snippet Result/Recommendation In the current implementation the IPFS addresses are hardcoded into the CurioERC1155Wrapper contract. | 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
Curio Cards 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 Curio Cards in September 2021. The full report is linked on this page and published in the softstack public audit archive.
The review reported 3 findings: 1 medium, 1 low and 1 informational. 1 of 3 were resolved or mitigated before the final report.
1 source files were reviewed. The published report lists every file covered.
This report covers the code as reviewed in September 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.