Connecting vs Signing

Connecting shares your public address (low risk). Signing a message proves ownership without moving funds. Signing a transaction or approval can move or spend your assets — review it carefully.

Quick answer

Connecting a wallet is read-only: it shares your public address. Signing a message proves you control the wallet without spending. Signing a transaction or token approval can move or authorize spending your assets. Treat those very differently.

What it means

A connection request is generally low risk. A message signature is usually safe but should still make sense for what you are doing. A transaction signature and a token approval can move funds or grant spending rights — these are the requests attackers abuse.

Why it matters

Wallet drainers rely on users approving dangerous requests out of habit. The challenge below shows realistic but fictional prompts and asks you to classify each by risk, so you build the habit of reading before approving.

What happens if you ignore this

Approve the wrong request and there is no reversal. A single blind 'approve all' on a fake site can hand an attacker permission to move your tokens whenever they like — even days later. The whole skill is pausing to read before you sign.

Safety considerations

No legitimate site ever needs your seed phrase or private key. A request for either is always a scam. Verify the destination, amount, and token on any transaction before you sign.

Story

Devon clicks a link to 'claim a free airdrop.' The site pops a wallet request that looks routine, so he approves it the way he's approved dozens of connections.

He thinks he's just connecting to see his airdrop.

It wasn't a connection — it was a token approval granting the site permission to move his tokens. Hours later, his wallet is emptied.

Connecting and signing look similar in the moment but do completely different things. Read what each prompt actually asks for; only a signature can move funds.

Beginner tips

Common mistakes

Related lessons