What Is a “Fork” and How Does It Relate to the Potential for Replay Attacks?

A blockchain fork is a split in the network's history, resulting in two distinct chains. When a fork occurs, a valid transaction signed on the original chain might also be valid on the new chain, allowing for a "cross-chain replay attack." This is because the signature is for the same transaction data, which exists on both chains.

Solutions like Ethereum's EIP-155 prevent this by including a unique chain ID in the signed transaction data.

How Do UTXOs in Bitcoin Inherently Prevent a Simple Replay Attack?
What Is a Replay Attack in the Context of a Signed Cryptocurrency Transaction?
How Does a Chain ID Prevent Cross-Chain Replay Attacks after a Fork?
What Are the Differences between Single-Function and Cross-Function Reentrancy Attacks?
How Does the Nonce Relate to Replay Attacks in Smart Contracts?
What Is the Concept of ‘Gas’ and How Does It Relate to Token Deployment Costs on Different Chains?
How Does Cross-Chain Bridging Introduce New MEV Vectors?
How Does a Hard Fork Differ from a Soft Fork in Terms of Network Consensus?

Glossar