A code fork
Developers copy and change open-source software. This alone does not establish shared transaction history with Bitcoin.
The guide A familiar name.
CHAPTER 03 / FORKS & NEW COINS
A familiar name.
A fresh set of questions.
Forks and new projects can sound closely related to Bitcoin. Understand the relationship before trusting a website, a wallet tool or a claim.
ONE WORD, DIFFERENT EVENTS
What actually
forked?
A fork is a divergence in software or network rules. Copying code and splitting a live chain are different things.
A hard fork
A rule change that older rules reject. A lasting separate chain can result if both sets of rules continue to be followed.
A soft fork
A tightening of rules compatible with the older rules. It does not inherently create a new coin. SegWit and Taproot are Bitcoin soft-fork upgrades.
Shared history is not shared trust.
Bitcoin Cash is a documented direct split from Bitcoin. That kind of shared history does not automatically give another chain Bitcoin's security, value or Bitcoin Core endorsement.
A NAME TO READ CAREFULLY
Bitcoin Genesis 1.
Separate from BTC.
Bitcoin Genesis 1 (BTC1) is presented in Bitcoin Ecosystem materials as a separate cryptocurrency project. It is not bitcoin (BTC) and it is not Bitcoin Core software.
The Compass references used for this guide do not establish a specific shared-history fork point with Bitcoin. This guide therefore does not describe BTC1 as a verified direct Bitcoin chain split.
A Bitcoin-related name does not demonstrate endorsement or the same security.
CLAIMS NEED THEIR OWN EVIDENCE
A project description
is not a guarantee.
The BTC1 project page describes reserve, governance and utility ambitions. These are attributed project claims, not independently verified outcomes in this guide.
Do not infer current network activity, verified reserves or economic safety from that description. Current code, observable chain data and supporting records need their own review.
BEFORE YOU TRUST A NEW PROJECT
Ask for evidence,
not reassurance.
What relationship is documented?
Is it a code fork, a chain split or a separate project? Is a claimed fork point backed by independently checkable chain records?
Can the network be inspected?
Look for working software, a public explorer and observable network records. A launch announcement alone does not establish current operation.
Who controls the important decisions?
Check code, issuance, allocations and governance. If reserves are claimed, look for supporting custody and governance records.
What could go wrong?
Consider technical, custody, liquidity and market risks. Pause if access requires exposing your keys or rushing a decision.
Educational content only. Not financial advice.
SOURCE NOTES
Trace the explanation.
This chapter follows the Bitcoin Compass BTC1 and Bitcoin-forks explainers supplied with this project. It does not independently verify BTC1's claims or current status.