Monero GUI

This change fixes a bug in the Monero wallet setup wizard. Previously, when restoring or creating a wallet from seed/keys, the wallet was first saved with a blank or temporary password before the user's chosen password was applied. If applying the real password failed, the wallet file could remain on disk with a weak or empty password. The patch makes the wallet creation functions accept the intended password directly, and aborts the save if the password cannot be set.

This commit updates the Monero GUI wallet's message-signing screen so that when a user verifies a signature, the app now reports extra details: whether the signature is valid, which key type was used (spend key, view key, or unknown), and whether it uses an older signing algorithm. It is a user-interface improvement to reduce confusion, not a fix for a vulnerability.

This change adjusts how the Monero GUI wallet stores and passes login credentials for remote daemon connections. Previously, daemon username/password and 'trusted daemon' status were kept as persistent properties on the wallet object and reused across connections. The patch scopes those credentials to each individual connection instead, passing them as parameters when initializing a connection rather than storing them on the wallet. This reduces the risk that credentials or trust settings from one remote node could accidentally be reused for a different node later.

This commit fixes a display bug in the Monero GUI wallet's transaction history. Previously, when sorting transactions by block height, failed transactions were incorrectly treated like pending ones and shown at the top of the list. The fix ensures only genuinely pending (unconfirmed) transactions float to the top, while failed transactions are sorted by their actual block height like normal. There is no direct evidence this is a security vulnerability—it's primarily a user-experience and accuracy fix.

This commit is a user-interface improvement for the Monero GUI wallet's transaction history screen. It changes how outgoing payments with multiple recipients are displayed, searched, and copied. There is no security vulnerability here; it is a routine feature enhancement.

This update fixes a timing bug in the Monero wallet's send screen. If a user quickly changed or cancelled a payment while a transaction was still being prepared in the background, the wallet could accidentally show or use the wrong transaction details. The fix adds request IDs so the app can tell old, stale transactions apart from the current one and safely discard them. It also cleans up transaction objects when the user rejects a payment, preventing possible crashes or memory waste.

This commit adds a feature that lets users scan a QR code to restore a Monero wallet from its secret keys. The change itself is a feature addition, not a fix for a known vulnerability. There is one minor security-relevant detail: the QR code URI scheme was changed from 'monero_wallet:' to 'monero-wallet:' and a new parser was added. The code validates the wallet address before accepting the QR data, which is good. However, the new parser does not validate the secret view/spend keys or restore height values, so a malformed QR code could at worst cause the restore wizard to receive invalid key strings. There is no evidence in the commit of a disclosed security bug, an exploit, or an attacker-controlled code path.