MetaCity Executed a Forced Identity Protocol Wipe on 2.3 Million Accounts at 3:00 AM Without Notice — Users Woke Up to Different Names, Missing Avatars, and No Explanation

At exactly 3:00 AM EST, MetaCity's identity infrastructure executed what internal logs describe as a 'Protocol Integrity Sweep' — an automated routine that forcibly reset username assignments, avatar configurations, and profile display settings for approximately 2.3 million user accounts. The sweep ran without any advance notice, user consent prompt, or in-platform alert. Affected users waking up this morning found their display names replaced with system-generated identifiers, their avatars reverted to platform defaults, and their custom profile configurations wiped. MetaCity confirmed the sweep occurred at 6:14 AM, described it as a 'legacy identifier conflict resolution process,' and has not indicated when or whether personalization data will be restored.

The phrase 'legacy identifier conflict' appears three times in MetaCity's published developer documentation. In each instance, it refers to a specific and narrow technical problem: accounts created before MetaCity's 2022 platform migration that retained old-format identifier strings incompatible with the current session management architecture. The fix for a legacy identifier conflict is a targeted account-level remediation — a process that runs on individual accounts flagged for migration incompatibility during routine health checks. It is not, by any documented procedure or architectural specification, a process that should run simultaneously on 2.3 million accounts at 3:00 in the morning. MetaCity has called what happened this morning a 'legacy identifier conflict resolution process.' The label is technically defensible. It does not explain what happened.

The sweep reset three distinct categories of account data. Display names — the names users choose to present themselves to the community — were replaced with system-generated identifiers following the format MC_USR_ followed by an eight-digit code. Avatar configurations — the visual appearance settings that users build, sometimes over years, through the platform's character customization system — were reverted to the platform's default avatar state: a featureless figure in a neutral gray outfit. Profile display settings — which include layout configurations, pinned content selections, featured item displays, and custom background choices — were cleared to default. None of this data was deleted from the platform's storage systems. It exists. The sweep did not destroy the data. It simply disconnected all of it from the accounts it belonged to and replaced it with defaults. The reconnection process has not been described by MetaCity.

2.3 Million People Woke Up as Someone Else

The community response organized around the hashtag #NotMyName within approximately 90 minutes of the first wave of users discovering the changes when they logged in between 5:30 and 6:00 AM EST. The initial posts were diagnostic — screenshots of the MC_USR identifier format with confused captions. By 7:00 AM they had shifted tone. Users who had spent years building their MetaCity identity — their name, their avatar, their profile as a presentation of who they are in this space — described the experience of logging in to find a system code where their name had been as something more visceral than a technical inconvenience. @KellyMoore_V4 wrote: 'I have had this name since MetaCity launched. I was in the beta. This is the name my community knows. Seeing MC_USR_40291847 on my profile felt like being told the platform doesn't know who I am anymore.' The post has 890,000 likes.

The legal dimension is being assessed by several advocacy groups who have been tracking MetaCity's data practices since the Neva Lynx exposure last month. MetaCity's Terms of Service grant the platform broad authority to 'modify, update, or reset account settings for purposes of platform integrity and infrastructure maintenance.' That language almost certainly covers what happened this morning from a contractual liability standpoint. What is less clear is whether the sweep constitutes a privacy violation — specifically, whether the replacement of a user-chosen identifier with a system-generated code constitutes a modification of personal data that required user consent under applicable digital privacy law. The platform's privacy policy describes usernames as 'account identifiers chosen by the user.' Three legal analysts have argued publicly this morning that replacing a user-chosen identifier with a platform-generated one without consent is a modification of personal data that falls under consent requirements. MetaCity has not addressed the argument.

The question that MetaCity has not answered, and that the community is asking with increasing urgency, is why. The 'legacy identifier conflict resolution' framing explains the mechanism — a sweep that finds and resets conflicted identifiers — but not the trigger. What caused 2.3 million accounts to be flagged for legacy identifier conflicts simultaneously, at 3:00 AM, with no apparent warning and no staged rollout? The platform has processed legacy migration issues continuously since 2022 without executing a sweep of this scale. One possibility is that a migration process that had been running gradually for four years hit a batch threshold and processed a large cohort automatically. Another is that a new system requirement created a sudden incompatibility in a previously untouched identifier class. A third, which several engineers have raised in community boards, is that the sweep was not a migration fix at all — that 'legacy identifier conflict resolution' is a description applied after the fact to a process that served a different purpose. MetaCity has not confirmed which of these is accurate.