Record sog_issuer_liquity

Liquity

Liquity developed LUSD for its original protocol and later introduced BOLD with Liquity V2.

Category
Protocol or software system
Regulatory character
Protocol or decentralized system
Jurisdiction
Unknown or not publicly resolvedUnknown or not publicly resolved
Connected assets
2
Relationships
2 current0 historical
Evidence
5 source records

Identity and taxonomy

Overview

Public classification, legal-form state, jurisdiction, roles, confidence, and review state remain explicit.
Organization categoryProtocol or software system
Canonical organization typeProtocol Ecosystem
Legal formNot recorded in canonical data
Legal-form stateNot Recorded
Regulatory characterProtocol or decentralized system
JurisdictionUnknown or not publicly resolved
Jurisdiction scopeUnknown or not publicly resolved
Functional rolesProtocol operator
Relationship statesActive relationship
Primary display relationships2
Official websitehttps://www.liquity.org/
Record confidenceMedium
Last reviewed2026-06-02
Category
Protocol or software system
Regulatory character
Protocol or decentralized system
Jurisdiction
Unknown or not publicly resolved
Jurisdiction scope
Unknown or not publicly resolved
Functional roles
Protocol operator
Record confidence
Medium

Connected assets

Relationships

Current, ended, and unknown relationships remain separate. Primary display is navigation only.
StablecoinSymbolFunctional roleDisplayFromUntilStateLifecycle
BOLDBOLDProtocol operatorPrimary display2025-05-19Not yet recordedActive relationshipActive
Liquity USDLUSDProtocol operatorPrimary display2021-04-05Not yet recordedActive relationshipActive

BOLD

Primary display
Role
Protocol operator
State
Active relationship
From
2025-05-19
Until
Not recorded

Liquity USD

Primary display
Role
Protocol operator
State
Active relationship
From
2021-04-05
Until
Not recorded

Material history

Events

Typed events and organization control actions remain linked to evidence.
DateEventCategorySubtypeStatus effect
2025-05-19Liquity V2 brings BOLD liveLaunch and introductionLaunchRemained active
2021-04-05Liquity V1 launches with LUSDLaunch and introductionProtocol Launch or Lifecycle ContextNo lifecycle change

Provenance

Evidence

Source identity, publication date, reliability, archive state, and relation count remain separate.
5 source identities · 6 evidence relations
SourcePublisherSource categoryProvenancePrimary or secondarySupported claimsArchiveReliability
Liquity documentation for LUSD
Published Not yet recorded
LiquityOfficial statement or announcement
Canonical: Issuer Statement
Subject-controlled sourcePrimary sourceEntity Collateral Redemption, Lusd Protocol Lifecycle ContextNo archive recordedMedium
BOLD and Earn
Published Not yet recorded
LiquityOfficial documentation or product page
Canonical: Protocol Docs
Subject-controlled sourcePrimary sourceBold Collateral Direct Redemption and Asset Identity, Bold Distinct from SboldDirect archived snapshotHigh
Liquity V2 relaunch reference
Published 2025-05-19
LiquityOfficial documentation or product page
Canonical: Protocol Docs
Subject-controlled sourcePrimary sourceLiquity V2 Relaunch DateDirect archived snapshotMedium
BOLD redemptions and delegation
Published Not yet recorded
LiquityOfficial documentation or product page
Canonical: Protocol Docs
Subject-controlled sourcePrimary sourceBold Public Redemption and Collateral RoutingNo archive recordedHigh
Liquity V2 technical documentation and audits
Published Not yet recorded
LiquityOfficial documentation or product page
Canonical: Protocol Docs
Subject-controlled sourcePrimary sourceBold Contract Identity Audits and Technical ArchitectureNo archive recordedHigh

Uncertainty

Known unknowns

Reviewed gaps remain visible instead of being converted into false certainty.

v1_v2_lifecycle

LUSD V1, Liquity V2, BOLD, current frontend access, and protocol redemption mechanics need deeper source-backed review.

Severity
Medium
Last checked
2026-06-02

Keep visible until LUSD and BOLD are clearly separated in lifecycle records.

v2_initial_deployment_and_relaunch_sequence

Liquity V2 experienced deployment and relaunch work before the documented May 19, 2025 live phase. A complete event sequence with exact contract transitions remains to be normalized.

Severity
Medium
Last checked
2026-06-14

The current canonical BOLD identity must not be split without source-backed contract or migration evidence.

cross_chain_representations

Official documentation describes BOLD as Ethereum-native and discusses future or external bridge support. Current non-Ethereum representations have not been accepted as canonical deployments in SOG.

Severity
Low
Last checked
2026-06-14

Do not treat third-party pools, wrappers, or bridge plans as canonical issuance.

Maintenance

Corrections and further reading

Report a record problem or inspect methodology and machine-readable data.