Proof of stake (Snow family), many L1s · since 2020
Avalanche
A network of chains: the C-Chain runs Ethereum-style apps, and companies launch their own Avalanche L1s.
Documented settlement, live read missed (about 1 to 2 s).
Live read:
Why people use it
How it works
Snow consensus
Validators repeatedly sample small random groups until they agree.
A shared clock, using numbers already on this site
The layout
A primary network plus many custom L1s, with an EVM-compatible C-Chain.
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
- Fast finality
- Custom chains for apps and institutions
- Strong tokenization traction
Trade-offs
- Activity is spread across many chains
- C-Chain usage is modest on the live board
- Custom chains can be permissioned
Design choices, next to Kaspa
Not a score. Every network picks a side on each of these. Filled: Avalanche. 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.
Also on our talk page
Next to Kaspa
Generous where Avalanche leads, specific where Kaspa differs.
Avalanche is far ahead in institutional tokenization and fast finality for apps.
Kaspa keeps one open, proof-of-work ledger instead of many custom chains; anyone can mine and nobody can be excluded.
Capital markets want predictable settlement and compliance tooling. That is a different market than Kaspa's open money.
The facts
1 to 2 sfinality, from this page
720 millionAVAX cap; fees are burned
Validator, official requirements
| CPU | 4 cores / 8 threads |
| Memory | 16 GB |
| Disk | 1 TB NVMe |
| Network | 100 Mbit/s |
Old data
State sync downloads active state instead of full history.
Official site
Static facts checked Nov 15, 2026. Spotted something wrong? The official source wins.