New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: DEVNET DSC was created from validator data - cannot unstake 1 node - public key mismatch #4488
Comments
Getting list of currently staked nodes from vm-values/query
|
Thanks for reporting this. We are aware of this problem and fix on the way. Although it will not make it in the v1.3.4x release, we are probably rolling it out on the v1.4.x release. Will link the fixing PR to this issue when it will become available. |
Thank-you for your response. I have 1 question. I plan to create a DSC on mainnet and merge my existing genesis validators to the DSC. If I proceed with this now on mainnet, will I be in a situation that in the future I could possibly have 1 node that I would never be able to unstake? Or, will the patch, once applied to mainnet in the future, mitigate the issue such that after the issue is patched, unstaking all nodes will be possible? |
Hi, Is this bug still around on testnet 1.4.10 ? Error: Could not get all blsKeys from registration data: error - public key mismatch |
Hi, the fix did not make it in the v1.4.10 release . It will come in the v1.5.x release and I will link the PR when it will become available. |
Hi @easy2stake, Upon further investigation, although the error messages are the same, in your case the |
Thanks @raduchis it worked. |
closing the issue as the issue seems to be solved. |
Contact Details
No response
Description
I created a DSC on DEVNET from existing validator data. One node cannot be unstaked due to public key mismatch error.
Node version
N/A
Host machine
N/A
Steps to reproduce
I created a DSC on DEVNET from existing validator data.
TXID a92415f38bc87a24a781b42e29524bfbda111c5359455be83dd8ab4c1e9ad51e
The transaction was issued using the web wallet, from the wallet that had previously been used to stake 6 validator nodes.
Wallet address erd1gzzc96mpflcq5lnat0dz7dryv74fnqu6ddkwrqnk32jk508hgkgqyfc5wy
Address of the DSC erd1qqqqqqqqqqqqqqqpqqqqqqqqqqqqqqqqqqqqqqqqqqqqqr8llllse9cj2t
As this was the first time I created a DSC, I wanted to try as many operations as I could, including unstaking, unbonding and removing all nodes.
I was able to unstake and remove all but one node. To remove the last one, I added new BLS keys to the DSC, but I still have one of the original keys staked and cannot unstake, or unbond, or remove it.
Each time I try to unstake the transaction fails with "
could not get all blsKeys from registration data: error - public key mismatch, key dedeffa6ae5e12405f18225fa348b4d5ec8cce423b21ce6c8ee6683ca495d951c20287e1b6230eb496c9c1b189c10c0b4e481ee278e8b60bbffa6c215d11dd5363cb1e8ca74a840bbce91aad6c30a7d9884d048de80f184d00e85dc22bb4dc04 not found"
TXID 56a7e3b349036cf354d4e151d45b05cdcafdd578afa9eb7d851dac4bb42353c7
On which network is the bug manifesting itself?
Devnet
Relevant log output
Code of Conduct
The text was updated successfully, but these errors were encountered: