Skip to content
Anomaly

First Launch, Profile, and @anomaly Identity

Intended scope

Section titled “Intended scope”
  • First-run identity keypair generation (ECDSA) — happens on the first Launcher run, persisted per user profile.
  • %APPDATA%/Anomaly/ layout on Windows, ~/.config/Anomaly/ on Linux (see Reference → Runtime Paths).
  • How to locate and copy your @anomaly ID — right-click your name in the Launcher.
  • What the @anomaly ID is used for — remote-admin permission strings, server allow-lists, identity proofs.
  • Backing up or migrating your identity (copy the private key file; warn about loss of access if deleted).

Sources

Section titled “Sources”
  • Anomaly.Shared\Auth\ — keypair primitives (ECDSA / X25519 / AES-GCM).
  • Anomaly.Launcher\Services\UserProfileService.cs.
  • E:\Projects\AnomalyLabs\Anomaly\README.md — “@anomaly” ID section.