Hardware wallet signing from connected wallet

[tupui]

What problem does your feature solve?

Avoid tx bad auth issues.

What would you like to see?

When I have a connected hardware wallet, I already had to specify the path (44'/148'/0'). It should select the proper path automatically.

What alternatives are there?

Do nothing and let people wonder what is going on when they have connected a hardware wallet already and just want to sign something.

[arjunkshah12345-hash]

For automatic hardware-wallet path selection, the safest UX is to make path discovery explicit and verifiable rather than silently guessing:

• Detect the connected device and enumerate supported Stellar/BIP paths; show the selected path and account before signing.
• If multiple paths/accounts are available, require a user choice or a deterministic previously-approved mapping. Never sign using a fallback path that was not displayed.
• Bind the pending signing request to the device fingerprint, derivation path, network, transaction hash, and expiration; reject a response that changes any of those fields.
• Surface distinct states: device missing, device locked, path discovery in progress, address mismatch, user rejected, transport error, and signature received. Preserve the request so retry does not create a different transaction.
• Acceptance tests: reconnect after discovery, two hardware wallets attached, wrong-path address mismatch, device lock/unlock, rejected signature, transport retry, stale request expiry, and successful signing on a non-default 44'/148'/N' path.

A small diagnostic mode that reports discovered public keys and paths without requesting a signature would make the path-selection bug reproducible without exposing private material.