How did Crescendo affect Kaspa node operators?

After the Crescendo Hardfork, Kaspa nodes must run P2P protocol version 7 to stay connected to the network. A node is software that participates in the Kaspa network by storing and relaying transaction data; running one requires keeping it updated whenever the network rules change. Because the block rate jumped to 10 BPS, the default pruning period — how long a node keeps historical data — shortened from approximately 50 hours to 30 hours. Operators who need longer history can set the new retention-period-days configuration option, but must ensure they have enough storage to match. If you run a Kaspa node, upgrading before a hardfork activates is essential: unupgraded nodes lose the ability to communicate with the rest of the network.