How does Kaspa handle the pruning boundary when block speed increases?

When Kaspa activates a higher block-per-second rate, the pruning depth — how many blocks must exist before old data can be discarded — increases to match, but the pruning boundary itself does not jump backward right away. Instead, the boundary stays fixed at its current position and only advances once a sufficient number of new blocks have accumulated above it under the updated rules. Think of it like a high-water mark: it can only rise, never fall. For everyday users, this means a protocol upgrade to faster block production does not disrupt existing nodes or require them to re-fetch already-pruned data.