ReytsCAD
Audit · firm’s term: security assessment
Certora reviewed Reyts (ReytsCAD) on 22 May 2026: 8 findings, 0 critical; all marked fixed.
No open critical findings
Findings15
Statuses are the security firm’s own, from its report.
| Severity | Open | Acknowledged | Fixed |
|---|---|---|---|
| Critical | 0 | 0 | 0 |
| High | 0 | 0 | 1 |
| Medium | 0 | 0 | 2 |
| Low | 0 | 0 | 5 |
HighDue to storing all refHashes in the instance storage of the old mint controller, the new mint controller will be permanently DoSd after ~1300-1400 mintsFixed
The report gives no description here.
MediumDeposit cap checks are ineffective as they’re per partner, rather than per assetFixed
The report gives no description here.
MediumRate band override mechanism can be circumvented with a sequence of transactionsFixed
The report gives no description here.
LowAll propose_* functions silently overwrite pending stateFixed
The report gives no description here.
LowGovernance has no per tx/ daily cap on treasury_send and burn_from_poolFixed
The report gives no description here.
LowNot removing certain instance key-value pairs but only setting them to false can lead to storage bloatFixed
The report gives no description here.
LowThe treasury address in the Governance contract can’t be changedFixed
The report gives no description here.
Lowvault.draw does not check partner_allowedFixed
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 Reyts’s security record
ReytsAudits1 audit by 1 firmLast audit May 2026, by Certora.
Critical findingsNo open critical findingsIn 1 report.
Open Reyts’s security recordSecurity firm
Certora29 projects reviewed · 56 reports · latest Aug 2026
See Certora’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