In this track: Wallets without mystery
beginner · 3 MIN READ

Wallet safety knowledge check

Put account access, networks and permissions into one simple review.

LET’S PICTURE IT

Imagine a visitor asks to see your club membership card, then hands you a separate authorization form. Treat those as different requests.

SEE IT FOR YOURSELF
From a public address to a verified signatureStep 1 / 4
From a public address to a verified signaturePublic address0x0000…0001Share to receiveAnother personCan read the addressCannot sign for youPublic identifier ≠ secret authorizationLocal signerPrivate key stays hereSign the chosen requestSigned requestMessage + signatureSecret key not includedThe moving packet represents a signature, not a keySignatureCheck the exact messageCheck the signing contextVerificationAuthorization checkedIntent still mattersValidity and safety are different questionsWallet interfaceReads public dataRequests authorizationNetwork stateBalances and recordsIndependent verificationNo wallet is connected in this local illustration

An address is public receiving information. It is not the private key that authorizes actions.

Animated local teaching model. No wallet, RPC or live blockchain data. Some labels and hashes are abbreviated for readability.

Scenario one: an account appears

A website asks you to connect an account. That can reveal a public address and network context. It is not the same as signing the site’s next transaction, and public account exposure can still affect privacy.

Scenario two: a tiny value, a large allowance

The site displays a small intended purchase but asks for a much larger approval. Read the spender and allowance rather than judging the request only by the visible payment. Closing the tab afterward does not erase an onchain approval.

Scenario three: a missing balance

After changing networks, your balance display changes. First check chain, account and asset identity. Switching a network is not a bridge, and an address shared across chains does not create a shared balance.

Scenario four: a helpful stranger

Someone claiming to be support asks for a phrase to “refresh” the account. Do not provide it. A public receiving address is enough for many diagnostic conversations; secret key material gives authorization, not just information.

QUICK CHECK · NO PRESSURE

Which action revokes an ERC-20 allowance by itself?

Your progress stays in this browser.
Keep exploring the original referenceethereum.org ↗

Original explanations by EtherTools. Examples are educational and source-linked; this site is independent of the Ethereum Foundation. Our approach.