A headline about a large Bitcoin holder can make ownership sound like control over a company. Bitcoin works differently: holding BTC, developing software and validating payments are separate activities. Understanding the roles helps you read ownership claims and choose how to receive your own purchase.
Who owns the coins, and who runs the network?
Individuals, businesses and institutions can hold BTC. Some keep the keys themselves; others use a custodian. The Bitcoin.org FAQ describes Bitcoin as an open network whose participants choose the software they use. There is no single company that owns the entire network and issues shares in it.
Ownership of a particular balance and influence over the payment system need separate explanations. A large holder can buy or sell, and a major service can influence customer access. The network’s operation also depends on the software rules participants enforce and the miners producing blocks.
Satoshi Nakamoto introduced Bitcoin’s original design. For the history and evidence behind that name, see our Bitcoin founder guide. Here, the focus is how the system operates and how your own BTC is held today.
The main roles in plain English
The same person or business can perform several roles. A holder might also run a node, while an exchange might hold customer keys and operate its own technical infrastructure.
Scroll across the table to see all columns.
| Role | What it does | What it means for a buyer |
|---|---|---|
| BTC holder | Has an interest in a particular amount of BTC, directly or through an account arrangement | Read how the balance is held and what withdrawal terms apply |
| Key holder or signing participants | Can authorize transfers under the wallet’s signing setup | Find out who must approve a transfer and how access is recovered |
| Miner | Builds candidate blocks and competes through proof of work to add them | Mining contributes to transaction confirmation |
| Full-node operator | Checks transactions and blocks against the rules implemented by its software | Validation helps enforce the network rules the operator has chosen |
| Developer or software maintainer | Proposes, reviews, tests or maintains software changes | Look at the change and its adoption rather than treating a developer as an account administrator |
| Exchange or custodian | Provides account services and may manage keys and withdrawals | Your access also depends on that service’s security, procedures and terms |
Fidelity Digital Assets’ explanation of network control describes miners producing blocks and nodes validating them. It also discusses differences in economic influence. Decentralized participation still includes concentrated businesses, mining operations and software development.
Who decides when Bitcoin’s rules change?
A proposed software change goes through discussion, implementation and review. Adoption comes afterward: participants choose which software to run and which rules to accept. Changes to shared transaction rules require particular care because participants need compatible behavior to continue operating together.
Bitcoin Core’s public contribution guidelines describe proposals, testing and peer review. They distinguish decisions about merging code into that project from changes to Bitcoin’s network consensus rules. Publishing a release is one step in a larger adoption process.
For example, imagine a developer proposes a new validation rule. Reviewers can inspect the code and its effects; operators then evaluate the software and whether to adopt it. The proposal’s technical details, compatibility and wider acceptance matter. Reading a headline that one developer ‘changed Bitcoin’ leaves out those decisions.
Example: two customers and one visible balance
Imagine a fictional custodian holding the following two customer balances in a simplified shared arrangement. It controls the signing keys. These numbers illustrate the bookkeeping; they describe no actual company, customer or reserve disclosure.
Scroll across the table to see all columns.
| Record | BTC | Satoshis |
|---|---|---|
| Customer A’s account record | 0.00200000 | 200,000 |
| Customer B’s account record | 0.00300000 | 300,000 |
| Combined amount in the example | 0.00500000 | 500,000 |
An observer seeing 0.00500000 BTC at the custodian’s address sees the on-chain amount at that address. The service’s internal records explain the two customer balances. Customer A requests a withdrawal through the custodian, which applies its account procedures and authorizes the transfer.
Now suppose Customer A receives the 0.00200000 BTC in a self-custody wallet, with the delivery charge paid separately for this example. Control over subsequent transfers follows that wallet’s signing setup. Customer A must protect the keys and recovery information. Bitcoin.org’s custody explanation describes the responsibilities and risks of these different arrangements.
The custodial vs. non-custodial wallet guide takes this comparison further, including account recovery and withdrawal approval.
Why an address ranking can mislead you about owners
A person can use several addresses, while a service can manage BTC associated with many customers. Bitcoin.org’s privacy guide recommends fresh receiving addresses and explains how transaction histories can become linked. Counting addresses therefore answers a different question from counting people.
Analytics services may group addresses into estimated entities. Glassnode’s active-entity definition describes clustering through heuristics and proprietary algorithms. Treat those groupings as an analytical model, and read how labels are assigned and updated.
Also check what a reported exchange balance covers. Glassnode’s transparency notice explains the scope of its address-based exchange data and its exclusion of obligations and liabilities. Assessing a custodian’s financial position needs broader records than an address balance alone.
- Does the chart rank individual addresses, grouped entities or disclosed holdings?
- Is the label a public disclosure, an analyst’s attribution or an estimate?
- Could the named organization be holding BTC for customers or a fund?
- What date does the information represent, and how are transfers between related addresses handled?
What should you check before your own purchase?
Turn the ownership question into five practical checks:
- Identify what you will receive: BTC in an account, BTC delivered to your wallet or shares in a separate investment product.
- Find out who controls the signing keys and who approves a withdrawal.
- Read the withdrawal minimum, complete charges, supported delivery network and any holding or review conditions.
- Understand the recovery process. For self-custody, follow the wallet maker’s verified backup instructions and keep recovery words private.
- Keep the purchase reference and check the actual receiving record when delivery occurs.
Our Buy Bitcoin guide compares payment routes and delivery checks. For brokerage products, see Bitcoin ETF vs. Bitcoin. For receiving BTC yourself, the wallet-address guide explains how to check the destination before funding.
Sources & further reading
General payment information and purchase-specific details serve different purposes. Review the current offer and terms before proceeding.
- Bitcoin.org — Network control and software adoption
- Fidelity Digital Assets — Nodes, miners and network influence
- Bitcoin Core — Contribution and code-review process
- Bitcoin.org — Keys, custody and responsibilities
- Bitcoin.org — Addresses and transaction privacy
- Glassnode — Estimated active entities
- Glassnode — Exchange-data scope and limitations
Original Fiat2Bitcoin guide. Examples are illustrative; they are not live quotes or customer transactions. How we prepare our guides.
