ERC-1822: a matching proxy UUID does not review a storage migration
The historical UUPS proposal includes an upgrade compatibility check and separately discusses storage-layout pitfalls. Its published status is Stagnant.
WFN interpretation: one successful interface check answers a narrower question than whether an entire upgrade preserves the application’s meaning. Passing it should not be renamed a complete migration audit.
What to check before drawing a conclusion
Review the actual proxy pattern, implementation and upgrade authority of the deployment. Sharing the UUPS name does not establish that every implementation uses the historical proposal’s exact storage location or code.
Quick Brief is a reading aid. The full article and source trail stay on this page.
WFN STORY COMPASS
Choose your reading angle
Switch between the reported record, market context and open questions. Status labels distinguish claims from findings.
All context layers are visible. Choose a lens to jump to that part of the story.
Original WFN vector illustrationWFN · 2 November 2026
Editorial noteSource-based explanation with original WFN analysis. Historical records retain their dates; numerical examples are illustrative. The original vector illustration is conceptual and is not documentary evidence.
WFN REALITY LEDGER
What is on the record?
Primary-source explainer
Primary-source explainer
Primary record / reference periodHistorical proposal; Stagnant status checked 2 November 2026
The linked source supports the documented record; WFN interpretation and illustrative examples are separate.
The historical UUPS proposal includes an upgrade compatibility check and separately discusses storage-layout pitfalls. Its published status is Stagnant.
WFN interpretation: one successful interface check answers a narrower question than whether an entire upgrade preserves the application’s meaning. Passing it should not be renamed a complete migration audit.
A useful comparison maps each stored field before and after the change. If the same position is interpreted differently, familiar balances or permissions can acquire a different meaning without a user initiating a transfer.
03 · REVIEW POINTS
What to check before drawing a conclusion
Review the actual proxy pattern, implementation and upgrade authority of the deployment. Sharing the UUPS name does not establish that every implementation uses the historical proposal’s exact storage location or code.
Preserve the proposal’s status and date in documentation. The review should join structural compatibility, state interpretation and authorised execution rather than treating a standard identifier as a general certificate of upgrade safety.
