A stranger wearing a homemade library badge does not automatically get access to the library’s keys.
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.
Start with where the conversation began
An unsolicited private message after a public support question can be an impersonation attempt. A copied name, profile image or logo is easy to reproduce. Establish the organization’s designated support channel independently.
Inspect the requested action
Questions about public transaction data differ from requests for recovery phrases, private keys or remote control of a device. Secret authorization material is not needed to explain a public receipt.
Watch for manufactured urgency
A message may claim funds will vanish unless you immediately “verify” or “sync” a wallet. Urgency can discourage checking the domain and the request. Slow down and verify the channel before following instructions.
Use a safe learning example
If a stranger asks for a phrase to inspect a transaction, the request crosses a clear boundary. Read the recovery-phrase lesson to understand why revealing it can grant access rather than merely share diagnostic information.
QUICK CHECK · NO PRESSURE
Does a matching support avatar prove a message is authentic?
Names and images can be copied. Verify the channel and the actual request.