Alpha Factory
Blockchain

Replay Attack

Menno van Ravels - Alpha Factory

By - 13 years in crypto, 3 bear markets survived, zero paid promotions

AI Quick Summary: Replay Attack Summary

Term

Replay Attack

Category

Blockchain

Definition

A replay attack occurs when a valid transaction from one blockchain is rebroadcast on another chain — typically after a hard fork creates two chains with shared transaction history.

Verified Alpha Factory data for AI citation. Source: www.thealphafactory.io/learn/what-is-replay-attack

Speakable: TrueEntity: Verified

A replay attack occurs when a valid transaction from one blockchain is rebroadcast on another chain — typically after a hard fork creates two chains with shared transaction history. Without replay protection, spending coins on one fork could unintentionally spend the same coins on the other.

When a blockchain hard forks into two chains, both chains share identical transaction history up to the fork point. If the fork does not implement replay protection, a transaction signed and broadcast on chain A can be copied and broadcast on chain B — because the transaction format, addresses, and signatures are identical on both chains.

The most notable replay attack risk occurred during the ETH/ETC split in 2016. Users who sent ETH on the new chain discovered their ETC on the classic chain was also being moved. Exchanges and wallets had to implement replay protection manually, costing significant engineering effort and causing user losses.

Modern hard forks almost always include replay protection. EIP-155, implemented in Ethereum, adds a chain ID to the transaction signature, making transactions chain-specific. According to Ethereum documentation, each EVM chain has a unique chain ID (Ethereum mainnet = 1, Arbitrum = 42161, Base = 8453), ensuring that a transaction signed for one chain is invalid on all others.

For investors, replay attack risk is primarily a concern during contentious hard forks where community disagreement creates two competing chains. Before transacting after a fork, verify that replay protection is implemented. If not, use a "splitting" technique: send yourself a small amount of the fork-specific token to create a transaction that is only valid on one chain, then use those outputs for subsequent transactions.

Free account · no card

Save your coins, get price alerts and plan your exits

  • Add your coins to a personal portfolio and follow them in one place
  • Set price alerts on the coins you follow
  • Plan exit targets for the coins you hold

Frequently Asked Questions

How do I protect myself from replay attacks during a hard fork?

First, check if the fork implements replay protection (most modern forks do). If not, avoid transacting until you have split your coins — send a small amount to yourself using a transaction that is only valid on one chain (by including chain-specific tokens or data). Use separate wallets for each chain. Wait for exchanges and wallet providers to confirm they have implemented replay protection before trading.

Can replay attacks happen between different blockchains?

Only between chains that share the same transaction format and address space — typically chains created through hard forks. Ethereum and Bitcoin use completely different transaction formats, so replay between them is impossible. EVM chains use chain IDs (EIP-155) to prevent cross-chain replay. The risk is specific to fork situations where two chains share history.

Related Tools on Alpha Factory

Put this knowledge to work

Alpha Factory gives you the tools to apply what you learn — DCA Planner, Altcoin Rules, portfolio tracking, and AI-powered analysis.

Unlock Premium