Stable or Gone
Event record
Return to registerOpen sources

Record sog_ev_fxusd_v2_upgrade_2025

fxUSD proxy is upgraded for f(x) Protocol V2

The continuous Ethereum fxUSD proxy emitted an on-chain upgrade event on January 2, 2025 as f(x) Protocol moved into its V2 architecture. Official documentation distinguishes V1 and V2 while retaining the same base fxUSD token identity.

Date
2025-01-02
Category
Governance and protocol change
Subtype
Protocol Upgrade
Status effect
Remained active
Recovery
Not applicableNot yet recorded
Evidence
3 source records2 relations

Identity and classification

Overview

Date, taxonomy, impact, recovery, mechanism, confidence, and evidence remain separate.
Date2025-01-02
Public event categoryGovernance and protocol change
Canonical event subtypeProtocol Upgrade
Structured detail kindMigration
Stablecoin subjectsf(x) Protocol fxUSD
Organization subjectsf(x) Protocol
ImpactHigh
Effect on stablecoin lifecycleRemained active
Canonical status-effect valueActive V2
Recovery or reversalNot applicable
Recovery dateNot Applicable
Cause or mechanismSame-proxy transition from the V1 product architecture to f(x) Protocol V2.
Structured detail coverageStructured fields available below
Record confidenceHigh
Date
2025-01-02
Public category
Governance and protocol change
Canonical subtype
Protocol Upgrade
Structured detail kind
Migration
Impact
High
Status effect
Remained active
Recovery
Not applicable
Recovery date
Not yet recorded
Cause or mechanism
Same-proxy transition from the V1 product architecture to f(x) Protocol V2.
Record confidence
High

Affected records

Subjects

Stablecoin and organization subjects remain separate record groups.
Stablecoin subject

f(x) Protocol fxUSD

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

Organization subject

f(x) Protocol

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 — SummarySame-proxy transition from the V1 product architecture to f(x) Protocol V2.
Migration detail — StatusImplemented Same Token Proxy Upgrade
Migration detail — Summary
Same-proxy transition from the V1 product architecture to f(x) Protocol V2.
Migration detail — Status
Implemented Same Token Proxy Upgrade

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
f(x) Protocol contracts
Published Not yet recorded		f(x) ProtocolOfficial documentation or product page
Canonical: Official Documentation		Subject-controlled sourcePrimary sourceEthereum Deployment, Fxusd Proxy, Version 1 Contracts, Version 2 Contracts, Current Proxy and Versioned ContractsArchive index or wildcardHigh
What is the difference between f(x) Protocol V1 and V2?
Published Not yet recorded		f(x) ProtocolOfficial documentation or product page
Canonical: Official Documentation		Subject-controlled sourcePrimary sourceVersion 1, Version 2, Architecture Change, Stablecoin Continuity, V1 V2 Architecture BoundaryArchive index or wildcardHigh
fxUSD proxy upgrade event on Ethereum
Published 2025-01-02		EtherscanOn-chain record or explorer
Canonical: Onchain Explorer		Technical primary sourcePrimary sourceProxy Upgrade, Same Token Address, V2 Activation, Ethereum, Same Proxy V2 UpgradeArchive index or wildcardHigh

Maintenance

Corrections and further reading

Use the documented correction path and methodology.
Submit a correctionMethodologyEvent registerData manifest