# Raw hash signature (eth_sign)

> A legacy signing method that, as implemented in MetaMask, signed an arbitrary hash with no message prefix. You cannot read what the hash stands for.

- Request: `eth_sign`
- Standard: Legacy JSON-RPC method; discontinued in MetaMask (MIP-3)
- 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/eth-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

- A hex string with no readable meaning. That is the warning sign: the prompt cannot show you what the hash represents.

## What it lets the other party do

- MetaMask’s MIP-3: `eth_sign` “allows blind signing of arbitrary data without the `\x19Ethereum Signed Message` prefix” and “can be used to sign arbitrary hashes, making it possible for attackers to trick users into signing malicious transactions or messages.”

## What it does not do

- It does not tell you what you are approving. Nothing in the prompt describes the action.

## How long it lasts

- Nothing in a raw hash signature sets an expiry. How long it can be used depends on what the hash stands for, which the prompt does not tell you.

## How to undo it

- There is no cancel. If you signed one, treat the account as you would after any unknown signature and check approvals with Revoke.cash or Etherscan’s token approval checker.

## Where it stands

- MetaMask disabled `eth_sign` by default (MIP-3: “As of last year, `eth_sign` was disabled by default”) and MIP-3, created 2024-05-15 and accepted, proposes discontinuing support entirely. MetaMask’s developer docs list it as deprecated. Other wallets may differ.

## Practice question (fictional)

A fictional site asks you to turn on an advanced wallet setting so you can sign a “login code”.

| Field | Value |
| --- | --- |
| Request type | Signature: eth_sign |
| Data | 0x7c1e…a94f (32 bytes of hex) |
| Site says | Login code |

**Question:** Can you tell from this prompt what the signature will authorize?

**Answer:** No. eth_sign signs a raw hash. The hash could stand for a transaction or anything else, and the prompt cannot show which. The site’s label is not part of what you sign.

## Check your real account elsewhere

This site never connects to a wallet or asks for an address. Established tools (independent, not endorsements):

- [Revoke.cash](https://revoke.cash/): shows and removes token approvals across many networks
- [Etherscan token approval checker](https://etherscan.io/tokenapprovalchecker): shows and removes token approvals on Ethereum mainnet

## Sources

- [MIP-3: Discontinuing the eth_sign signature method](https://github.com/MetaMask/metamask-improvement-proposals/blob/main/MIPs/mip-3.md). MetaMask Improvement Proposals. Accepted; created 2024-05-15. 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.
- [ERC-191: Signed Data Standard](https://ercs.ethereum.org/ERCS/erc-191). Ethereum ERCs. Final; created 2016-01-20. Checked 2026-11-04.
