Network Mismatch Warning for Wallet-dApp Interactions

[Nuel-osas]

Problem

Currently, when a dApp runs on testnet but the IOTA wallet is configured for mainnet (or vice versa), users encounter an unhelpful error message:

"package id does not exist"

This error doesn't explain the actual problem (network mismatch) and creates confusion, especially for developers testing dApps across different networks.

Current Behavior

Example scenario:

1. Wallet is set to mainnet
2. User connects to a testnet dApp
3. User attempts a transaction
4. Error: "package id does not exist"
5. No indication that the issue is a network mismatch

Proposed Solution

Implement cross-network transaction execution with explicit user consent, similar to Sui Wallet's approach:

Proposed Flow

1. Wallet detects network mismatch
   (Wallet: mainnet, dApp: testnet)
2. Display clear warning:
   "This app is running on testnet, but your IOTA wallet is set to mainnet.
   If you wish to proceed, this transaction will process on testnet."
3. User chooses:
   - Reject transaction
   - Approve transaction
4. If approved:
   - Wallet fetches package ID from testnet (dApp's network)
   - Transaction executes on testnet
   - Wallet global network setting remains mainnet

Key Features

✅ Clear communication - Users understand what's happening
✅ Seamless developer experience - Test on testnet without switching wallet network
✅ No context switching - Wallet stays on preferred network
✅ Multi-network workflows - Interact with multiple networks in one session
✅ Explicit consent - User approves each cross-network transaction
✅ Industry proven - Sui Wallet successfully implements this pattern

Benefits

For Developers:

• Test testnet dApps without constantly switching wallet network
• Faster development iteration
• Reduced friction in multi-network testing

For Users:

• Clear, actionable error messages instead of cryptic failures
• Better understanding of network context
• Reduced support tickets

For the Ecosystem:

• Improved UX parity with other major blockchains
• Lower barrier to entry for new developers
• Professional polish

Reference Implementation

Sui Wallet implements this behavior successfully. When their wallet is on mainnet and a user interacts with a testnet dApp:

1. Warning is displayed
2. User can approve the transaction
3. Transaction executes on testnet (fetches package ID from testnet)
4. Wallet remains on mainnet globally

This has proven to work well in production.

Technical Considerations

The implementation would require:

• Multi-network RPC connection management
• Network detection from dApp connection requests
• Cross-network package ID resolution
• Clear security boundaries and user consent flow

---

Context: I encountered this issue while testing dApps as a dev and noticed that Sui Wallet handles this scenario much more gracefully. I believe IOTA could benefit from a similar UX improvement.

[begonaalvarezd]

A new version of the wallet and the dapp-kit npm package has been released (see PR iotaledger/iota#8619) to allow dapps to use the current chain when requesting tx signing to the wallet.

Closing discussion since now this issue is fixed. Please reopen if necessary.

Thank you 🌷