What are BTC and Bitcoin Core?
Bitcoin (BTC) launched in January 2009. It uses proof-of-work and has a supply cap of 21 million BTC. Bitcoin Core is the reference software, not a separate coin.
In proof-of-work, miners spend energy to add blocks. A familiar name does not give another network Bitcoin's security or establish an endorsement.
Primary sources: how Bitcoin works and about Bitcoin Core.
How do BCH and BSV relate to Bitcoin?
A fork is a change of rules. A chain split happens when some nodes keep the old rules and others follow new ones. A fork coin is a separate asset with its own software, market and risks.
Bitcoin Cash's split was mainly over block size. Holding BTC does not mean a fork coin is safe to claim or use.
Does every fork create a coin?
No. These terms describe different kinds of change.
- A code fork
- Developers copy and change open-source software. This alone does not establish shared transaction history with Bitcoin.
- A hard fork
- A 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.
What does the Bitcoin Ecosystem project describe?
The Bitcoin Ecosystem project describes the following family. These are attributed project descriptions, not independently verified outcomes. This guide does not describe any of these chains as a fork of Bitcoin.
Bitcoin Reserve / RWA1 (BTCr1)
The Sovereign Reserve / Real World Asset Chain
This is the project's name and role description. The table uses the project's supply wording.
| Name and ticker | Project's role description | Project's supply wording |
|---|---|---|
| Bitcoin Reserve / RWA1 (BTCr1) | The Sovereign Reserve / Real World Asset Chain | 26.6 Million per year |
| Bitcoin Genesis 1 (BTC1) | The Decentralised Utility & Security Chain (proof-of-work) | 26.6 Million per year |
| 1Bitcoin1 (1BTC1) | The Scarcity Anchor | 21 Million |
| Bitcoin1USD (BTC1USD) | The Stability Layer | No supply figure stated here |
| Bitcoin1.ai (BTC1ai) | The Decentralised Intelligence Layer | 26.6 Million per year |
| BitcoinQu1 (BTC1q) | The Quantum-Secure Ledger | 21 Million |
On a narrow screen, scroll the table sideways to read every column.
A role name does not establish reserves, price stability, present network operation or resistance to a particular attack. Check evidence for each claim separately. The name BTC1 is not the ticker BTC.
What should you ask before using a fork or new chain?
What relationship is documented?
Is this a chain split or a separate project? Look for independently checkable chain records rather than inferring a relationship from the name.
Can you inspect the network?
Look for working software, observable network records and a public explorer. A launch announcement alone does not establish current operation.
Who controls changes and access?
Read the code, issuance and governance information. Where reserves are claimed, ask for supporting custody and governance records.
What does the tool ask you to expose?
Check wallet support, network selection and transaction risks. Stop if a claim requires an existing recovery phrase, private key or rushed approval.