Dev Multi-User Wallet Testing

Why this exists

Private send/receive UX needs at least two users to test contact selection, request links, and private transfers end to end.

The wallet dev login flow supports multiple local dev identities via environment keys and a profile picker on /login.

Configure dev users

In apps/wallet/.env.local, set:

DEV_PRIVATE_KEY=0x...            # existing default profile (Satoshi)
DEV_PRIVATE_KEY_ALICE=0x...      # optional Alice profile
DEV_PRIVATE_KEY_BOB=0x...        # optional Bob profile

Notes:

• DEV_PRIVATE_KEY is still used as the deployer and default profile source.
• DEV_PRIVATE_KEY_ALICE / DEV_PRIVATE_KEY_BOB add selectable profiles in dev login.
• Restart the wallet dev server after env changes.

Login as different users

1. Open http://localhost:3006/login.
2. Click Dev Login (choose user).
3. Select Satoshi, Alice, or Bob.

If a selected profile has no existing wallet identity yet, wallet provisioning runs automatically for that profile.

Recommended local test flow

1. Log in as Alice.
2. Open Receive and copy/share Alice stealth meta-address.
3. Log out, log in as Bob.
4. Add Alice as a contact.
5. Send a private transfer to Alice (st: flow).
6. Verify:
   • Send contact selection works
   • Receive request/share flows prefill correctly
   • Recent activity and note updates appear for both users

Troubleshooting

• No profiles listed in dev picker
  • Ensure env keys are present in .env.local.
  • Restart apps/wallet dev server.
• DB unavailable during dev login/register
  • Start local Postgres/Docker services and retry.
• Profile logs into wrong account
  • Clear browser session/local storage for wallet app and re-run dev login.