Bitcoin is open source software, and like any software, it needs to evolve. Bugs need fixing, security can be improved, and new features can make the network more useful. But Bitcoin doesn't have a CEO or central authority deciding which changes get made. So how does an upgrade actually happen?
Unlike a traditional software company where developers can release an update for customers to install, Bitcoin operates through a decentralized network of independent participants. Changing its rules requires people to agree that the changes are worth adopting.
TL;DR
Bitcoin upgrades begin with ideas that are discussed, reviewed, and tested publicly. Significant proposals are often documented through Bitcoin Improvement Proposals (BIPs), which provide a structured way to describe potential changes.
Developers can write and release new software, but they can't force anyone to use it. Node operators choose which rules to enforce, while miners, businesses, and other users influence whether proposed changes gain support.
Upgrades that change Bitcoin's consensus rules require coordination among participants who want to continue operating on the same network. There is no central authority that can approve a change on everyone's behalf.
Bitcoin Improvement Proposal (BIP)
A Bitcoin Improvement Proposal, or BIP, is a document that describes a proposed improvement, technical standard, or process related to Bitcoin. BIPs provide a common format for presenting ideas so that developers and other interested participants can evaluate them.
Anyone can propose a BIP. The process typically begins with public discussion, where an idea can be questioned, refined, or challenged before it becomes a formal proposal. A BIP generally explains what the author wants to accomplish, why the change might be useful, and how it would work.
Each published BIP receives a number, making it easier to reference and discuss. For example, BIP 141 describes Segregated Witness (SegWit), an upgrade that activated in 2017.
However, publishing a BIP doesn't mean the proposal has been approved or will ever be adopted. Some proposals lead to widely used features, while others remain under discussion or are eventually abandoned.
From proposal to upgrade
Once an idea has attracted interest, developers may begin writing code to implement it. That code can then be reviewed by other contributors, who examine how it works, look for potential problems, and suggest improvements.
Testing is especially important because changes to Bitcoin can affect software used by people around the world. Developers may test new features in controlled environments before they are considered ready for wider use.
If a change is incorporated into a software release, participants can choose whether to install that version. Some updates improve performance or fix bugs without changing Bitcoin's consensus rules. Others introduce changes that require broader coordination because they affect which transactions or blocks the network considers valid.
Who decides whether an upgrade is adopted?
Developers contribute code and technical expertise, but releasing new software doesn't automatically change Bitcoin. Node operators ultimately choose which software to run and which consensus rules to enforce, while miners help coordinate certain upgrades. Businesses, exchanges, wallet providers, and individual users also influence adoption through the software and services they choose to support.
These groups don't always agree, and there's no fixed percentage of support that guarantees every proposed change will succeed. An upgrade can gain widespread acceptance, remain controversial, or fail to attract enough support to move forward.
Why does Bitcoin take so long to upgrade?
Bitcoin's development process can seem unusually slow compared with traditional software projects. Proposals may be discussed for years, and even changes with substantial support can require extensive review and coordination.
Part of the reason is that Bitcoin's consensus rules protect a network that people rely on to store and transfer value. A mistake in those rules could have serious consequences, and there is no central administrator who can simply reverse an unwanted change.
The decentralized nature of Bitcoin also means that participants need time to evaluate proposals independently. Developers may agree that a feature is technically possible without agreeing that it should be introduced, or how it should be activated. This careful approach can make upgrades more difficult, but it also helps protect the network from changes that haven't been thoroughly examined.
How does Bitcoin move forward?
Bitcoin doesn't need a central authority to improve, but it does need cooperation. Ideas are proposed publicly, developers write and review code, and participants decide whether to adopt the resulting changes.
Not every proposal becomes an upgrade, and disagreement is a normal part of the process. Bitcoin's development depends on people being able to question changes rather than simply accepting decisions made by someone in charge. The result is a system that can evolve without giving any single person or organization the authority to decide its future.
Learn Bitcoin. Find your people.
Bitcoin Party KC brings together Bitcoiners and the Bitcoin curious across Kansas City through local events, education, and a growing community. Members receive The Sovereign Review, exclusive event access, discounts, and more.

