04 · When usage grows
What happens when many more people want to use a network?
Every action on a network requires work.
Information has to reach other computers.
Transactions have to be checked.
Blocks have to be checked and stored.
And on networks that run programs, the computation and its result must also be verified.
Now imagine usage growing dramatically while everyone still expects the network to respond quickly.
More usage means more work for the computers checking the network
When more people send transactions, the computers on the network receive more information.
They have to verify more transactions, process more blocks, and keep the information needed to check what happens next.
If Smart Contracts are involved, some actions require more computation and update more data.
So:
Activity does not disappear just because we want the network to be faster.
The computers still have to process and verify it.
How much activity a network can handle and how quickly users get an answer are different questions
A network may be able to process a large amount of activity over time.
That is a question of Capacity / Throughput.
But a user also asks:
How long until I see my action included?
and
How long until I feel confident enough to rely on it?
These questions are related, but they are not identical.
So when someone says a network is “fast”, it is worth asking:
What exactly became faster?
Why not simply make the network do much more?
A network can try to fit more activity into each block.
It can create blocks more frequently.
It can require more powerful computers.
Each of those choices can increase performance.
But they create another important question:
Who can still keep up and verify the network independently?
If independent verification requires extremely expensive servers and data-center-class connectivity, fewer people can run their own Node.
More users will have to rely on large services to check the network for them.
That is why performance and decentralization are connected.
Even under heavy usage, the rules still have to remain trustworthy
A very fast network is not useful if the payment rules can be bypassed.
It still has to prevent someone from spending money they do not own, spending the same money twice, or easily replacing history that users already relied on.
That is why one number - such as TPS - cannot tell us by itself whether a network is “better”.
We want several things at once:
More activity.
Fast response.
Independent verification.
Rules that are difficult to bypass.
Faster blocks create another challenge
Information does not travel across the internet instantly.
Imagine one miner finds a new block and publishes it.
The block begins spreading through the network.
Before another miner hears about it, that second miner may also find a new block built on the same earlier history.
Now two valid blocks exist, and neither miner knew about the other block when it was created.
They do not need to be found at the exact same second.
The second block only needs to be found before news of the first one arrives.
Miner A finds a new block and broadcasts the information to the wider network. Several amber signals spread outward, including one toward Miner B. Before that information arrives, Miner B independently finds another valid block built on the same earlier history. Neither discovery needs to happen at the same instant. This animation does not decide which block wins.
The more frequently blocks are created, the more often this can happen
If minutes pass between blocks, information usually has plenty of time to spread before the next one appears.
If blocks are created many times per second, it becomes more likely that several miners will find blocks before they hear about each other.
In Bitcoin, situations like this can create temporary branches. Eventually one valid branch becomes the main chain based on accumulated work.
That means some work done in parallel does not remain part of the main chain.
So the challenge is not simply “make everything faster”
The goal is not only to create more blocks.
The goal is to support more activity and faster response while keeping the network practical for independent participants to verify.
And when blocks are created quickly, the network needs a better way to deal with work that happens in parallel.
That leads to a new question:
What if two valid blocks created in parallel did not have to compete for only one place in the history?
