During stOSMO price feed onboarding, Simply staking reported an issue that was affecting one of the NOPs 01node ->
'Error: key is not a valid name or address: Bytes left over in UnmarshalBinaryLengthPrefixed, should read 10 more bytes but have 153'
'we found a workaround but it is still happening. I read that it might be happening because the keys were imported with an older version of cosmos sdk and are being accessed with a newer version of cosmos sdk (again not sure if its the case);
To Reproduce
Steps to reproduce the behavior:
when prompted:
'Not sure exactly, all we did was run
agd keys list
But the keys might have been imported using an old agd version'
Expected behavior
A clear and concise description of what you expected to happen.
Describe the bug
During stOSMO price feed onboarding, Simply staking reported an issue that was affecting one of the NOPs 01node ->
'Error: key is not a valid name or address: Bytes left over in UnmarshalBinaryLengthPrefixed, should read 10 more bytes but have 153'
'we found a workaround but it is still happening. I read that it might be happening because the keys were imported with an older version of cosmos sdk and are being accessed with a newer version of cosmos sdk (again not sure if its the case);
To Reproduce
Steps to reproduce the behavior: when prompted: 'Not sure exactly, all we did was run agd keys list But the keys might have been imported using an old agd version'
Expected behavior
A clear and concise description of what you expected to happen.
other context: https://agoricopco.slack.com/archives/C03KCPAE4A1/p1707774957932779?thread_ts=1707489868.968649&cid=C03KCPAE4A1