A lookalike address can be planted where you expect useful history.
LET’S PICTURE IT
An impostor can place a similar-looking contact card next to a trusted one and hope you copy the wrong card later.
SEE IT FOR YOURSELF
From a public address to a verified signatureStep 1 / 4
An address is public receiving information. It is not the private key that authorizes actions.
An address is public receiving information. It is not the private key that authorizes actions.The local signing system uses secret authorization material. It produces a signature; the private key is not sent along with it.A verifier checks the signed request under the account’s rules. A valid signature does not by itself prove that the action is safe.Balances belong to network state. A wallet is an interface and signing system, not a box containing coins.
Animated local teaching model. No wallet, RPC or live blockchain data. Some labels and hashes are abbreviated for readability.
History is not an address book
An attacker can arrange activity or token records involving an address they control. The goal can be to make a lookalike destination appear in a wallet’s recent activity, where a user might later copy it.
Abbreviated displays create an opening
Two addresses can share recognizable starting and ending characters while differing elsewhere. A shortened preview can hide those differences. Passing a format or checksum test does not make the lookalike the intended recipient.
Confirm the intended destination
Use a previously trusted channel to establish the correct full address. Do not promote an unexpected history entry into a trusted recipient simply because it appears near legitimate transactions.
Practice the distinction
The address checker can tell you whether the supplied text has a valid address shape. It cannot establish who controls it. Treat identity confirmation and formatting as separate steps in the payment review.