How UnifiedID is Created

The typical flow:

1. User arrives at an app or Glyph-enabled entry point (game, wallet, ecosystem portal, etc.).

2. Connect / sign-in with any supported wallet or identity method.

3. Create UnifiedID

   • The user opts to create a UnifiedID.

   • A registry contract or off-chain registry service (depending on chain and trust model) registers an ID bound to the user’s initial wallet.

4. Attest additional wallets

   • The user can link more wallets by proving ownership with signed messages or transactions.

   • Depending on the privacy level, these links can be kept off-chain or turned into ZK commitments.

5. Grant consent to an app

   • The user approves specific scopes so the app can query a subset of claims via Glyph.

From this point on, the user’s UnifiedID becomes the anchor for all privacy-preserving signals that apps can request, rather than dealing with raw wallet addresses directly.