Why does Kaspa keep red blocks if they don't count toward consensus?

Kaspa retains red blocks in the DAG even though they are excluded from consensus decisions, because the protocol needs a complete record of all blocks for accurate network state tracking. Red blocks are produced by honest miners whose work arrived slightly out of step with the blue-block set; discarding them entirely would mean losing part of the network's history. By keeping both blue and red blocks, GHOSTDAG maintains a full picture of every block ever created, which supports the integrity and auditability of the entire DAG. For a beginner, this means Kaspa treats miners more fairly — their work is recorded even when it doesn't directly drive consensus — and the network is never operating on an incomplete view of its own history.