Cryptoart.com Audit Report
Cyfrin reviewed CRYPTOART (Cryptoart.com Audit Report) on 24 Apr 2025: 7 findings, 0 critical; 6 marked fixed, 1 acknowledged.
No open critical findings
Open the reportOpen CRYPTOART’s security record
Report hosted on GitHub.
Trustblock does not review code.
Findings7
Statuses are the security firm’s own, from its report.
| Severity | Open | Acknowledged | Fixed |
|---|---|---|---|
| Critical | 0 | 0 | 0 |
| High | 0 | 0 | 0 |
| Medium | 0 | 0 | 1 |
| Low | 0 | 1 | 5 |
MediumCollector can add CreatorStory, corrupting the provenance of an artworkFixed
The report gives no description here.
LowAllow custom Creator and Collector names to be emitted in IStory events to build artwork provenanceFixed
The report gives no description here.
LowAllow users to increment their nonce to void their signaturesFixed
The report gives no description here.
LowIERC7160 specification requires hasPinnedTokenURI to revert for non-existent tokenIdFixed
The report gives no description here.
LowIERC7160 specification requires pinTokenURI to revert for non-existent tokenIdFixed
The report gives no description here.
LowInconsistent pause functionality allows certain state-changing operations when contract is pausedFixed
The report gives no description here.
Contracts in scope
No deployed address is recorded for this audit.
The report names a repository or files. Open the report to see its scope.
Part of CRYPTOART’s security record
CRYPTOART
Audits1 audit by 1 firmLast audit Apr 2025, by Cyfrin.
Critical findingsNo open critical findingsIn 1 report.
Open CRYPTOART’s security recordSecurity firm
Cyfrin28 projects reviewed · 79 reports · latest Sep 2026
See Cyfrin’s auditsSomething wrong on this page? A missing report, a wrong date, a finding that was fixed since. Tell us and we check it against its source.
Tell us