Wallet login on testnet issue

[defrag]

Summary

Running tempo wallet login --network testnet completes the browser authorization flow, but the CLI remains unavailable on testnet. The same wallet is ready on mainnet. The browser URL does not visibly include a network parameter. It is unclear whether the authorization code carries the requested network server-side.

This prevents paying a Stripe sandbox MPP challenge, because that challenge targets Tempo testnet while the only usable delegated CLI key is registered on mainnet.

Steps to reproduce

1. Start a testnet login:

   tempo wallet login --network testnet

2. Open the generated URL and complete authorization in the Tempo wallet browser UI:

   https://wallet.tempo.xyz/api/auth/cli?code=<redacted>
   

3. Check testnet readiness:

   tempo wallet whoami --network testnet

4. Compare it with mainnet:

   tempo wallet whoami --network mainnet

Actual behavior

Testnet remains unconfigured after the browser flow:

ready: false

Mainnet is ready and returns a delegated key:

ready: true
wallet: <redacted>
key:
  chain_id: 4217
  network: tempo
  status: null

The Tempo testnet wallet UI also shows no connected app or CLI key.

When that mainnet key is subsequently selected while paying a testnet MPP challenge, gas estimation is sent to https://rpc.moderato.tempo.xyz and fails with:

Revm error: keychain validation failed:
AccountKeychainError(KeyNotFound(KeyNotFound))

Logging out, logging in again with --network testnet, refreshing the wallet UI, and repeating the authorization flow produce the same result.

Expected behavior

After successfully completing tempo wallet login --network testnet:

• tempo wallet whoami --network testnet should return ready: true.
• A delegated CLI key should be registered on the testnet chain.
• The key should appear in the testnet wallet UI under connected apps/CLI keys.
• The key should be usable to pay a Tempo testnet MPP challenge.
• Mainnet and testnet login state should remain clearly separated.