How have Kaspa node storage and processing requirements improved recently?

Recent changes to the Kaspa node software significantly reduced the storage space and CPU overhead required to run a node. Two key changes drove most of the gain: compressed block-header data in network handling, and smarter on-the-fly relationship tracking that avoids maintaining every inter-block link at all times. Contributors reported large real-world improvements, including up to ~3x faster header-stage IBD on some machines, with lower storage pressure especially on archival setups. For node operators, this means running a full Kaspa node demands less disk space and completes initial sync faster — making home-node participation more practical.