Glossary
A hard fork is a protocol change old software cannot follow - nodes must upgrade or reject the new chain. When both sides keep running, two coins exist, and the ATO treats the new one as its own CGT asset.
A hard fork is a change to a blockchain's rules that old software cannot validate. Under the new rules, blocks and transactions the old software would reject become valid, so every node must upgrade or stop following the chain. When the whole network upgrades together, one chain continues and nothing visible happens. When the community splits over the change, two chains share the history up to the fork block and diverge from it - and two coins exist.
The split version is the one with consequences. Bitcoin split into Bitcoin and Bitcoin Cash in 2017 over block size, and Ethereum split into Ethereum and Ethereum Classic in 2016 after the DAO fork. Anyone holding the original coin at the fork block held equal amounts of both, because the same keys control the same history on both chains. The ATO treats a new asset received from a chain split as its own CGT asset, with a cost base equal to its market value in AUD when you obtained it.
Every node validates incoming blocks against its own rulebook: signatures, block structure, size, and consensus rules. Change a rule so that old software would reject a new block - a bigger block size, a new transaction type, a changed signature scheme. The two software versions stop agreeing. The fork block is the last block both versions accept; after it, the chains diverge, each extending its own version of the next block. Every coin and address that existed before the fork exists on both chains, because the ledger history up to that point is identical.
A contentious fork walks a predictable sequence: the change is proposed, the community argues, and an activation block height is set. On the day, either one chain continues or both do. Bitcoin Cash activated on 1 August 2017 with an 8 megabyte block size while Bitcoin kept the original rules, and Ethereum Classic kept the original ledger in 2016 while Ethereum moved past the DAO hack. Receiving both creates a replay problem: a transaction signed for one chain can sometimes replay on the other, which is why forks ship replay protection. Planned upgrades avoid all of it by coordinating the whole network, as Ethereum's Merge did in 2022 - a consensus engine swap with no split and no new coin.
Exchanges decide independently whether to credit a forked asset, and many did not in past splits. The ATO's chain split guidance is the tax flow. The old asset continues with its cost base, the new asset arrives with a cost base equal to its AUD market value on the day you obtained it. Neither event is a disposal of the other.
For Australian readers, the fork that matters is the one that happened to holdings you forgot about. Anyone who held Bitcoin in August 2017 held Bitcoin Cash by default. A colleague named Brent (yes, that Brent) discovered a BCH balance on an exchange he had stopped using years earlier. It was credited, unrecorded, and worth real money by the time he looked. ASIC MoneySmart's guidance treats custody gaps like this as a standard risk of holding through platform changes.
The tax treatment is the part people get wrong. A forked asset is not free money with no paperwork - it is a CGT asset from the moment you obtain it, cost based at its AUD market value on receipt. Recording that value at the time is the difference between a substantiated cost base and a guess years later. The highest-leverage things most Australians can do are check whether past forks were credited to their accounts, record the AUD value on receipt for any future split, and keep the paper trail. The crypto record keeping entry covers the five-year rule the trail needs to meet.
A holder with 1 BTC at the fork block automatically held 1 BCH on the new chain, because the same keys control the same history. Suppose BCH's market value on the day an exchange credited it was $600 AUD: that is the cost base. Selling the BCH two years later for $450 AUD produces a $150 capital loss, measured from the receipt value - not from zero. The BTC side of the holding never changed cost base at all, and neither disposal triggered the other.
Ethereum holders at the DAO fork held equal ETC on the original chain. ETC's AUD value on receipt set its cost base, and the asset later grew into a major coin before becoming the 51 percent attack entry's case study, suffering reorganisation attacks in 2019 and 2020. A forked asset can outlive the fork - and inherit the parent chain's weaknesses. The same keys controlled both chains, so nothing needed claiming.
Ethereum's consensus engine swap replaced proof of work with proof of stake across the entire network on one activation. No split occurred, no new coin was created, and no CGT event followed - the ETH holding simply continued. It is the counter-example that keeps the term honest: a network-wide upgrade can be as deep as any fork without producing a second asset. The depth of the change is not what makes a new coin; the disagreement is.
Mistake: Assuming every hard fork creates a new coin.
Why it bites you: Most hard forks are planned upgrades the whole network adopts, with no split and no new asset. A new coin exists only when both chains keep running.
Mistake: Ignoring forked balances on old exchange accounts.
Why it bites you: They are CGT assets from receipt, and unrecorded cost bases surface at the worst time. Brent's BCH sat unrecorded for years before anyone looked.
Mistake: Recording a forked coin's cost base as zero.
Why it bites you: The ATO expects market value in AUD on the day you obtained it. A zero base overstates the later gain and invites an amended assessment.
Mistake: Sending a forked asset without checking replay protection.
Why it bites you: Post-fork transactions can replay on the other chain, moving coins you did not intend to move. Forks ship replay protection for a reason; use it.
I spent an evening with the ATO's chain-split guidance and the post-mortems of two forks so you don't have to, and the line I underlined is the cost base one: market value in AUD on the day you obtained the new asset. Not zero, not the parent's cost base, not whatever the exchange's statement says months later.
Brent's forgotten BCH balance is the case I keep citing, because the fork happened to him and he noticed years late. Forks are the only events in crypto where new assets arrive uninvited - no signature, no email, no invoice. My position: check the old accounts, record the receipt values, and treat every fork announcement as a records event first and a trading event second.
On the chain itself, yes - the same keys control both sides of a split. On an exchange, only if the platform decides to credit the new asset.
The new asset is a separate CGT asset with a cost base equal to its AUD market value on the day you obtained it. The original holding continues with its own cost base untouched.
A soft fork tightens the rules in a way old software still accepts; a hard fork breaks compatibility, forcing an upgrade. Only a hard fork can split a chain into two assets.
It was an upgrade of equivalent depth that replaced the consensus engine network-wide. Because every client moved together, no split occurred and no new coin was created.
A 2017 disagreement over block size - bigger blocks versus smaller, more frequent ones. Neither side would follow the other's rules, so both chains kept running and two assets exist.
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.