# Message signature (personal_sign)

> A request to sign a readable message. A fixed prefix means the signed data can never be a valid Ethereum transaction.

- Request: `personal_sign`
- Standard: ERC-191 version 0x45; often ERC-4361 sign-in
- Track: Request types
- Checked against sources: 2026-11-04
- Review status: drafted with AI assistance, awaiting human review
- Canonical page: https://walletpermissions.com/learn/requests/personal-sign

Education only. This does not assess any real request, wallet or app, and is not advice to sign or not sign. Every app, token and address in the practice card is fictional.

## What to read in the prompt

- The full message text.
- For Sign-In with Ethereum: the domain, the statement, the nonce and any expiration time.

## What it lets the other party do

- It proves to whoever receives it that your account signed this exact text. MetaMask’s docs say it is “often used for signature challenges that are authenticated on a web server, such as Sign-In with Ethereum.”
- A service or contract can choose to treat the signature as permission for something. What the message says matters.

## What it does not do

- ERC-191 explains that the `0x19` prefix means “any EIP-191 `signed_data` can never be an Ethereum transaction.”
- It does not create an on-chain allowance by itself.

## How long it lasts

- Whatever the receiving service decides. ERC-4361 sign-in messages can include an `Expiration Time`, “the time when the signed authentication message is no longer valid.”

## How to undo it

- There is nothing on-chain to undo. For a sign-in, log out of the service.

## A pattern to recognise

- Readable is not the same as harmless: read what the text says you agree to. No legitimate signature request needs your recovery phrase.

## Practice question (fictional)

Fictional Pebble Pass asks you to sign in.

| Field | Value |
| --- | --- |
| Request type | Signature: personal_sign |
| Message | pebblepass.example wants you to sign in with your Ethereum account. Nonce: 8f2k1. Expiration Time: in 10 minutes. |

**Question:** Could this exact signature be broadcast as a transaction that sends your tokens?

**Answer:** No. personal_sign adds the “\x19Ethereum Signed Message” prefix, and ERC-191 notes that such signed data can never be an Ethereum transaction. It can still be used by the service that asked for it, as a login.

## Sources

- [ERC-191: Signed Data Standard](https://ercs.ethereum.org/ERCS/erc-191). Ethereum ERCs. Final; created 2016-01-20. Checked 2026-11-04.
- [ERC-4361: Sign-In with Ethereum](https://ercs.ethereum.org/ERCS/erc-4361). Ethereum ERCs. Final; created 2021-10-11. Checked 2026-11-04.
- [Sign data (eth_signTypedData_v4 and personal_sign)](https://docs.metamask.io/metamask-connect/evm/guides/sign-data/). MetaMask developer docs. Page as published on the check date. Checked 2026-11-04.
