Record sog_ev_susd_rebrand_2018

nUSD is renamed sUSD during the Synthetix rebrand

Havven announced its transition to Synthetix on November 30, 2018 and mapped nUSD to sUSD. The announcement stated that contract addresses would not change, so SOG treats this as a same-token rebrand rather than a new stablecoin launch.

Date
2018-11-30
Category
Migration and rebrand
Subtype
Rebrand
Status effect
No lifecycle change
Recovery
Not applicableNot yet recorded
Evidence
3 source records2 relations

Identity and classification

Overview

Date, taxonomy, impact, recovery, mechanism, confidence, and evidence remain separate.
Date2018-11-30
Public event categoryMigration and rebrand
Canonical event subtypeRebrand
Structured detail kindGovernance Change
Stablecoin subjectsSynthetix USD
Organization subjectsSynthetix
ImpactMedium
Effect on stablecoin lifecycleNo lifecycle change
Canonical status-effect valueNo recorded change
Recovery or reversalNot applicable
Recovery dateNot Applicable
Cause or mechanismProject and token naming changed from Havven and nUSD to Synthetix and sUSD without contract-address changes.
Structured detail coverageStructured fields available below
Record confidenceHigh
Date
2018-11-30
Public category
Migration and rebrand
Canonical subtype
Rebrand
Structured detail kind
Governance Change
Impact
Medium
Status effect
No lifecycle change
Recovery
Not applicable
Recovery date
Not yet recorded
Cause or mechanism
Project and token naming changed from Havven and nUSD to Synthetix and sUSD without contract-address changes.
Record confidence
High

Affected records

Subjects

Stablecoin and organization subjects remain separate record groups.
Stablecoin subject

Synthetix USD

Open the stablecoin dossier for current state, organizations, deployments, evidence, and unknowns.

Organization subject

Synthetix

Open the organization record for roles, relationships, events, evidence, and unknowns.

Typed record

Structured detail

Event-type-specific facts remain visible with explicit value states.
Structured event detail
Governance-change detail — SummaryProject and token naming changed from Havven and nUSD to Synthetix and sUSD without contract-address changes.
Governance-change detail — StatusImplemented Same Token Rebrand
Governance-change detail — Resolution date2018-11-30
Governance-change detail — Affected deploymentssog_dep_susd_ethereum_seed
Governance-change detail — Related organizationssog_issuer_synthetix
Governance-change detail — Summary
Project and token naming changed from Havven and nUSD to Synthetix and sUSD without contract-address changes.
Governance-change detail — Status
Implemented Same Token Rebrand
Governance-change detail — Resolution date
2018-11-30
Governance-change detail — Affected deployments
sog_dep_susd_ethereum_seed
Governance-change detail — Related organizations
sog_issuer_synthetix

Provenance

Evidence

Source identity, publisher, publication date, reliability, archive, and relation count remain separate.
3 source identities · 3 evidence relations
SourcePublisherSource categoryProvenancePrimary or secondarySupported claimsArchiveReliability
Rebuilding sUSD
Published 2026-02-12
SynthetixOfficial statement or announcement
Canonical: Official Protocol Update
Subject-controlled sourcePrimary sourcePersistent Depeg, Minting Deprecation, Repeg Plan, 420 Pool, Persistent Depeg and Repeg MeasuresNo archive recordedHigh
Havven is transforming into Synthetix!
Published 2018-11-30
SynthetixOfficial statement or announcement
Canonical: Official Protocol Announcement
Subject-controlled sourcePrimary sourceRebrand, Same Contract, Nusd Alias, Susd Name, Nusd to Susd RebrandArchive index or wildcardHigh
Synths are now live on Mainnet
Published 2018-12-07
SynthetixOfficial statement or announcement
Canonical: Official Protocol Announcement
Subject-controlled sourcePrimary sourceSusd, Nusd Continuity, Synth Mainnet, Susd Continuity from NusdArchive index or wildcardHigh

Rebuilding sUSD

Publisher
Synthetix
Published
2026-02-12
Reliability
High
Relations
0

Maintenance

Corrections and further reading

Use the documented correction path and methodology.