Backport #10515 to v0.44

[karzak]

Summary of Bug

Using v0.44.5, I cannot currently migrate multisig threshold accounts from v0.39 to v0.44 - this is because #10515 has not been backported.

Version

v0.44.5

Steps to Reproduce

On v0.44.5, add a line after

cosmos-sdk/crypto/keys/multisig/multisig_test.go

Line 430 in 33dbf6a

require.Equal(t, uint32(3), lpk.Threshold)

require.Equal(t, 5, len(pk.(*kmultisig.LegacyAminoPubKey).PubKeys))

The test will fail, because the PubKeys field is being lost.

To apply the backport, you need to cherry-pick both 1662e45 and 3d3bc7c

---

For Admin Use

• Not duplicate issue
• Appropriate labels applied
• Appropriate contributors tagged
• Contributor assigned/self-assigned

[amaury1093]

Ah yes, see #10871

[karzak]

@AmauryM any chance you can cut a v0.44.6 release this week? We are going to be upgrading the Kava blockchain shortly from v0.39 to v0.44 and ideally would like to pin to v0.44.6 rather than a commit hash.

[amaury1093]

Sure, we can do that tomororw

[amaury1093]

@karzak Probably today will be hard. Is Monday okay for a release? I started the release here: #10953, let's continue conversation there to not pollute this issue

[tac0turtle]

0.44.6 is cut with this