How to claim Bitcoin Cash on Trezor? (Hard fork guide)

Understanding the Bitcoin Cash Fork Event

1. Bitcoin Cash emerged as a hard fork of the Bitcoin blockchain on August 1, 2017, at block height 478558.

2. The fork created an independent ledger with larger block sizes, enabling higher transaction throughput and lower fees.

3. All BTC held in a Trezor wallet at the time of the fork were mirrored as equivalent BCH balances on the new chain.

4. No action was required during the fork itself—BCH existed as a parallel asset tied to the same private keys controlling the original BTC.

5. Users who controlled their own private keys via Trezor retained full ownership rights over both BTC and BCH without needing third-party intervention.

Prerequisites for BCH Claiming

1. A Trezor Model T or Trezor One device must be physically connected and unlocked using the correct PIN.

2. Firmware version must be 2.3.0 or later for Model T, or 1.9.0 or later for Trezor One—older versions lack BCH support.

3. The wallet must have been used before the fork date; funds received after block 478558 do not generate corresponding BCH.

4. Recovery seed must be intact and unaltered—any change to the derivation path or passphrase invalidates the claimable balance.

5. Internet access and browser compatibility are essential: Chrome, Edge, or Brave with WebUSB enabled.

Step-by-Step BCH Access Procedure

1. Navigate to wallet.trezor.io and ensure the Trezor device is connected via USB.

2. Click the “Select coin” dropdown menu and choose Bitcoin Cash instead of Bitcoin.

3. Confirm on the device screen that the selected coin is indeed Bitcoin Cash—this prevents accidental BTC transfers.

4. Wait for the interface to load the BCH account; addresses will appear under the “Receive” tab.

5. Verify that the displayed receiving address matches the one derived from your seed by manually checking the first six and last four characters on-device.

6. Initiate a test transaction with a small amount to confirm functionality before moving significant balances.

Risks and Common Pitfalls

1. Sending BCH to a BTC address—or vice versa—results in permanent loss, as the networks are incompatible and non-recoverable.

2. Using third-party tools or unofficial firmware to extract BCH may expose seed phrases and compromise BTC security.

3. Enabling passphrase protection during recovery changes the entire derivation tree—BCH balances become inaccessible unless the exact same passphrase is entered.

4. Attempting to claim BCH through unsupported wallets like Electrum or Exodus without proper derivation path configuration leads to zero balance display.

5. Reusing the same receive address across BTC and BCH chains increases traceability and weakens privacy assumptions.

Frequently Asked Questions

Q: Can I claim Bitcoin Cash if I used my Trezor with a third-party wallet like Exodus?A: Yes—if the third-party wallet used the standard BIP-44 derivation path and did not implement custom logic, the BCH remains accessible via Trezor’s native interface once restored with the original seed.

Q: What happens if I sent BTC from my Trezor after the fork but before claiming BCH?A: The BCH balance remains unaffected as long as the original UTXOs still exist in the wallet history. Transaction activity on BTC does not erase BCH entitlements tied to pre-fork holdings.

Q: Does Trezor support Bitcoin Cash ABC or Bitcoin Cash Node separately?A: As of current firmware, Trezor only supports the Bitcoin Cash chain following the November 2018 chain split consensus—the client defaults to the dominant fork recognized by CoinMarketCap and major explorers.

Q: Is it possible to claim Bitcoin SV (BSV) using the same process?A: No—BSV resulted from a separate November 2018 fork and requires distinct derivation parameters. Trezor does not natively support BSV; users must rely on external tools or alternative wallets compatible with its specific HD path.