feat(wallet): differentiate between transaction and message in KeystoneProvider.tsx

[Copilot]

Description of change

The Keystone signing dialog displayed "Confirm Transaction" regardless of whether the user was signing a transaction or a personal message (e.g., dApp login). This PR adds signature type awareness to show the appropriate header.

Changes:

• Add SignatureType enum (Transaction | Message) to KeystoneProvider.tsx
• Extend requestSignature to accept optional signatureType parameter (defaults to Transaction)
• Update ScanBothWays component to render "Confirm Message" or "Confirm Transaction" based on type
• Update KeystoneSigner to pass SignatureType.Message in signMessage() and SignatureType.Transaction in signTransactionBytes()

Links to any relevant issues

Fixes #6401

How the change has been tested

• Basic tests (linting, compilation, formatting, unit/integration tests)
• Patch-specific tests (correctness, functionality coverage)
• I have added tests that prove my fix is effective or that my feature works
• I have checked that new and existing unit tests pass locally with my changes

Change checklist

• I have followed the contribution guidelines for this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• downloads.sentry-cdn.com
  • Triggering command: /usr/local/bin/node node ./scripts/install.js (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Wallet: differentiate between transaction and message in KeystoneProvider.tsx</issue_title>
<issue_description>## Description

The header

iota/apps/wallet/src/ui/app/components/keystone/KeystoneProvider.tsx

Line 134 in c45a160

<Header title="Confirm Transaction" titleCentered onClose={() => onCancel()} />

has Confirm transaction hardcoded, however this component is also used when signing a message (for example to login into a dApp) instead of a transaction. In this case it shouldn't mention transaction

Motivation

Make it clear that a message and not a transaction is signed for the case where it's a message.
</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes Wallet: differentiate between transaction and message in KeystoneProvider.tsx #9448

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

6 Skipped Deployments

Project	Deployment	Preview	Comments	Updated (UTC)
apps-ui-kit	Ignored	Preview		Nov 27, 2025 9:48am
apps-backend	Skipped			Nov 27, 2025 9:48am
iota-evm-bridge	Skipped			Nov 27, 2025 9:48am
iota-multisig-toolkit	Skipped			Nov 27, 2025 9:48am
rebased-explorer	Skipped			Nov 27, 2025 9:48am
wallet-dashboard	Skipped			Nov 27, 2025 9:48am

[marc2332]

Nice Job @copilot