Organization record
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 resolved
Scope: Unknown or not publicly resolved - Connected assets
- 2
- Relationships
- 2 current
0 historical - Evidence
- 5 source records
Reviewed identity
Organization summary
The primary category, regulatory character, jurisdiction, asset count, relationship count, and Evidence count are already shown above.Liquity developed LUSD for its original protocol and later introduced BOLD with Liquity V2.
- Legal form
- Not recorded in canonical data
- Functional roles
- Protocol operator
- Official website
- https://www.liquity.org/
- Record confidence
- Medium
- Last reviewed
- 2026-06-02
Connected assets
Relationships
Current, ended, and unknown relationships remain separate. Primary display is navigation only.| Stablecoin | Role | Period | State | Lifecycle |
|---|---|---|---|---|
| BOLDPrimary display | Protocol operator | 2025-05-19 – Not yet recorded | Active relationship | Active |
| Liquity USDPrimary display | Protocol operator | 2021-04-05 – Not yet recorded | Active relationship | Active |
BOLD
PrimaryProtocol operator
2025-05-19 – Present / not recordedLiquity USD
PrimaryProtocol operator
2021-04-05 – Present / not recordedMaterial history
Events
The five latest typed events are shown first. Control actions remain linked to evidence.| Date | Event | Type | Effect |
|---|---|---|---|
| 2025-05-19 | Liquity V2 brings BOLD live | LaunchLaunch and introduction | Remained active |
| 2021-04-05 | Liquity V1 launches with LUSD | Protocol Launch or Lifecycle ContextLaunch and introduction | No lifecycle change |
Liquity V2 brings BOLD live
Launch
Remained activeLiquity V1 launches with LUSD
Protocol Launch or Lifecycle Context
No lifecycle changeProvenance
Evidence
The first ten source records are shown initially. Source identity, publication date, reliability, and archive state remain separate.| Source | Publisher | Source category | Provenance | Primary or secondary | Supported claims | Archive | Reliability |
|---|---|---|---|---|---|---|---|
| Liquity documentation for LUSD Published Not yet recorded | Liquity | Official statement or announcement Canonical: Issuer Statement | Subject-controlled source | Primary source | Entity Collateral Redemption, Lusd Protocol Lifecycle Context | Direct archived snapshot | Medium |
| BOLD and Earn Published Not yet recorded | Liquity | Official documentation or product page Canonical: Protocol Docs | Subject-controlled source | Primary source | Bold Collateral Direct Redemption and Asset Identity, Bold Distinct from Sbold | Direct archived snapshot | High |
| Liquity V2 relaunch reference Published 2025-05-19 | Liquity | Official documentation or product page Canonical: Protocol Docs | Subject-controlled source | Primary source | Liquity V2 Relaunch Date | Direct archived snapshot | Medium |
| BOLD redemptions and delegation Published Not yet recorded | Liquity | Official documentation or product page Canonical: Protocol Docs | Subject-controlled source | Primary source | Bold Public Redemption and Collateral Routing | No archive recorded | High |
| Liquity V2 technical documentation and audits Published Not yet recorded | Liquity | Official documentation or product page Canonical: Protocol Docs | Subject-controlled source | Primary source | Bold Contract Identity Audits and Technical Architecture | Direct archived snapshot | High |
Official statement or announcement
MediumLiquity documentation for LUSD
- Publisher
- Liquity
- Published
- Not yet recorded
- Provenance
- Subject-controlled source
- Primary or secondary
- Primary source
- Supported claims
- Entity Collateral Redemption, Lusd Protocol Lifecycle Context
- Archive
- Direct archived snapshot
- Reliability
- Medium
Official documentation or product page
HighBOLD and Earn
- Publisher
- Liquity
- Published
- Not yet recorded
- Provenance
- Subject-controlled source
- Primary or secondary
- Primary source
- Supported claims
- Bold Collateral Direct Redemption and Asset Identity, Bold Distinct from Sbold
- Archive
- Direct archived snapshot
- Reliability
- High
Official documentation or product page
MediumLiquity V2 relaunch reference
- Publisher
- Liquity
- Published
- 2025-05-19
- Provenance
- Subject-controlled source
- Primary or secondary
- Primary source
- Supported claims
- Liquity V2 Relaunch Date
- Archive
- Direct archived snapshot
- Reliability
- Medium
Official documentation or product page
HighBOLD redemptions and delegation
- Publisher
- Liquity
- Published
- Not yet recorded
- Provenance
- Subject-controlled source
- Primary or secondary
- Primary source
- Supported claims
- Bold Public Redemption and Collateral Routing
- Archive
- No archive recorded
- Reliability
- High
Official documentation or product page
HighLiquity V2 technical documentation and audits
- Publisher
- Liquity
- Published
- Not yet recorded
- Provenance
- Subject-controlled source
- Primary or secondary
- Primary source
- Supported claims
- Bold Contract Identity Audits and Technical Architecture
- Archive
- Direct archived snapshot
- Reliability
- High
UncertaintyKnown unknowns3
V1 V2 Lifecycle
LUSD V1, Liquity V2, BOLD, current frontend access, and protocol redemption mechanics need deeper source-backed review.
Medium · last checked 2026-06-02Keep 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.
Medium · last checked 2026-06-14The 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.
Low · last checked 2026-06-14Do not treat third-party pools, wrappers, or bridge plans as canonical issuance.
Maintenance