How does Kaspa keep lane history from bloating node storage?

Kaspa marks a lane as 'active' only when it has seen recent transactions, and quietly removes lanes that have gone quiet. In KIP21, a configurable setting called the activity window parameter F defines how recent a lane's last transaction must be for that lane to remain active. Any lane older than that window is considered inactive and can be purged from the node entirely. This keeps the set of lanes a node must store roughly proportional to current network use, not the full historical record. For node operators and the long-term health of the network, this design means running a full Kaspa node stays practical even if many different applications have used the network over the years.