Scoutinternal

Bitcoin Cash (BCH) — Common Issues: Claiming, Missing Funds, and BTC/BCH Address Confusion

Bitcoin Cash (BCH) — Common Issues: Claiming, Missing Funds, and BTC/BCH Address Confusion

Problem

Customers contact support regarding Bitcoin Cash (BCH) for several recurring reasons: (1) they want to claim BCH that should be available in their BitGo wallet following the original BTC/BCH fork, (2) they report missing BCH balances or transactions not appearing, (3) they accidentally send BTC to a BCH wallet address (or vice versa) due to the shared address format between legacy BTC and BCH wallets, or (4) they want to "cash out" or convert their Bitcoin/BCH holdings. These issues primarily affect users with older v1 BTC wallets whose addresses overlap with BCH addresses.

Diagnostics

  • Confirm which coin the customer is asking about. Many customers use "Bitcoin Cash" loosely — clarify whether they mean BCH (the forked coin) or are simply asking how to convert BTC to fiat ("cash out"). Ticket subjects like "Cashing Out Bitcoin" and "I really want to cash out my bitcoin" are often fiat-withdrawal questions, not BCH issues.
  • Request the transaction hash and wallet ID. If the customer reports a missing transaction, ask for both in plain text (not as a screenshot). Verify the hash on a block explorer (e.g., mempool.space for BTC, or a BCH explorer).
  • Check the address in BGA (BitGo Admin). Search the destination address to determine whether it resolves to a BTC wallet or a BCH wallet. Legacy BTC addresses and BCH addresses can look identical; BGA will show which coin/wallet the address belongs to.
  • Identify the wallet version. Determine whether the wallet is v1 (v1btc) or v2. V1 BTC wallets share the same address format as BCH wallets, making cross-chain sends a common mistake.
  • Check wallet migration status. In BGA Web, verify whether the wallet has been migrated. If clicking a migrated wallet link produces an error such as "Cannot read properties of undefined," escalate to engineering.
  • Verify address ownership. Use BGA to confirm that the address the customer sent to actually belongs to one of their wallets. The diagnostic output will show which wallet(s) received value — confirm whether any of those wallets belong to the customer's account.
  • For BCH fork claims: Check whether the customer held BTC in a BitGo wallet at the time of the BCH fork (August 1, 2017). If they did, a corresponding BCH balance should exist. Look for a BCH wallet associated with the same keychain.

Resolution

Scenario: cash-bitcoin-bitcoincash-upgrade#btc-sent-to-bch-address

Trigger: Customer sent BTC from an external source (e.g., Cash App) to what they believed was their BTC wallet address, but the address actually belongs to a BCH wallet due to legacy address format overlap.

Signals: missing transaction, BTC sent to BCH address, v1btc, address pointing to BCH wallet, legacy address, Cash App, shared address format

Steps:

  1. Ask the customer for the transaction hash and the wallet address they sent funds to, in plain text.
  2. Look up the transaction hash on a BTC block explorer (e.g., mempool.space) to confirm it is a valid, confirmed BTC transaction.
  3. In BGA, search the destination address. Confirm whether it resolves to a BTC wallet or a BCH wallet. If the address points to a BCH wallet, this confirms the cross-chain address issue.
  4. Verify whether the customer also has a v1 BTC wallet by searching their account. Check if the v1 BTC wallet's first receive address matches the BCH wallet address.
  5. If BTC was indeed received on an address that belongs to a v1 BTC wallet (even though BGA also maps it to a BCH wallet), confirm the BTC balance on the v1 BTC wallet.
  6. If the funds are stuck due to a v1 wallet migration issue or the wallet is no longer accessible through the UI, engineering may need to provide a recovery script. Inform the customer that a possible solution exists which requires them to:
    • Create a new BTC wallet on the BitGo platform.
    • Install JavaScript (Node.js) on their computer.
    • Install BitGoJS.
    • Run a script provided by the BitGo engineering team to move the funds.
  7. Assess the customer's technical comfort level before proceeding. If the customer is not comfortable, coordinate with engineering for further assistance.

Notes: This scenario is most common with v1 BTC wallets because legacy BTC and BCH share the same address format. V2 wallets use different address formats and are less susceptible. If BGA Web shows an error like "Cannot read properties of undefined" when clicking a migrated wallet link, this is a known issue — escalate to engineering.

