Ouroboros security review

Pashov Audit GroupCode version: not recorded (see the report)

Audit · firm’s term: security review

Pashov Audit Group reviewed Ouroboros (Ouroboros security review) on 26 Dec 2024: 22 findings, 0 critical; 14 marked fixed, 8 acknowledged.

No open critical findings
Open the reportOpen Ouroboros’s security record

Report hosted on GitHub.

Trustblock does not review code.

Findings22

Statuses are the security firm’s own, from its report.

SeverityOpenAcknowledgedFixed
Critical000
High000
Medium056
Low038
MediumBorrower will unfairly lose his stables if the collateral goes into recovery mode during sunset periodAcknowledged

The report gives no description here.

MediumCurrent redemption design causes users to be charged a penalty despite doing nothing wrongAcknowledged

The report gives no description here.

MediumDoS due to Chainlink oracle returning wrong data or going offlineAcknowledged

The report gives no description here.

MediumDoS in redemptions due to inability to consume reescrowed stablesAcknowledged

The report gives no description here.

MediumTCR is overestimated on redemptionsAcknowledged

The report gives no description here.

LowInconsistent behavior of fetchEthPrice() when Chainlink oracle failsAcknowledged

The report gives no description here.

LowRate limits can prevent the system recovery via debt issuanceAcknowledged

The report gives no description here.

LowUsers can pay less fees by abusing the utilization ratio fee calculationAcknowledged

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 Ouroboros’s security record

Ouroboros
Audits1 audit by 1 firmLast audit Dec 2024, by Pashov Audit Group.
Critical findingsNo open critical findingsIn 1 report.
Open Ouroboros’s security record

Security firm

Pashov Audit Group

30 projects reviewed · 53 reports · latest Jul 2026

See Pashov Audit Group’s audits

Something 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