unstake issue

[cloud token]

creating a thread here, will have to get back later

[cloud token]

can you supply screenshots of what happens?

have you tried raising gas?

[shrewd hound]

yes

both unstake and redelegate not working. when I click that unstake botton nothing happen

tnam1qpur87kyc8fcuq8mufg80ex96y9h8e9lfvg533kh

I have 1k+ nam for gas. I redelegate last month

[cloud token]

@misty kraken this was the problematic validator, right?

or am I mixing them up?

[cloud token]

will discuss and get back to you.

[misty kraken]

Yes, it was.
Incident epoch 1660 was started on January 23, 2026
This delegation was also affected

[cloud token]

which namadillo are you using?

[shrewd hound]

u mean the website？

namadillo.app

[cloud token]

could you try namadillo.5elementsnodes.com and see if the stake displays differently?

long story short, it looks like your stake got slashed due to a double-sign event that happened for that particular validator.

[shrewd hound]

same

[misty kraken]

could you please try to redelegate again with Chrome console opened ad share with us the log?

[misty kraken]

thank you 👍

[shrewd hound]

it seems like I have to wait until epoch 1836?🥲

[misty kraken]

As mentioned by @cloud token, the validator in question, along with all its delegations, was heavily penalized due to multiple infractions. The result is that also your bond was entirely affected by the slash and has been lost.
If you manage to submit the redelegation tx in the future, unfortunately this will not reverse the slash. What I expect instead is that, once the unbonding is processed, the slash will be accounted for and you will see staked balance 0

[shrewd hound]

So you mean that it will automatically unstake at that time, right?

and my nam will get back？

[misty kraken]

Unfortunately no.
Since the validator was fully slashed, all the bonded NAM was unfortunately lost and will not be returned 🫂