backport: #8865 vesting account fix

[RoHoss]

It is not fixed.

I need a solution for this issue. Who can help?

Originally posted by @RoHoss in #9013 (comment)

[RoHoss]

"@type": "/cosmos.vesting.v1beta1.DelayedVestingAccount",
"base_vesting_account": {
"base_account": {
"address": "cro1xxxxxxxxxxxxx",
"pub_key": null,
"account_number": "0",
"sequence": "0"
},
"original_vesting": [
{
"denom": "basecro",
"amount": "632232016211"
}
],
"delegated_free": [],
"delegated_vesting": [],
"end_time": "1648170000"

Is delegating / send with this account possible or first after the end_time?

[tac0turtle]

Hey, thanks for opening this issue. We do have a bug template that we recommend following.

What version of the software is your node running? Has it been updated?

[tac0turtle]

The fix has not been backported it seems, #8865. I couldn't find it. this is why you have not had the issue fixed.

[aaronc]

This can't be backported because it is state breaking and requires a migration for live chains. New zones can fork the SDK temporarily (like we did), but most zones will need the migration which will be included in 0.43.

[tac0turtle]

oh okay. Thank you for the explanation!

@RoHoss You will have to wait till the next upgrade. The funds are safe.

[aaronc]

If crypto.com wants to address sooner they can. I believe Akash did something similar. The fact there is an unsupported type error makes me think there may be some other issue. If crypto.com maintainers want support in figuring out an intermediate solution they can let us know, but there's no easy immediate fix in the SDK.

[RoHoss]

Thanks for info. I transport it to CDC.