Skip to content
INTERN STATUS

Wallet basics

Wallet Signature vs Transaction: What You Are Actually Approving

A transaction changes the blockchain and costs gas. A signature does not, but some signatures still authorise token transfers. How to tell them apart.

By SATOSHI'S INTERN Editorial DeskPublished 14 MIN READFacts checked

Part of What Is a Crypto Wallet? Keys, Not Coins

A transaction is a signed instruction that your wallet broadcasts to the blockchain: it changes state, such as moving tokens or granting an approval, and it costs a network fee. A signature request only asks your wallet to sign some data and hand the signature back to the website, with nothing sent onchain and no fee. That does not make every signature harmless: a login message proves you own an address, while a permit signature can authorise someone to spend your tokens later.

What matters is what the request authorises, and for whom. The wallet prompt tells you, once you know how to read it. If keys and signing are new to you, what a crypto wallet actually holds is the place to start.

What your wallet can ask you to sign on Ethereum

On Ethereum and other EVM chains, a website talks to your wallet through a handful of standard requests. Three matter for everyday use, and a fourth is a legacy method to refuse.

personal_sign: plain text (EIP-191)

personal_sign asks you to sign a readable message. Before signing, the wallet adds a prefix, \x19Ethereum Signed Message:\n followed by the message length. MetaMask's documentation describes the point of this: it "prepends a safe prefix to the signed message to prevent the challenge tricking users into signing a financial transaction."

The prefix works because of how Ethereum encodes transactions. EIP-191 explains that the leading 0x19 byte guarantees the signed data is not valid RLP, so "any EIP-191 signed_data can never be an Ethereum transaction." Sign-In with Ethereum uses this method.

The prefix only guarantees that the signature cannot be replayed as a transaction. The data after it "can be any arbitrary data", in EIP-191's words, and what a website or contract later accepts the signature as is up to them. So a personal_sign request is only as safe as the text you can read. If it shows a meaningless hex string instead of words, you cannot tell what it will be used for.

eth_signTypedData_v4: structured data (EIP-712)

