A payment system with no operator
Bitcoin was released in 2009 as software that lets people transfer value without an
institution in the middle. There is no company running it, no server to shut down and no
administrator who can freeze a balance. The network is whoever chooses to run the software,
and the rules are whatever a majority of them will accept as valid.
That structure produces the properties people argue about. Transfers cannot be reversed
because there is no one with the authority to reverse them. Accounts cannot be frozen because
there are no accounts. Nobody needs permission to receive a payment because there is nobody to
ask. Each of these is a benefit and a hazard depending entirely on the situation you are in.
- Maximum supply
- 21,000,000
- Block interval
- ~10 minutes
- Issuance halves
- Every 210,000 blocks
- Smallest unit
- 0.00000001
The schedule is the design
New bitcoin enters circulation as a reward to whoever writes the next block, and that reward halves at fixed intervals, every 210,000 blocks, which works out to roughly four years. The
sequence is not a policy anyone administers. It is written into the software every participant
runs, and a block paying more than the schedule allows is rejected by everyone else.
This is why the supply cap is a stronger claim than most monetary promises. It is not a
commitment by an issuer who could change their mind; it is a rule enforced independently by
every party who would have to accept the violation. Changing it would require the people
holding the asset to agree to dilute themselves, which is not a coalition anyone has managed
to build.
Where the mechanism ends and the argument begins
Everything above is checkable. What follows is not, and the two are constantly presented in
the same voice. The common argument runs: supply is capped, demand grows, therefore price
rises. The first clause is a fact about software. The second is a prediction about human
behaviour, and it is doing all the work.
A capped supply guarantees scarcity. Scarcity guarantees nothing about price, because price
requires demand, and demand for a scarce thing can fall to nothing. Plenty of genuinely scarce
objects are worth very little. Keeping the fact and the forecast separate is the single most
useful habit when reading anything about this asset, including material that is broadly
correct.
Why the halving gets so much attention
It is the only scheduled supply event in the asset’s design, which makes it the one thing
anyone can point to on a calendar. Whether it moves price is genuinely disputed: the
schedule has been public since the beginning, so a market that prices in known information
should already reflect it. That argument and the observed history do not obviously agree.
Why the price and the network are only loosely linked
Transaction volume, address activity and hash rate all move somewhat independently of
price, over long stretches. Using one as evidence for another is common and usually
unjustified, because the buyer setting the price today is rarely the participant using the
network today.
What “digital gold” gets right and wrong
Right: both are scarce, neither pays a yield, and both are held partly as a hedge against
currency debasement. Wrong: gold has millennia of established behaviour and industrial
demand, while bitcoin has fifteen years and no use outside its own network. The analogy
smuggles in a track record the asset does not have.
Who actually runs it
Three groups are routinely confused, and the distinction decides what any of them can change.
Developers write software and can propose anything. Miners order transactions and choose which
software to run. Node operators, which includes anybody running the full client, decide which
blocks they will accept as valid.
That last group holds the constraint people usually attribute to the first. A rule change that
nodes reject produces blocks nobody recognises, so a proposal with developer support and
mining support can still fail. It is why the supply schedule is described as fixed even though
no authority enforces it: changing it would require persuading a large, uncoordinated set of
people to run software that devalues what they hold.
This was tested rather than assumed. The scaling dispute that ran through 2017 ended when one
side’s proposal failed to attract the node adoption it needed, and the network continued on the
existing rules while the alternative separated into its own chain. Whatever one thinks of the
outcome, it demonstrated where the veto sits, which no whitepaper could have established on its
own.
The same structure explains why upgrades are slow and usually backwards-compatible. A change
that old nodes still accept can roll out gradually; one that requires everybody to move at once
needs coordination the network has no mechanism to compel.
What it is bad at
It is a poor everyday payment instrument in most places. Confirmation takes minutes, fees rise
when the network is busy, and the price moves enough that a coffee bought today may have cost
substantially more or less by the time it settles. Layer networks address parts of this and
add their own complexity.
It is also unforgiving. The absence of an intermediary removes the intermediary’s services
along with its control: no reversal, no dispute process, no recovery of a mistyped address.
For a person who has only ever used systems with those safeguards, the adjustment is the real
barrier, not the technology.
Be the first to comment