"Upon checking address: [...] Seems like its pointing to a BCH wallet: [...] Address does not look like its on BTC but BCH .. did the user send to wrong address?" (ticket #318818)

"Our engineering team feels they have a possible solution which would require software be installed on your end and actions taken by you. We will need you to first create a new BTC wallet on our platform. Then we will need you to install javascript on your computer. Once this is installed, we will need you install our BitgoJS. Once this is completed, we would provide you with the script to run that will help us resolve this issue." (ticket #318818)

"Its migrated from [...] but I get an error when clicking the link Cannot read properties of undefined" (ticket #318818)

Scenario: cash-bitcoin-bitcoincash-upgrade#bch-fork-claim

Trigger: Customer held BTC in a BitGo wallet at the time of the Bitcoin Cash fork (August 1, 2017) and wants to access or claim their corresponding BCH.

Signals: bitcoin cash claim, BCH fork, BCC, bitcoin cash balance, claim bitcoin cash, bitcoin cash distribution, when is BCH available, bitcoin cash don't show up

Steps:

  1. Confirm the customer had a BTC balance in their BitGo wallet on or before August 1, 2017 (the BCH fork date).
  2. Check in BGA whether a BCH wallet already exists for the customer's account. BitGo historically created BCH wallets corresponding to existing BTC wallets after the fork.
  3. If a BCH wallet exists and shows a balance, direct the customer to access it via the BitGo web UI at https://app.bitgo.com/auth/log-in — they should see the BCH wallet listed alongside their other wallets.
  4. If the BCH wallet exists but the balance does not appear, verify that the wallet is active and not frozen. Check the wallet status in BGA.
  5. If no BCH wallet exists, or if the customer's wallet is a v1 wallet that has not been migrated, escalate to engineering to investigate whether BCH can still be claimed or recovered.
  6. If the customer needs to perform a self-recovery (e.g., they no longer have platform access), direct them to the BitGo non-BitGo recovery tool at https://app.bitgo.com, selecting "Bitcoin Cash" as the coin. They will need their keycard values: Box A (encrypted user key), Box B (encrypted backup key), and Box C (BitGo public key), plus their wallet passphrase.

Notes: Some older tickets reference BCH by the ticker "BCC" — this is the same coin (Bitcoin Cash). The large volume of tickets with subjects like "Bitcoin Cash," "Bitcoin Cash Claim," and "BCC ? bitcoin cash" all relate to this fork-claim scenario. Many of these tickets lack detailed resolution data, suggesting they were handled via a standardized process or bulk communication at the time of the fork.

Scenario: cash-bitcoin-bitcoincash-upgrade#cash-out-inquiry

Trigger: Customer asks how to "cash out" their Bitcoin or wants to convert BTC to fiat currency — this is not a BCH-specific issue.

Signals: cash out, cashing out bitcoin, cash out my bitcoin, convert bitcoin, sell bitcoin

Steps:

  1. Clarify that BitGo is a custody and wallet platform, not an exchange. BitGo does not directly facilitate conversion of cryptocurrency to fiat currency for individual/retail users.
  2. Advise the customer to send their BTC from their BitGo wallet to an exchange or trading platform that supports fiat withdrawals.
  3. If the customer is an enterprise/institutional client, check whether they have access to BitGo's trading services and direct them to the appropriate team.
  4. Provide basic send instructions: navigate to the wallet, select "Withdrawal" or "Send," enter the destination address at their chosen exchange, and complete the transaction with 2FA and wallet password.

Notes: These inquiries are common from retail or self-managed wallet users. Do not confuse "cash out" requests with Bitcoin Cash (BCH) issues — always confirm what the customer is actually asking.

Scenario: cash-bitcoin-bitcoincash-upgrade#bch-wallet-recovery

Trigger: Customer needs to recover a Bitcoin Cash wallet using keycard credentials, either because they lost platform access or need to perform a non-BitGo recovery.

Signals: BCH wallet restore, BTCv2 wallet restore, bitcoin cash tool, bitcoin cash command line tool, recovery, keycard

Steps:

  1. Direct the customer to the BitGo recovery tool:
    • Mainnet: Navigate to the recovery tool via https://app.bitgo.com and select the appropriate environment.
    • Select Bitcoin Cash as the coin.
  2. The customer will need the following from their keycard:
    • Box A Value: Encrypted user key (include JSON parentheses).
    • Box B Value: Encrypted backup key.
    • Box C Value: BitGo public key.
    • Wallet Passphrase: The passphrase set when the wallet was created.
  3. If the customer needs an unsigned sweep transaction instead (e.g., they do not have the wallet passphrase), direct them to the "Building Unsigned Wallet Sweep Transactions" flow, which requires the User Public Key (Box A), User Key ID (Box B), BitGo Public Key (Box C), a non-BitGo destination address, and an Address Scanning Factor.
  4. If the customer references a "command line tool," they may be referring to BitGoJS or an older CLI recovery utility. Confirm their technical capability and guide accordingly, or escalate to engineering if a custom script is needed.

Notes: Bitcoin Cash is supported by both the Non-BitGo Recovery tool and the Unsigned Wallet Sweep tool. The Address Scanning Factor may need to be increased if the wallet has many generated addresses with gaps between deposits.

Related