A network name in a wallet is a convenient label, while a chain ID is a field used in transaction signing. Ethereum’s EIP-155 specifies how that identifier is included in replay-protected legacy transaction signatures. The goal is to distinguish transactions intended for different chains, not to certify the application receiving the transaction. Ethereum EIP-155: Simple replay attack protection
Follow the evidence
Trace how the event could reach markets, then inspect a competing explanation.
Compare explanations
Switch lenses to see what each account explains—and what remains uncertain.
WFN analysis: imagine an application showing a familiar token symbol after a user changes networks. A matching symbol and address format cannot establish that the underlying token is the same asset. The relevant record includes the selected chain, token contract and intended destination. Chain identification makes the first field explicit; it does not fill in the others. There is a second distinction between replay protection and authorisation quality. A transaction can be correctly bound to the intended chain while granting an unwanted permission on that chain. The signing mechanism answers where that transaction is intended to operate. It cannot determine whether the user understands the action, approves the spender or recognises the actual contract. A support workflow should also avoid assuming that a single transaction identifier tells the whole story across networks. The report needs the network context and an appropriate source for that chain. Looking up a transaction on the wrong explorer can lead to a false conclusion that nothing happened, even when the original report simply omitted the network field.
WFN analysis: imagine an application showing a familiar token symbol after a user changes networks. A matching symbol and address format cannot establish that the underlying token is the same asset. The relevant record includes the selected chain, token contract and intended destination. Chain identification makes the first field explicit; it does not fill in the others. There is a second distinction between replay protection and authorisation quality. A transaction can be correctly bound to the intended chain while granting an unwanted permission on that chain. The signing mechanism answers where that transaction is intended to operate. It cannot determine whether the user understands the action, approves the spender or recognises the actual contract. A support workflow should also avoid assuming that a single transaction identifier tells the whole story across networks. The report needs the network context and an appropriate source for that chain. Looking up a transaction on the wrong explorer can lead to a false conclusion that nothing happened, even when the original report simply omitted the network field.
Before describing a transaction as correctly addressed, identify the intended network, recipient and action separately. When the interaction involves a token, include its contract address rather than relying only on its display name. These are WFN review suggestions built around the standard’s scope, not a guarantee that a particular wallet or application has validated every relevant field. For incident reporting, preserve the chain context, transaction hash and available signing details. State whether the concern involves a legacy transaction, another transaction format or a separate message signature. That narrower description makes technical investigation more useful. EIP-155 explains a specific replay defence; judging a complete user interaction requires evidence about the actual transaction and destination.
The scope of the original specification
EIP-155, created on 14 October 2016, adds chainid and two zero values to the legacy transaction data hashed for signing. Its specification also changes how the signature’s v value encodes the chain identifier. Ethereum mainnet is assigned chain ID 1 in the document. Ethereum EIP-155: Simple replay attack protection
The rationale encourages other networks to choose different identifiers so a transaction intended for one chain is not usable unchanged on another. The document also retains the earlier signature scheme. This article explains that historical legacy-transaction mechanism; it does not claim that every transaction format or signed-message standard is governed solely by EIP-155. Ethereum EIP-155: Simple replay attack protection
A network check is one part of an identity check
WFN analysis: imagine an application showing a familiar token symbol after a user changes networks. A matching symbol and address format cannot establish that the underlying token is the same asset. The relevant record includes the selected chain, token contract and intended destination. Chain identification makes the first field explicit; it does not fill in the others.
There is a second distinction between replay protection and authorisation quality. A transaction can be correctly bound to the intended chain while granting an unwanted permission on that chain. The signing mechanism answers where that transaction is intended to operate. It cannot determine whether the user understands the action, approves the spender or recognises the actual contract.
A support workflow should also avoid assuming that a single transaction identifier tells the whole story across networks. The report needs the network context and an appropriate source for that chain. Looking up a transaction on the wrong explorer can lead to a false conclusion that nothing happened, even when the original report simply omitted the network field.
Make a signing review specific
Before describing a transaction as correctly addressed, identify the intended network, recipient and action separately. When the interaction involves a token, include its contract address rather than relying only on its display name. These are WFN review suggestions built around the standard’s scope, not a guarantee that a particular wallet or application has validated every relevant field.
For incident reporting, preserve the chain context, transaction hash and available signing details. State whether the concern involves a legacy transaction, another transaction format or a separate message signature. That narrower description makes technical investigation more useful. EIP-155 explains a specific replay defence; judging a complete user interaction requires evidence about the actual transaction and destination.