Practice identifying what a request actually grants.
LET’S PICTURE IT
You can rehearse decisions using fictional situations before a real interface puts you under pressure.
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.
Scenario: the urgent helper
A stranger offers to repair a missing balance if you provide a recovery phrase. The requested capability is account restoration, not merely viewing public data. Verify support independently and do not disclose that secret.
Scenario: the familiar address
A recent-history destination matches the first and last few characters of a trusted contact. That is incomplete evidence. Confirm the full intended destination and network rather than relying on the abbreviated preview.
Scenario: the zero-cost signature
A site says a message is free because signing uses no immediate gas. Determine what the signature authorizes and where it can be used. No immediate fee does not mean no effect.
Scenario: the disconnected app
You close a site after granting a token allowance. The interface connection changed; the contract permission may remain. Review approvals separately from browser connection state.
QUICK CHECK · NO PRESSURE
Which is a meaningful distinction?
Connection, signatures, allowances and transfers are different capabilities with different lifetimes.