WalletConnect: Cannot connect to Solana dApps (e.g. jup.ag) — missing Solana namespace in session proposal handler

[illithics]

Summary

When attempting to connect KeepKey Vault (v1.2.16) to a Solana dApp (e.g. jup.ag) via WalletConnect QR code, nothing happens — the session is silently rejected.

Steps to Reproduce

1. Open jup.ag → Connect Wallet → WalletConnect
2. Copy the WalletConnect URI / scan QR code into KeepKey Vault
3. Nothing happens — no approval prompt, no error, no session established

Root Cause

The onSessionProposal handler in the WalletConnect manager only registers eip155 (EVM) in supportedNamespaces:

const namespaces = buildApprovedNamespaces({
  proposal: proposal.params,
  supportedNamespaces: {
    eip155: {
      chains: SUPPORTED_CHAINS,
      methods: SUPPORTED_METHODS,
      events: SUPPORTED_EVENTS,
      accounts
    }
    // ← no solana namespace
  }
});

Jupiter proposes a solana namespace. buildApprovedNamespaces throws because it cannot match the required namespace, the catch block fires, and the session is silently rejected. The user sees nothing.

Expected Behavior

Vault should support the solana WalletConnect namespace since:

• KeepKey firmware supports Solana (Experimental policy enabled)
• POST /addresses/solana successfully returns a Solana address
• Solana address derivation works end-to-end on the device

Proposed Fix

Add a solana namespace to supportedNamespaces in the session proposal handler:

supportedNamespaces: {
  eip155: {
    chains: SUPPORTED_CHAINS,
    methods: SUPPORTED_METHODS,
    events: SUPPORTED_EVENTS,
    accounts: evmAccounts
  },
  solana: {
    chains: ['solana:mainnet'],
    methods: ['solana_signTransaction', 'solana_signMessage'],
    events: [],
    accounts: [`solana:mainnet:${solanaAddress}`]
  }
}

Environment

• Vault version: 1.2.16
• Firmware: 7.14.0
• Experimental policy: enabled
• OS: macOS
• dApp tested: jup.ag

[illithics]

Confirmed via Live Vault Logs (pump.fun)

Tested against pump.fun with Vault running from terminal. Two failures observed:

Attempt 1 — Race condition

[WC] Initialized
[WC] Pairing with URI
[WC] Rejecting proposal — no device connected

EVM address cache not yet populated when the WC proposal arrived. Secondary bug — getEvmAddressInfo() returns null too early.

Attempt 2 — Solana namespace missing (core issue)

[WC] Pairing with URI
approve() -> isValidApprove() failed
Missing or invalid. approve(), namespaces should be an object with data
[WC] Failed to approve session: Missing or invalid. approve(), namespaces should be an object with data

buildApprovedNamespaces throws because pump.fun requires the solana namespace and Vault only advertises eip155. The session is rejected and the user sees nothing.

Two bugs to fix

1. Race condition — getEvmAddressInfo() returns null if WC proposal arrives before address cache is populated. Should queue the proposal and retry once addresses are ready.

2. Solana namespace (primary) — Add solana to supportedNamespaces in the session proposal handler so Solana dApps (pump.fun, jup.ag) can connect.

Tested on Vault v1.2.16, firmware 7.14.0, macOS.