[Bug]: DEVNET DSC was created from validator data - cannot unstake 1 node - public key mismatch about mx-chain-go HOT 9 CLOSED

Hi,

Is this bug still around on testnet 1.4.10 ? We're having the same issue when trying to unjail our nodes that are under our Delegation Contract.

Example TX: https://testnet-explorer.multiversx.com/transactions/ae3f6ae3aa54e6bc3225dd3520fe5fee30f9992539e516e92773abd299424198#2caf78c2e2abdad7e3fd79f57c6a73fda97e3cc697844fc111f49691062b426c

Error: Could not get all blsKeys from registration data: error - public key mismatch The transaction was sent from the wallet that deployed the Delegation Contract.

Hi @easy2stake,

Upon further investigation, although the error messages are the same, in your case the unJail transaction was not formatted correctly. Please use the unJailNodes method described here for Delegation Contracts: https://docs.multiversx.com/validators/delegation-manager#unjailing-nodes with the receiver: <address of the delegation contract>

from mx-chain-go.

Thanks @raduchis it worked.

from mx-chain-go.

Getting list of currently staked nodes from vm-values/query

$ API_SERVER="https://devnet-gateway.elrond.com/vm-values/query"
$ CONTRACT_ADDRESS="erd1qqqqqqqqqqqqqqqpqqqqqqqqqqqqqqqqqqqqqqqqqqqqqr8llllse9cj2t"
$ data="{\"scAddress\": \"${CONTRACT_ADDRESS}\", \"funcName\": \"getAllNodeStates\"}"
$ response=$(curl -s -k --data "${data}" "${API_SERVER}")

$ echo $response | jq -r '.data.data.returnData[]'
c3Rha2Vk
3t7/pq5eEkBfGCJfo0i01eyMzkI7Ic5sjuZoPKSV2VHCAofhtiMOtJbJwbGJwQwLTkge4njotgu/+mwhXRHdU2PLHoynSoQLvOkarWwwp9mITQSN6A8YTQDoXcIrtNwE
yv5MSwnChsiZh8VSFli9aY85/PCXoI/nrpwRGm+WA8GKWJE2LXX/JwNmb0/LOwQXq3rMKDi+pkEb05bAouAfT6XDBzf4fzcLzxrTcIvkX+M2/K3YR9UfeOdCMHqV1myH
yv5MlXFRBpnav8ekvJRGy13F341bv/pPLk/ncJ7aVMYCn2AWcNg7IMYbYrvgRyIPrz7w7yGG8LKY/z6IrNvB/tyPwf2sGLnqlTpBTE+uMciJYLAjr0yTZEbreuG31ryQ
yv5aS9EmUCt3uIdSctpawZ/Bpg9DNmW+a2J9aeopb/+qNV48JDIu1nQKSmPT5LkTv5vAg5CSq9aOq+jmYrOi4LAblxx729UakYduNznNG585XYnQ6lZfE3BrJYbyCFIO
yv5eE/olGwXCatqrlHo2Dc/o8EeqkdQQXncbST1dbvcdSjYWJ/3gELXP1dnS8/YVCzQgFqJCLo1GSNO1J3qo0tLqe5G5tLCWWDNOcXf8ilKHmheiXiufAMN+92Xq6MkO

$ echo $response | jq -r '.data.data.returnData[0] | @base64d'
staked

$ echo $response | jq -r '.data.data.returnData[1]' | base64 -D | xxd -p -c256
dedeffa6ae5e12405f18225fa348b4d5ec8cce423b21ce6c8ee6683ca495d951c20287e1b6230eb496c9c1b189c10c0b4e481ee278e8b60bbffa6c215d11dd5363cb1e8ca74a840bbce91aad6c30a7d9884d048de80f184d00e85dc22bb4dc04

from mx-chain-go.

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.

from mx-chain-go.

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?

from mx-chain-go.

@raduchis

from mx-chain-go.

Hi,

Is this bug still around on testnet 1.4.10 ?
We're having the same issue when trying to unjail our nodes that are under our Delegation Contract.

Example TX:
https://testnet-explorer.multiversx.com/transactions/ae3f6ae3aa54e6bc3225dd3520fe5fee30f9992539e516e92773abd299424198#2caf78c2e2abdad7e3fd79f57c6a73fda97e3cc697844fc111f49691062b426c

Error: Could not get all blsKeys from registration data: error - public key mismatch
The transaction was sent from the wallet that deployed the Delegation Contract.

from mx-chain-go.

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.

from mx-chain-go.

closing the issue as the issue seems to be solved.

from mx-chain-go.