I’ve had SWAMP Neurons locked for 8 years, they have been locked at a time where the maximum dissolve delay what 8 years and where the SNS was still called ICPCC.
Now, the SNS has changed it’s name and voted to reduce the max dissolve delay to first 2 years and now 6 months.
My neurons are still locked for 8 years. I’ve tried to dissolve one and then change the dissolve delay but I’ve received this beautiful error: Invalid nat32 argument: -189345588 which I’m guessing is related to the governance canister calculating that I want to add a negative value, since my current dissolve delay is higher than what I can possibly “add” now.
Is this a known issue? If this is a common issue, then all the SNS are at risk and the long term stakers are essentially the turkey of the joke
Hi @Seb,
you should be able to try to “set” the dd to a non-zero (positive) amound and what SNS governance should do in the background is take the max of whatever value you provided & the current set maximum dissolve delay. In you situation, this should cause the dd to be lowered.
Note that this is not possible on the NNS dapp (as it would only allow the increase if it is below the current max), but should be possible via a direct call. I assume you have the option to do that from your message (as you get an error)?
I see - yes I was assuming you’d use dfx or similar.
Indeed, depending on the SNS, you could give another principal some permissions on your neuron, but also this is not possible on the NNS dapp as it hides such complexities from the users.
Thanks for the response, but there are some technical limitations that make this solution not feasible for Internet Identity users.
The issue is that Internet Identity can’t be can’t be extracted as a private key or PEM file. So there’s no way to import my II into dfx to make direct canister calls.
The other problem is that the NNS dapp frontend at nns.ic0.app doesn’t expose the ability to “set” dissolve delays - it only allows increasing them (and only up to the current maximum). The frontend logic prevents me from even attempting to set a lower value, so I never get to the point where the governance canister could take the max of my input and the current limit.
Since Internet Identity is domain-locked, I can’t modify or inject code into nns.ic0.app to bypass these frontend restrictions either.
So essentially, Internet Identity users with dissolve delays above the current maximum are stuck - we can’t use dfx, and the NNS dapp frontend won’t let us attempt the “set” operation you described.
This seems like we need either:
An update to the NNS dapp frontend to allow “setting” dissolve delays (not just increasing)
Or a governance canister fix to handle the existing “change dissolve delay” calls properly when the current delay exceeds the maximum
Is there any plan to address this? Because right now II users with old long-term stakes are essentially locked out of managing their neurons. If my analysis is correct this is a quite major bug/limitation.
