#Troubleshooting Unstaking Error

1 messages · Page 1 of 1 (latest)

pastel shuttle
#

Which Namadillo Interface are you using?

median elbow
#

This one

pastel shuttle
#

Would you mind switching to another browser Brave or other chromium. Install the wallet extension and import your wallet there. Then try

#

The interface is up to date.

#

You backed up your seeds yes?

median elbow
#

OK,thank you for your support,I do it now

pastel shuttle
devout oar
#

hi

#

just a quick hint

#

Brave is not supported yet . only chrome and firefox

#

so please try with firefox . thanks

pastel shuttle
#

Is there anything new that I'm unaware of?

median elbow
devout oar
median elbow
#

Still can not unstake and vote

pastel shuttle
#

Same error?

median elbow
#

yes

devout oar
#

which keychain version do you have ? also do you have any popup blocker installed in your machine ? one last thing .. can you please try with firefox . Thanks

median elbow
#

I try the firefox

pastel shuttle
devout oar
#

yup . now can you try with firefox

#

thanks

median elbow
#

Is that one?But few user

#

just 200 user

devout oar
#

yes thats the one

#

normaly ppl use chrome

median elbow
#

Just the same

devout oar
#

@pastel shuttle what do you think?

median elbow
pastel shuttle
#

Check if there's a pop-up. Minimise your browser if it's blocking the view.

median elbow
pastel shuttle
#

Please check this @dreamy slate . Transaction Approval Popup Not Showing Up.

median elbow
pastel shuttle
# median elbow

I have tagged Chris he might be able to help. Please wait for his reply 🙏. Don't worry, 😊

dreamy slate
#

There is currently an ‘unstake’ bug with the indexer and the UI that means an amount that was already unstaked is still showing as available unstake. Usually after multi unstaking

This is why there is no extension pop up. As there’s actually no value to unstake

Can you check the tnam address against an explorer and see if the unstake actually went through. You’ll have to dive into the specific transaction data

This is what happened to two other users and was the confirmed case.

There is is fix for this in the next indexer version that will automatically update the UI to show the correct information

dreamy slate
#

@median elbow

The following would be a quick instant fix.

Stake a tiny amount of NAM back to that validator that the extension doesn’t pop up for. That should trigger the indexer to update the values and show the initial unbond as successful.