Skip to content

Mainnet Crescendo Release - v1.0.0

Latest
Compare
Choose a tag to compare
@michaelsutton michaelsutton released this 31 Mar 22:33
eb71df4

This release introduces the Crescendo Hardfork, transitioning the Kaspa network from 1 BPS to 10 BPS. This marks a significant increase in transaction throughput and network capacity, as well as improved network responsiveness due to shorter block intervals, enhancing the overall user experience. Crescendo is scheduled to activate on mainnet at DAA Score 110,165,000, projected to occur on May 5, 2025, at approximately 15:00 UTC.

Starting 24 hours before activation, nodes will connect only to peers using the new P2P protocol version 7. Ensure your node is updated to maintain network connectivity.

Key highlights for Kaspa node maintainers

  • 10 BPS Activation: Mainnet will transition from 1 BPS to 10 BPS.
  • Retention Period Configuration: Operators now have greater control over data management with a new retention-period-days configuration. Due to the higher block rate, the pruning period has shortened from approximately 50 hours to 30 hours. If operators wish to retain the same amount of historical data as before, they should specify the desired retention period using the new configuration and ensure sufficient storage capacity is available.
  • Protocol Version Update: Nodes will switch to P2P protocol version 7. Ensure your node is upgraded to maintain connectivity.

Retention period configuration

The new retention-period-days parameter provides flexibility for node operators by determining how many days of historical data to retain.

Configuration Type Usage
retention-period-days f64 The number of days to keep data for. Must be at least 2. If not set, the node will default to keeping only data for the pruning period.

Example: Keep 2.5 days (=60 hours) of data using the following command:

./kaspad --utxoindex --retention-period-days=2.5

Crescendo specification

For full details of the changes activated in this hardfork, refer to KIP-14.

Node upgrade guide

Ensure your node is updated to stay compatible with the Crescendo Hardfork. For detailed instructions on upgrading and configuring your node, refer to the Crescendo Guide.


Full Changelog: v0.16.1...v1.0.0