EIP-712 was written because, in its words, "signed messages are an opaque hex string displayed to the user with little context about the items that make up the message." Typed data gives each signature a domain (fields such as the app's name, version, chain ID and the contract that will verify it) and a set of labelled fields. MetaMask renders those fields for you, and notes that this kind of signature "can be verified onchain".

Onchain verification is what makes typed data useful, and what makes it risky. Many apps use it to collect off-chain authorisations that a contract will later act on: marketplace listings, orders, gasless approvals.

eth_sendTransaction: a transaction

eth_sendTransaction asks the wallet to create, sign and broadcast a transaction from your account. ethereum.org describes transactions as "cryptographically signed instructions from accounts" with fields such as the recipient, the value, input data and gas limits. The wallet returns a transaction hash, and the change lands onchain once the transaction is included in a block. A transaction can send ETH, call a contract, or grant a token approval: the input data decides which.

eth_sign: the legacy method

eth_sign signs raw data without the prefix. MetaMask has deprecated it; its improvement proposal MIP-3 says it "allows blind signing of arbitrary data without the \x19Ethereum Signed Message prefix, posing a significant phishing risk."

Table: What each request can do

RequestSent onchain?Fee?Can assets move?
personal_sign, e.g. a SIWE loginNoNoNot by itself, if it is a readable login
eth_signTypedData_v4NoNoYes, if it is a permit, Permit2, order or listing
eth_sendTransactionYesYesYes: sends, swaps, approvals, NFT transfers
eth_sign (legacy)NoNoPotentially; deprecated in MetaMask
Solana messageNoNoNot by itself
Solana transactionYesYesYes

A typed-data signature does not go onchain when you sign it. Someone else submits it later, and that is when assets can move.

Signatures that can move your tokens

The dangerous signatures are the ones a contract will accept as a permission slip.

EIP-2612 permit. An ordinary ERC-20 approval is a transaction. EIP-2612 adds a permit function so that token holders can "modify the allowance mapping using a signed message" instead. You sign typed data with five fields: owner, spender, value, nonce and deadline. Whoever holds that signature can submit it to the token contract, and the spender then has an allowance over your tokens.

The EIP is candid that the intended party is not the only one who can submit it: "another party can always front run this transaction".

A permit request in your wallet looks roughly like this:

Domain:   Example Token, version 1, chain 1
Type:     Permit
owner:    0x073eE65DeB5484113d22dda620Be3cC51A2087e6
spender:  0x... (the address that will be allowed to spend)
value:    115792089237316195423570985008687907853269984665640564039457584007913129639935
nonce:    0
deadline: 1800000000

That enormous value is the maximum possible number (2^256 − 1), which in practice means "unlimited". The deadline is a Unix timestamp; 1800000000 falls in January 2027.

Permit2. Uniswap's Permit2 contract extends the idea to any ERC-20 token, "even those that do not support EIP-2612". You first approve the Permit2 contract through the token contract, which is a normal onchain approval.

From then on, apps can request signatures that either set an allowance through Permit2 for "a specified amount for a specified duration of time" (the PermitSingle and PermitBatch messages) or authorise a one-time transfer (PermitTransferFrom and PermitBatchTransferFrom).

MetaMask's signature-phishing page warns that the act of signing is "not recorded on chain", and that if the approval stays valid for weeks, the attacker can steal the assets later.

Listings and orders. Marketplace listings are often signatures too. MetaMask describes fake bulk-listing "Root" messages, imitating an NFT marketplace, that let attackers withdraw all the NFTs in an account.

revoke.cash names the trap: a permit request "may look like you're simply signing into a website, but you're actually granting an approval." A signed permit that has not been used yet does not show up as an onchain approval, so you cannot revoke it the normal way. Once it is submitted, it becomes an ordinary approval that you can revoke, if anything is left.

How drainers use these requests, and how to clean up afterwards, is in how to spot a wallet drainer.

EIP-7702 authorisations. Since Ethereum's Pectra upgrade (activated 7 May 2025), an ordinary account can delegate itself to smart-contract code via a signed authorisation.

EIP-7702 is blunt about it: "There is no safe way to provide this interface. The code specified by an authorization has unrestricted access to the account." It says applications "must not" expect to suggest that users sign an authorisation, and that it is the wallet's duty not to provide an interface for it. Treat a website asking you to sign one as hostile.

What a Sign-In with Ethereum (SIWE) message says

Sign-In with Ethereum (SIWE, EIP-4361, status Final) is the standard login message. It is plain text signed in the EIP-191 format (the personal_sign prefix), and it has a fixed layout so that wallets can parse it and check it.

Here is an example using made-up values for a site at example.com. It leaves out the optional scheme; EIP-4361 also allows the first line to start with one, as in https://example.com wants you to sign in with your Ethereum account:.

example.com wants you to sign in with your Ethereum account:
0x073eE65DeB5484113d22dda620Be3cC51A2087e6

Sign in to Example.

URI: https://example.com
Version: 1
Chain ID: 1
Nonce: 4f9c2a7e81b3d6a0
Issued At: 2026-09-29T12:00:00Z
Expiration Time: 2026-09-29T12:10:00Z
Request ID: 7c1e5b2a

Table: SIWE fields, line by line

LineWhat it meansWhat to check
example.com wants you to sign in…The site requesting the sign-in (a scheme such as https:// may come first)Exactly the site you meant to visit
0x073e…87e6The account doing the signingThat it is your address
Sign in to Example. (optional)A one-line, human-readable statementThat it says what you think you are doing
URI:The resource the sign-in is forSame site as the first line
Version:Always 1Nothing
Chain ID:The network the session is bound to (1 = Ethereum mainnet)A chain you recognise
Nonce:A random one-time value, at least 8 alphanumeric characters, that stops replayThat it looks random
Issued At:When the message was createdRoughly now
Expiration Time: (optional)When the signature stops being validA short window is a good sign
Not Before: (optional)When it starts being validRarely used
Request ID: (optional)An identifier for this requestNothing
Resources: (optional)URIs the site wants resolved as part of sign-inAnything unexpected

A SIWE message cannot be turned into a transaction, and signing it costs nothing. What happens afterwards is separate: if the site then wants a transaction or a permit, your wallet has to show you a new, different request.

How to read the domain line

The first line is the one that matters most. It names the site that will receive your signed login.

  • Compare it with the site you intended to visit, not only the tab. A phishing site can honestly put its own domain in the message. examp1e.com or example.com.login-verify.io is a different site.
  • Read the host from the right. In app.example.com, the site is example.com. In example.com.evil.io, the site is evil.io.
  • Take wallet warnings seriously. EIP-4361 says wallets "MUST prevent phishing attacks by verifying the origin of the request against the scheme and domain fields". Implementations differ. As of September 2026, MetaMask's developer docs say it shows a prominent warning when the domain does not match the site "but does not block users from bypassing the warning", while Phantom's docs say a mismatched Sign In With Solana message returns an error "without prompting the user".

SATOSHI'S INTERN's own wallet sign-in works this way. Its message begins https://satoshiintern.com wants you to sign in with your Ethereum account: (the explicit-scheme form), carries a one-time nonce and a short expiration time, and names chain ID 1 (Ethereum mainnet) or 8453 (Base). You sign it, nothing is sent onchain, and there is no gas.

Solana: signing in and signing messages

Solana wallets draw the same line. Phantom's developer documentation: "Message signatures do not involve network fees and are a convenient way for apps to verify ownership of an address." A transaction, by contrast, pays a base fee of 5,000 lamports per signature, plus an optional prioritization fee.

Phantom announced its support for Sign In With Solana (SIWS) in August 2023, describing it as "Inspired by EIP-4361". Its signIn method "shifts the responsibility of message construction from apps to the wallet": the app passes the fields, and Phantom builds the message and can check the domain and issue time itself. The reading rules above apply unchanged: domain first, then address, then statement.

Gas is for transactions

Gas is the fee for computation on Ethereum. You pay it only when a transaction is included onchain: the fee is the gas used multiplied by the base fee plus a priority tip, and the base fee is burned. A plain ETH transfer uses 21,000 gas. ethereum.org notes the fee "is paid regardless of whether a transaction succeeds or fails" once it is executed.

That gives you a quick diagnostic. A prompt that shows a network fee is a transaction. A prompt with no fee is a signature, which tells you it is free to sign, not that it is safe. Permits exist precisely so that someone else can submit them later and pay the gas themselves; EIP-2612's motivation cites the "long outstanding goal" of letting users interact with Ethereum "without holding any ETH".

Before you click sign

  1. Check the site. Look at the domain in the address bar and, for sign-in messages, the first line of the message. Both should be the site you meant to use, reached from a bookmark or a link you trust.
  2. Identify the request type. A fee means a transaction. Readable text without a fee is a message. Labelled fields with a domain block are typed data.
  3. For text messages, read every line. A login says so. If you see hex instead of words, reject it.
  4. For typed data, look for spending words. Permit, spender, value, amount, deadline, expiration, Permit2's PermitSingle, PermitBatch, PermitTransferFrom or PermitBatchTransferFrom, an order or a listing: this is a spending permission, however friendly the button.
  5. For transactions, read the simulated result. If the wallet shows assets leaving and you expected to receive something, believe the preview, not the website.
  6. Match the action to the request. Logging in needs a message. Claiming, minting or swapping may need a transaction. A login that asks for a permit or an approval is a mismatch; close the tab.
  7. Never sign an EIP-7702 authorisation from a website, and never sign legacy eth_sign requests.
  8. On a hardware wallet, read the device screen, not just the computer. If the device cannot show the details, you are blind signing.
  9. When in doubt, reject. A rejected signature costs nothing. Look up the site and try again later.

Backups, approval reviews and the rest of wallet hygiene are in the crypto wallet security checklist.

FAQ

Does signing a message cost gas?

No. Signing happens inside your wallet and nothing is broadcast, so there is no network fee. Only transactions pay gas.

Is it safe to sign a message in MetaMask?

It depends on the message, not the wallet. A readable sign-in from the site you meant to visit is routine. Hex you cannot read, typed data with spending fields such as a permit, or an EIP-7702 authorisation can cost you tokens, and MetaMask warns on a SIWE domain mismatch but lets you click past the warning.

What is the difference between signing and approving a token?

A classic ERC-20 approval is a transaction that sets an allowance onchain. A permit sets the same kind of allowance with a signature instead, and the allowance only appears onchain when someone submits it.

Sources

No transaction required. The intern only needs a signature.

GET YOUR INTERN ID

Educational content, not financial, legal or tax advice. Nothing here says any asset will go up. Crypto is risky — read the Risk Disclosure.