How to Claim Bitcoin Gold (BTG) Safely Without Getting Scammed

Claiming Bitcoin Gold safely comes down to one rule: never expose the private keys still holding your Bitcoin. A hard fork like BTG copies the Bitcoin ledger at a snapshot block, so anyone who controlled BTC at that height also controls the matching BTG. The catch is that "claiming" requires access to those original keys, and that is exactly what scammers exploit. The correct workflow is to move your BTC to fresh keys first, then import the now-empty old keys into a reputable BTG-aware wallet, never pasting a seed phrase into any website. This guide walks through the safe sequence step by step.

What "Claiming" a Bitcoin Gold Fork Actually Means

When a blockchain undergoes a fork, the new chain inherits the entire transaction history of the original up to a specific snapshot block. Bitcoin Gold forked from Bitcoin at block 491,407. If your BTC balance existed in a wallet you controlled at that block, an identical BTG balance exists on the new chain — credited to the same address.

The crucial detail: those coins are unlocked by the same private key that controls your BTC. There is no "claim button" that mints coins to you. Claiming simply means importing your keys into software that understands the BTG chain so you can sign a BTG transaction. This is why every legitimate guide focuses on key handling, and every scam tries to get you to surrender that key.

📷 a simple diagram showing one Bitcoin address splitting into two balances after the fork block — BTC on the original chain and BTG on the forked chain, both controlled by the same private key

The Golden Rule: Move Your BTC Before You Touch BTG

The single most important safety step is sequencing. Before you import any old key into BTG software, send your BTC to a brand-new wallet whose seed phrase has never touched fork-claiming tools. Once your BTC is safe, the old keys hold only BTG, so even a mistake or a buggy tool can cost you the forked coins at most — not your main holdings.

This order matters because of a technical hazard called a replay attack. On poorly separated forks, a transaction broadcast on one chain can be rebroadcast ("replayed") on the other, potentially moving coins you did not intend to move. Bitcoin Gold added replay protection, but treating the two chains as fully independent — and emptying BTC first — removes the risk entirely.

Safe Sequence at a Glance

1. Back up everything. Record your original 12- or 24-word seed offline, on paper, before doing anything.
2. Create a fresh BTC wallet with a new seed phrase on a trusted, updated app or hardware device.
3. Send all BTC from the old wallet to the fresh wallet. Confirm it arrives.
4. Only now import the old seed/key into a reputable BTG-supporting wallet to access the forked coins.
5. Sweep the BTG to a wallet you control long-term, then retire the exposed old key permanently.

Choosing a Wallet That Supports BTG

Not every wallet recognizes the Bitcoin Gold chain, so wallet choice is itself a security decision. The categories below trade off control against convenience.

For most people, a well-reviewed self-custody wallet that explicitly supports BTG is the right balance. If you are claiming a meaningful amount, a cold wallet keeps the signing key offline and is worth the extra steps. Avoid the full-node route unless you specifically intend to run infrastructure — it forces you to download the entire chain history, which is hundreds of gigabytes and growing.

📷 a comparison screenshot of a wallet's "import account" screen highlighting where a public address field differs from a private-key field

How BTG Phishing Scams Work

Forks attract scammers precisely because newcomers often do not understand what a private key or recovery phrase can do. The pattern is consistent across every major fork:

• Lookalike domains. Sites with names like "claim-btg," "btg-gold," or "mybtg-wallet" appear in search results and paid ads, mimicking an official portal.
• The seed-phrase trap. The page asks you to "enter your wallet to check your balance," then requests your 12- or 24-word recovery phrase or your private key. Anyone who receives that phrase controls every coin it secures.
• Fake support and giveaways. Impersonators on social channels promise to "help you claim" in exchange for your keys, or claim you must send a small amount first.

A real-world failure mode: a user who pastes a seed phrase into a "balance checker" can have both their BTC and BTG swept within minutes, because the seed unlocks every coin on every chain derived from it. This is functionally identical to a rug pull in outcome — total, irreversible loss.

📷 an annotated screenshot of a fake BTG claim site, with a red callout on the input box demanding a 12-word recovery phrase

Worked Example: Why the Move-First Order Saves You

Suppose you held 0.5 BTC at the fork snapshot. That entitled you to 0.5 BTG on the new chain.

• Scenario A — unsafe. You paste your seed into a "claim" site to check your BTG. The site operator now has your seed and drains 0.5 BTC plus 0.5 BTG. Total loss: 0.5 BTC + 0.5 BTG.
• Scenario B — safe. You first move 0.5 BTC to a fresh wallet, then import the old seed into BTG software. Even if that BTG tool were compromised, the old key now holds only 0.5 BTG. Maximum loss: 0.5 BTG; your BTC is untouched.

The arithmetic makes the discipline obvious: sequencing converts a catastrophic loss into a capped, survivable one. Treat the old key as "burned" the moment it has been near any claiming tool, and never reuse it.

Verifying Authenticity Before You Type Anything

Before entering any address or installing any app, run these checks:

1. Confirm the project's official domain from multiple independent references, not from a search ad. Bookmark it; type it manually next time.
2. Never enter a seed phrase on a website. Legitimate balance checks only ever need a public wallet address, which is safe to share. If a site asks for your private key or seed, it is a scam — full stop.
3. Verify wallet apps by downloading only from the official site or the wallet's verified store listing, and check publisher names carefully.
4. Cross-check guides. If a fork-claiming method asks you to disable security features or send funds upfront, abandon it.

For a deeper grounding in how forks distribute coins and what to expect during a claim window, see our walkthrough on claiming hard forks and airdrops.

Risks and Pitfalls to Avoid

• Pasting a seed into any website. The number-one cause of fork-claim losses. There is no legitimate exception.
• Claiming before moving BTC. Skipping the move-first step exposes your entire BTC balance to buggy or malicious tools and to replay risk.
• Reusing the exposed key. After a key has been imported into claiming software, retire it. Do not receive new funds to it.
• Trusting search ads. Paid results for "claim [fork]" are a known scam vector. Navigate manually.
• Ignoring hardware-wallet hygiene. A cold wallet only protects you if you confirm addresses on the device screen and buy it from the manufacturer.
• Assuming an exchange will credit the fork. Many do not, or do so on their own timeline. Do not count on it.

If you want a broader security baseline beyond forks, our guide on protecting your crypto from common threats covers the habits that prevent most losses.

COINOTAG Perspective

The enduring lesson of Bitcoin Gold and every fork since is that "free coins" are a social-engineering magnet. The forked value is real, but it is never worth risking your primary holdings to grab quickly. From a security standpoint, the only defensible workflow is to assume any key touched by claiming tools is compromised, and to structure your steps so that assumption costs you nothing important. Move first, claim second, verify obsessively, and never let a seed phrase leave your offline backup. If the math of a claim does not clearly outweigh the operational risk, skipping it is a perfectly rational choice.

Frequently Asked Questions