Glossary
A replay attack on a forked chain is when a transaction you sign on one chain is rebroadcast and accepted on the other. Two chains sharing history and address formats means one signature can spend coins on both - unless the fork added replay protection.
A replay attack happens after a blockchain splits in two. If both chains share the same transaction format and the same address history, a transaction signed on one chain can be rebroadcast on the other and accepted as valid. You meant to move coins on the new chain only; the same signature also moves the matching coins on the old chain. The attack is not theft in the hacking sense - it is one signature being valid in two places at once.
The fix is replay protection: a fork adds a marker to its transactions so the old chain rejects them and vice versa. Not every fork adds it on day one, which is why the weeks after a split are the dangerous ones. For Australian readers, the ATO treats both sides of a split as separate CGT assets, so a replayed spend is a disposal you did not intend, on a coin you meant to keep.
Walk one split. A chain hard forks - the hard-fork entry covers the mechanics - and every address that held coins before the split now holds matching balances on both sides. You decide to sell your coins on the new chain and keep the old side. You sign a transaction moving 10 coins to an exchange, and the transaction lands. But if the two chains share a transaction format, the same signed transaction can be rebroadcast on the old chain, where it is also valid: the matching 10 old-side coins move too.
The attack needs no thief with your keys - your own signature is the problem, valid in two places. Protection comes from the fork: adding a chain identifier or a signature format change so transactions on one side fail validation on the other. Bitcoin Cash added replay protection to its signature scheme after the 2017 split; Ethereum forks adopted chain ID protections in later splits.
The practical defence for a holder is timing and structure: wait until the ecosystem standardises replay protection, move coins with fresh addresses on one chain only, and never reuse addresses across both sides until the formats diverge. The transaction-signing entry covers what a signature commits you to.
For an Australian reader, replay attacks are a niche risk with a real tax sting. The ATO's chain-split guidance treats both sides of a fork as separate CGT assets with their own cost bases - the hard-fork entry covers the cost-base rules. A replayed transaction is a disposal on the side you meant to keep, recorded on the chain whether you intended it or not.
A colleague named Brent (yes, that Brent) sold one side of a fork in the first week after the split, before replay protection was standard, and discovered the matching old-side coins had moved too. The exchange was fine; his plan to hold the other side was not. The highest-leverage thing most Australians can do during a split is wait for replay protection to be standard before moving coins, keep the two sides in separate addresses, and record both sides' cost bases per the crypto-record-keeping entry from day one.
A chain splits and your 10 coins become 10 on each side. In the first week, before replay protection is standard, you sell the new side: 10 coins move to an exchange for $4,000 AUD. The same signature is rebroadcast on the old chain, where it is also valid, and the matching 10 old-side coins move to the same exchange address. You meant to keep those. One signature, two chains, and the side you meant to hold is gone.
A later fork ships with a chain identifier baked into every transaction's signature. You move 10 coins on the new side, and the transaction lands. The same signature rebroadcast on the old chain fails validation, because the chain ID does not match - the fork's protection is doing its job. The old-side coins stay put, and you can decide their fate deliberately rather than discover it on a block explorer.
The ATO treats both sides of a split as separate CGT assets. Your replayed spend on the old side is a disposal at market value on that date: if the old-side coins were worth $3,500 AUD, that is a $3,500 disposal against your proportional cost base. Unintended, but still recorded - the transaction-id entry anchor for it sits on the old chain. Record both sides from the split onward, or the reconciliation gets expensive at tax time.
Mistake: Moving coins immediately after a split, before replay protection is standard.
Why it bites you: The first weeks are when one signature can spend both sides. Waiting for protection to standardise is the free defence that Brent skipped.
Mistake: Reusing the same addresses on both sides of a fork.
Why it bites you: Shared addresses are what make one signature valid in two places. Separate addresses per side break the link until the transaction formats diverge.
Mistake: Not recording both fork sides as separate CGT assets.
Why it bites you: The ATO treats each side as its own asset with its own cost base. A replayed spend is a disposal on the side you meant to keep, and it lands in your tax year regardless of intent.
Mistake: Assuming a replay attack requires stolen keys.
Why it bites you: Your own valid signature is the problem, rebroadcast to a chain that also accepts it. Key security is separate - the [seed-phrase entry](/glossary/seed-phrase/) covers that layer.
I spent a weekend reading through the replay-protection changes that the major forks shipped after their splits so you don't have to, and the pattern is consistent: the dangerous window is the first weeks, when the two chains still speak the same transaction language and one signature works on both. Every fork eventually adds protection, because without it the chaos is unmanageable.
The advice I actually use during a split is boring: do nothing for a fortnight. Let the exchanges sort their support, let replay protection standardise, then move each side with fresh addresses and a small test transaction. I ran the numbers on Brent's week-one sale and the cost was not the coins - it was the CGT event on a side he meant to hold, which is the most expensive kind of accidental trade there is. Forks are chaos by default. Wait out the chaos.
It is when a transaction you signed on one chain is rebroadcast and accepted on another chain after a fork. One signature becomes valid in two places, so coins can move on both sides when you only meant to move one.
Wait until replay protection is standard on both ecosystems, keep the two sides in separate addresses, and make a small test transaction before moving sizeable funds. The ATO treats both sides as separate assets, so record both from day one.
Not on day one. Bitcoin Cash added protection after its 2017 split, and later Ethereum forks used chain IDs, but the first weeks after any split are the risk window. Check the fork's documentation before moving coins.
Generally yes. The ATO treats both sides of a fork as separate CGT assets, so a replayed spend is a disposal at market value on the side you meant to keep. Record the transaction ID as your evidence.
In practice, no - the attack needs two chains sharing history and transaction formats, which is the fork situation. Separate chains with different formats do not accept each other's signatures.
Disclaimer: This information is general in nature and does not constitute financial or legal advice. Always consult a qualified professional for your specific situation.

Financial Chaos Analyst
Ivy Sinclair-Wren is a Financial Chaos Analyst covering crypto markets, investing behaviour, and the Australian habit of checking prices during family dinners. Based in Melbourne, she reviews AUD Crypto Tracker's coin guides for accuracy, ATO alignment, and ruthless utility — no hype, no predictions, just what the data says.