# Approve an Ethereum test message with WalletConnect

[Read this guide on KeySigner](https://keysigner.io/integrations/guides/sign-an-ethereum-test-message/)

Connect an Ethereum test account, review the exact message on your phone, and verify the signature in the app that requested it.

## Before you start

**KeySigner on iPhone and a WalletConnect-enabled test app**

- Use an Ethereum key in KeySigner and a test app that offers WalletConnect on a network KeySigner can use. The test app needs a way to verify the signature against the account you select.

## Data and access

- **Shared or checked**. The requesting app supplies a plain-text test message and receives a signature for the selected address if you approve.
- **Check separately**. Transaction signing is a separate action. A fixed test message should stay out of an authentication flow.

## 1. Prepare a test app

Use a WalletConnect app you control on a supported test network, such as Sepolia. It needs to request a plain-text signature and verify which address signed it. Choose a KeySigner Ethereum test account with no real funds.

**Check.** The verifier has the intended test address and the exact plain-text message it will check.

## 2. Share just the test account

Choose WalletConnect in the test app. In KeySigner, open Accounts, tap Add (+), then choose Connect a dapp. Scan or paste the code. Compare the domain and network with the test app before sharing the account.

**Check.** The test app receives the one address you selected. KeySigner lists the session under the expected domain.

## 3. Review and approve the message

Ask the test app to sign a message you wrote, such as KeySigner test only. Keep KeySigner open and find the request in Inbox. Check the requesting site and exact text before approving.

**Check.** The Inbox request displays the same website and message. The test app receives a signature only after approval.

## 4. Verify and end the session

In the test app, verify the signature against the original message and the selected address. In KeySigner, return to Connected apps and disconnect the test session.

**Check.** The verifier accepts the original message for the chosen address and rejects a changed message. The session disappears from Connected apps.

![KeySigner Connect a dapp screen with options to scan a QR code or paste a WalletConnect code.](https://keysigner.io/integrations/guides/sign-an-ethereum-test-message/keysigner-walletconnect.png)

Open Connect a dapp to scan the QR code or paste the pairing code.

## Check your result

The app verifies the test address as the signer. Change one character of the message and check that the same signature fails verification. A plain-text test message creates no on-chain transaction.

[How to verify your setup](https://keysigner.io/integrations/verify-a-setup/)

## If you get stuck

### The connection works but the request does not appear

Check that the app is requesting a plain message signature from the address you shared. Reopen KeySigner, confirm that the session is active, and retry from the same test app.

## Tools in this guide

- [Ethereum](https://keysigner.io/integrations/ethereum/)
  - [Review transaction fields, signatures and fees](https://ethereum.org/developers/docs/transactions/)
  - [Setup requirements](https://keysigner.io/integrations/setup-requirements/#ethereum)
- [WalletConnect](https://keysigner.io/integrations/walletconnect/)
  - [Check what a wallet can verify before connecting](https://docs.walletconnect.com/wallets/ios/verify)

## Setup instructions

- [Review how Ethereum message signatures work](https://eips.ethereum.org/EIPS/eip-191)

[More guides for this task](https://keysigner.io/integrations/tasks/check-key-approval/)
