v0.42 Tracking Issue

[clevinson]

It should be noted that Cosmos SDK based blockchains which do not use the default bech32 prefixes (e.g. all chains except the Cosmos Hub) should be waiting until v0.42 if they are planning to upgrade to a Stargate (>=v0.40) version of the Cosmos SDK. This is because of a bug in v0.41 in which non-cosmos based chains will not be able to properly handle evidence and jail validators (#8461).

Current outstanding blocking issues for v0.42 are as follows:

• Secp256r1 Support
  • Add secp256r1 Signing Keys Add secp256r1 Signing Keys #7718
  • Enable secp256r1 in Antehandlers Enable secp256r1 in Antehandlers #8515
• x/authz
  • Additional standard library x/authz Authorizations Additional standard library x/authz Authorizations #8312
• ADR028 Implementation
  • Refactor store keys to allow variable-length addresses Refactor store keys to allow variable-length addresses #8345
• Bug Fixes / Other
  • Cannot make block after skipped x/upgrade Cannot make block after skipped x/upgrade #8538
  • Update cosmovisor Update cosmovisor #8523
  • Permanently Locked Vesting Accounts Permanently Locked Vesting Accounts #8283!

Other issues / nice-to-haves can be seen on the github milestone here.

Update (March 3, 2021): After seeing several of the planned issues for v0.42.0 taking longer than expected, we've decided to plan for the release of v0.42.0 by cutting directly off of the existing v0.41.x line, with only a singular backport of #8461. This will essentially render v0.42.0 nearly identicial to v0.41.4, with the distinction that v0.42.0 is safe to use by all Cosmos SDK based chains, and not only the Cosmos Hub.

[alessio]

What's the ETA? Due date please?

[clevinson]

@alessio Hoping to have an RC by end of next week. I'll update the milestone due date.

[sahith-narahari]

Sorry for the unpin, it was unintentional and didn't realize I did it.

[alessio]

Release is out. Hence closing. Thanks all!