Record sog_ev_nuon_base_launch

Nuon v2 opens publicly on Base

Nuon opened its redesigned v2 protocol to the wider public on March 3, 2025. Users could mint NUON 1:1 against USDC and stake on Base. SOG records this as a v2 public relaunch rather than the original asset launch.

Date
2025-03-03
Category
Launch and introduction
Subtype
Protocol V2 Public Launch
Status effect
Remained active
Recovery
Not applicableNot yet recorded
Evidence
5 source records5 relations

Identity and classification

Overview

Date, taxonomy, impact, recovery, mechanism, confidence, and evidence remain separate.
Date2025-03-03
Public event categoryLaunch and introduction
Canonical event subtypeProtocol V2 Public Launch
Structured detail kindMigration
Stablecoin subjectsNuon
Organization subjectsNuon Finance
ImpactHigh
Effect on stablecoin lifecycleRemained active
Canonical status-effect valueActive V2
Recovery or reversalNot applicable
Recovery dateNot Applicable
Cause or mechanismNuon v2 public relaunch on Base with a new contract and redesigned USDC-treasury architecture. Holder migration from v1 is not established.
Structured detail coverageStructured fields available below
Record confidenceHigh
Date
2025-03-03
Public category
Launch and introduction
Canonical subtype
Protocol V2 Public Launch
Structured detail kind
Migration
Impact
High
Status effect
Remained active
Recovery
Not applicable
Recovery date
Not yet recorded
Cause or mechanism
Nuon v2 public relaunch on Base with a new contract and redesigned USDC-treasury architecture. Holder migration from v1 is not established.
Record confidence
High

Affected records

Subjects

Stablecoin and organization subjects remain separate record groups.
Stablecoin subject

Nuon

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

Organization subject

Nuon Finance

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
Migration detail — SummaryNuon v2 public relaunch on Base with a new contract and redesigned USDC-treasury architecture. Holder migration from v1 is not established.
Migration detail — StatusActive V2
Migration detail — Summary
Nuon v2 public relaunch on Base with a new contract and redesigned USDC-treasury architecture. Holder migration from v1 is not established.
Migration detail — Status
Active V2

Provenance

Evidence

Source identity, publisher, publication date, reliability, archive, and relation count remain separate.
5 source identities · 5 evidence relations
SourcePublisherSource categoryProvenancePrimary or secondarySupported claimsArchiveReliability
Nuon stablecoin overview
Published Not yet recorded
NuonOfficial documentation or product page
Canonical: Protocol Docs
Subject-controlled sourcePrimary sourceNuon USD Mint Inflation Yield Rebase and Base DeploymentNo archive recordedHigh
Minting Nuon
Published Not yet recorded
NuonOfficial documentation or product page
Canonical: Protocol Docs
Subject-controlled sourcePrimary sourceNuon Usdc Mint and Positive Rebase MechanicsNo archive recordedHigh
Nuon token contracts
Published Not yet recorded
NuonOfficial documentation or product page
Canonical: Protocol Docs
Subject-controlled sourcePrimary sourceNuon Base Contract and Related Token AddressesNo archive recordedHigh
Nuon v2 is now Open
Published 2025-03-03
NuonOfficial statement or announcement
Canonical: Official Protocol Announcement
Subject-controlled sourcePrimary sourceV2 Public Launch, Base, Usdc Minting, Staking, V2 Base Public LaunchArchive index or wildcardHigh
Nuon v2 Whitepaper Introduction
Published Not yet recorded
NuonTechnical documentation or repository
Canonical: Official Whitepaper
Subject-controlled sourcePrimary sourceV1 Cdp Model, V2 Rebase Model, Version Transition, V1 V2 Architecture DifferenceArchive index or wildcardHigh

Minting Nuon

Publisher
Nuon
Published
Not recorded
Reliability
High
Relations
1

Maintenance

Corrections and further reading

Use the documented correction path and methodology.