API Change: Neuron Minimum Dissolve Delay Constraint Update (Release ETA March 17, 2025)

[1eo]

We’re announcing an upcoming API change ETA March 17, 2025, that may affect your neuron-related functionality. Specifically, this update pertains to the constraint on the minimum dissolve delay required for neurons to propose or vote.

Action Required

All NNS downstream clients who have any neuron-related functionality should:

• check if they rely on the minimum delay constant (neurons’ min dissolve delay to propose / vote),
• and if so, they should start reading its value from the network economics API (NetworkEconomics.VotingPowerEconomics.neuron_minimum_dissolve_delay_to_vote_seconds) when it becomes available.

This change is a first step towards reducing the minimum dissolve delay to 3 months. If you have questions, feedback, or need assistance with the transition, feel free to reply here.

cc @aterga @nns-downstream-clients

[nadiein]

heya @1eo

could you please clarify the following:
1/ will the minimum_dissolve_delay_to_vote be part of response from the get_network_economics_parameters query call, or it will be separate one?
2/ what about maximum_dissolve_delay? still hardcoded to 8 years?

thanks

[1eo]

1/ Indeed it’s going to be part of the voting_power_economics field of get_network_economics_parameters query call.
2/ There’s no plan AFAIK to change the maximum delay, so no point in fetching it dynamically.

[nadiein]

1/ got it, thanks
2/ still nice to have everything consistent and achievable from the get_network_economics_parameters call. in the same way as for SNS projects from the get_nervous_system_parameters call.

anyway, step by step (: