In this track: Cryptography with intuition
advanced · 4 MIN READ

Recovering an externally owned signer

Recovery identifies a candidate signer for one digest and signature.

LET’S PICTURE IT

A stamp can be checked against the exact document and expected author.

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.

Hash the intended message

Recovery requires the same digest that was signed. Raw hashing, personal-message hashing and typed-data hashing are different procedures.

Recover under the right convention

A library interprets signature components and recovery information under its supported format. A successful recovered address still needs comparison with the expected authorized signer.

Validate the authorization context

Check the signed action, domain, nonce and expiry rules. Recovering an address alone does not make the requested operation appropriate or prevent replay.

Separate contract-account validation

A contract account can define its own signature policy. EOA recovery by itself is not a general replacement for checking the relevant contract-signature interface.

Inspect the distinction

exact message → correct digest convention
signature + digest → candidate recovered EOA
compare expected signer + enforce action rules

These are local teaching values, not a signature request or a live-chain lookup.

TURN UNDERSTANDING INTO PRACTICEOpen the Keccak-256 →
QUICK CHECK · NO PRESSURE

Is a recovered address alone enough to authorize an arbitrary action?

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.