Ten blocks
every second.
Nothing discarded.
Every proof-of-work network before Kaspa bought security with slowness. Speed a chain up and blocks collide, losers get orphaned, and the wasted work is wasted security. Kaspa stopped treating simultaneous blocks as competitors — it orders all of them instead. This is the reference for how that works, what it cost, and what is still unproven.
Read it off the network, not off a chart
Because Kaspa halves annually rather than every four years, the overwhelming majority of KAS has already been issued. New supply now arrives slower than almost any other proof-of-work network — which also means fee revenue has to start carrying security sooner. That is the real open question, and no amount of enthusiasm settles it.
See the full curve →The reward drops to — per block — a 5.61% step. Twelve of these compound to an exact halving.
Speed was never the hard part.
Not wasting the work was.
Switch the panel below to a single-chain protocol and watch the discard counter climb. Both simulations mine ten blocks a second with a 250 millisecond propagation delay — the only difference is what the protocol does when two miners publish at once.
A Bitcoin block references exactly one parent. If two miners find a block in the same instant, the network eventually keeps one and orphans the other. At ten-minute intervals that almost never happens, so the cost is invisible. At ten blocks per second it happens constantly, and every orphan is real electricity spent on security the network does not get to keep.
GHOSTDAG changes the question. A Kaspa block references every tip it can see, so simultaneous blocks all enter the structure. The protocol then greedily picks the largest set of mutually well-connected blocks — the blue set — orders those first, and deterministically interleaves the rest. Every honest node running the same rule on the same DAG derives the same total order.
That is the whole trick, and it is why the block rate stopped being capped by propagation delay.
Red blocks in the panel are not rejected. They are stored, ordered, and their transactions settle. Red only means the block’s anticone exceeded the k parameter, so it does not contribute security weight. The single most repeated error in Kaspa threads is treating red as invalid.
Everything Kaspa,
organised for reading
No section here is a stub. Each one either explains a mechanism properly, hands you a working instrument, or tells you plainly where the evidence runs out.
Built on the
twelve-tone scale
Every Kaspa month the block reward is multiplied by 2^(-1/12) — the frequency ratio between two semitones. Twelve steps compound to exactly one half, so the network halves annually without ever putting a cliff in front of miners. The phase opened at 440 KAS per second: the pitch of A4.
Being right is
more persuasive
than being loud
If you post about Kaspa, these three corrections will do more for your credibility than any price take. Each one is a claim you can defend, and each one is repeated wrongly somewhere on your feed today.
"Red blocks get thrown away."
They do not. A red block is stored, ordered, and its transactions settle. Red means its anticone was wider than k, so it carries no security weight — that is a different statement entirely.
"10 blocks per second means 10× the transactions."
Roughly 8–9×. Testing before Crescendo measured 80–90% efficiency, because more parallel blocks means more chance two of them carry the same transaction. The gap is small and it is real.
"Kaspa confirms faster than chain X finalises."
Those are two different measurements. Confirmation is inclusion and ordering. Finality is when reversal becomes economically unrealistic. Kaspa is genuinely fast at the first one — say which one you mean.
Bring people here
and they leave
knowing something.
Most crypto communities are built on anticipation, which has a half-life. This one is built on a mechanism that is genuinely unusual and genuinely explainable. Post the signal board, hand out the creator kit, send newcomers to the consensus lab — and let the protocol do the convincing.
- A public wallPost a callsign and a take. Stored in Postgres, no links allowed, no accounts required.
- Six ready threadsCopy-and-post templates on the orphan problem, the chromatic curve, and what Toccata did and did not ship.
- A shareable scoreTwelve questions. Most people miss the red-block one. The result copies as a post.
- The briefing listReduction milestones, activation scores, and corrections when the timeline gets something wrong.
Ten blocks
every second.
Nothing discarded.
Every proof-of-work network before Kaspa bought security with slowness. Speed a chain up and blocks collide, losers get orphaned, and the wasted work is wasted security. Kaspa stopped treating simultaneous blocks as competitors — it orders all of them instead. This is the reference for how that works, what it cost, and what is still unproven.
Read it off the network, not off a chart
Because Kaspa halves annually rather than every four years, the overwhelming majority of KAS has already been issued. New supply now arrives slower than almost any other proof-of-work network — which also means fee revenue has to start carrying security sooner. That is the real open question, and no amount of enthusiasm settles it.
See the full curve →The reward drops to — per block — a 5.61% step. Twelve of these compound to an exact halving.
Speed was never the hard part.
Not wasting the work was.
Switch the panel below to a single-chain protocol and watch the discard counter climb. Both simulations mine ten blocks a second with a 250 millisecond propagation delay — the only difference is what the protocol does when two miners publish at once.
A Bitcoin block references exactly one parent. If two miners find a block in the same instant, the network eventually keeps one and orphans the other. At ten-minute intervals that almost never happens, so the cost is invisible. At ten blocks per second it happens constantly, and every orphan is real electricity spent on security the network does not get to keep.
GHOSTDAG changes the question. A Kaspa block references every tip it can see, so simultaneous blocks all enter the structure. The protocol then greedily picks the largest set of mutually well-connected blocks — the blue set — orders those first, and deterministically interleaves the rest. Every honest node running the same rule on the same DAG derives the same total order.
That is the whole trick, and it is why the block rate stopped being capped by propagation delay.
Red blocks in the panel are not rejected. They are stored, ordered, and their transactions settle. Red only means the block’s anticone exceeded the k parameter, so it does not contribute security weight. The single most repeated error in Kaspa threads is treating red as invalid.
Everything Kaspa,
organised for reading
No section here is a stub. Each one either explains a mechanism properly, hands you a working instrument, or tells you plainly where the evidence runs out.
Built on the
twelve-tone scale
Every Kaspa month the block reward is multiplied by 2^(-1/12) — the frequency ratio between two semitones. Twelve steps compound to exactly one half, so the network halves annually without ever putting a cliff in front of miners. The phase opened at 440 KAS per second: the pitch of A4.
Being right is
more persuasive
than being loud
If you post about Kaspa, these three corrections will do more for your credibility than any price take. Each one is a claim you can defend, and each one is repeated wrongly somewhere on your feed today.
"Red blocks get thrown away."
They do not. A red block is stored, ordered, and its transactions settle. Red means its anticone was wider than k, so it carries no security weight — that is a different statement entirely.
"10 blocks per second means 10× the transactions."
Roughly 8–9×. Testing before Crescendo measured 80–90% efficiency, because more parallel blocks means more chance two of them carry the same transaction. The gap is small and it is real.
"Kaspa confirms faster than chain X finalises."
Those are two different measurements. Confirmation is inclusion and ordering. Finality is when reversal becomes economically unrealistic. Kaspa is genuinely fast at the first one — say which one you mean.
Bring people here
and they leave
knowing something.
Most crypto communities are built on anticipation, which has a half-life. This one is built on a mechanism that is genuinely unusual and genuinely explainable. Post the signal board, hand out the creator kit, send newcomers to the consensus lab — and let the protocol do the convincing.
- A public wallPost a callsign and a take. Stored in Postgres, no links allowed, no accounts required.
- Six ready threadsCopy-and-post templates on the orphan problem, the chromatic curve, and what Toccata did and did not ship.
- A shareable scoreTwelve questions. Most people miss the red-block one. The result copies as a post.
- The briefing listReduction milestones, activation scores, and corrections when the timeline gets something wrong.