Recovery

Deterministic identities can be restored by reproducing the original wallet signature and, if enabled, the same passkey factor. Recovery depends on retaining those credentials.

New device

1. Open the same trusted identity domain and choose the same cluster. Sign the fixed identity message again with the same wallet key and a supported deterministic signer. Native sign-in and plain signing agree when they sign those exact bytes.
2. If you registered with a passkey factor, use the same PRF-capable passkey. Device sync is platform-dependent; a newly created passkey produces a different factor.
3. The secret recomputes (SHA-256 of the deterministic signature, mixed with the passkey factor if you chose one), and every app ID and pocket follows from it.
4. The SDK re-derives pockets from your visited-app list; the dashboard lets you add any app origin you remember, and looks it up on-chain. That list reveals browsing history even though it contains no identity secret.

Non-deterministic wallets

A small minority of signers randomize signatures. Registration detects this with a double-sign comparison after signature verification and refuses by default. An SDK integrator may explicitly enable allowNonDeterministic, which uses a random secret that must be backed up independently before registration. Re-signing cannot recover that secret. The dashboard does not offer this fallback or an encrypted backup flow.

Emergencies

After recovering the secret, you can generate owner proofs to sweep_home and revoke_session without the old session key. Fetch each pocket's current owner-action nonce before proving. You still need the original factor when applicable, valid registry data, and a relayer or fee payer to submit transactions.