Proof of work, single chain (Bitcoin fork) · since 2017
Bitcoin Cash
The 2017 fork that chose bigger blocks so the base layer itself can carry cheap payments.
Documented pace, live read missed
Live read:
Why people use it
How it works
A shared clock, using numbers already on this site
Block size
The block size adjusts to demand (ABLA) since 2024.
Upgrades
The network upgrades once a year, in May.
Try it: how long until a payment counts?
The wide mark is when that network calls a payment settled.
Block paces use the live read when it answers.
Strengths and trade-offs
Strengths
- Bigger blocks, low fees
- Active small dev community with yearly upgrades
- Native tokens on a UTXO chain
Trade-offs
- Low usage today on the live board
- Shares SHA-256 miners with Bitcoin, so a smaller security budget
- 10-minute blocks until the planned May 2027 switch to 1 minute
Design choices, next to Kaspa
Not a score. Every network picks a side on each of these. Filled: Bitcoin Cash. Outlined in blue: Kaspa. Tap a row for the trade-off.
Tap a row.
What its community is talking about
Paraphrased from X News story pages, which summarize public posts. Tap for the original thread.
Next to Kaspa
Generous where Bitcoin Cash leads, specific where Kaspa differs.
Bitcoin Cash has years of experience running big blocks and native tokens on a UTXO chain.
Kaspa scales with more blocks per second instead of bigger, slower blocks, so confirmations arrive in seconds.
Capacity without users stays empty. BCH shows the scaling fight is half the story.
The facts
10 minblocks; settlement is probabilistic
21 millionBCH cap
Run a node
A Bitcoin-like full node.
Old data
Pruning is available.
Official site
Static facts checked Nov 15, 2026. Spotted something wrong? The official source wins.