In this track: Ethereum protocol concepts
advanced · 4 MIN READ

EIP-155 replay protection

Legacy transaction signing can bind a chain identifier.

LET’S PICTURE IT

A payment form can name the jurisdiction where it is intended to be used.

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.

Identify the original replay issue

Without suitable chain binding, a signed transaction can potentially be valid on another chain with compatible state and rules. A network name in a wallet display is insufficient by itself.

Read the legacy mechanism

EIP-155 changes protected legacy signing data and the v interpretation to incorporate chainId. It is a specific transaction-signature convention.

Separate newer transaction formats

Typed transactions define their own field and signing rules. Do not apply the legacy v formula as a universal parser for every signature.

Keep application messages separate

A chain-protected transaction does not automatically protect arbitrary off-chain messages accepted by a contract. Those messages need their own domain and replay rules.

Map the protocol concept

protected legacy signing includes chainId context
typed transactions have their own schema
application signatures need separate domain and nonce rules

A conceptual model. Exact fields, limits and processing rules must be checked against the intended network fork.

QUICK CHECK · NO PRESSURE

Does EIP-155 automatically add replay protection to every off-chain message?

Your progress stays in this browser.
Keep exploring the original referenceEthereum Improvement Proposals ↗

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