Liquity Bold Core (Liquity V2)

CoinspectCode version: not recorded (see the report)

Coinspect reviewed Liquity V2 (Liquity Bold Core (Liquity V2)) on 31 Dec 2024: 2 findings, 0 critical; all marked fixed.

No open critical findings
Open the reportOpen Liquity V2’s security record

Report hosted on GitHub.

Trustblock does not review code.

Findings9

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

SeverityOpenAcknowledgedFixed
Critical000
High000
Medium002
Low000

Marked None (Impact: Recommendation) by the firm. Not counted as findings.

None (Impact: Recommendation)Adversaries can manipulate batch's debt/shares ratio by deflating the debtAcknowledged

The report gives no description here.

None (Impact: Recommendation)Amount of parameters when opening troves facilitates deceiving usersAcknowledged

The report gives no description here.

None (Impact: Recommendation)Attackers can claim minted yield from the Stability Pool without leaving their funds depositedAcknowledged

The report gives no description here.

None (Impact: Recommendation)Redemption decay rate is zero before expectedAcknowledged

The report gives no description here.

None (Impact: Recommendation)Missing bold amount check in urgent redemptionsFixed

The report gives no description here.

None (Impact: Recommendation)Unused codeFixed

The report gives no description here.

None (Impact: Recommendation)Wrong implementation of an LST oracle forces protocol re-deploymentFixed

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

Liquity V2
Audits7 audits by 3 firmsLast audit Jun 2025, by Cantina.
Critical findingsNo open critical findingsAcross the 7 reports, 3 critical findings were reported. Each is marked fixed by the firm that reported it.
Open Liquity V2’s security record

Security firm

Coinspect

7 projects reviewed · 11 reports · latest Aug 2025

See Coinspect’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