Implement ADR 028 and Address Follow-ups

[aaronc]

• Finalize ADR-28 Finalize ADR-28 #8397
• add address generation algorithm adr-028 address generation #8415
• store key refactor
• migrations for storkey refactor Refactor store keys to allow variable-length addresses #8345
• Enable secp256r1 in Antehandlers Enable secp256r1 in Antehandlers #8515

Nice to have

• Update building a module documentation with section about address generation #9916

Follow-ups (out of scope for v0.42)

• Update simapp to use new modulekey format
• Implementation for derived submodule addresses Implementation for derived submodule addresses #8516

[aaronc]

/cc @robert-zaremba

[robert-zaremba]

I will be happy to handle this task. I like it.

[colin-axner]

It'd be good to add recommended prefix sizes or explain why the size wouldn't matter, ref

[colin-axner]

Has ADR 28 been implemented? Is there a different issue to track it? I see unchecked tasks on this issue and the ADR documents the status as Proposed

For the IBC application called Interchain Accounts, we need to generate account addresses using the portIDs. This is the same issue we ran into for the IBC transfer module. In that case, a manual check that none of the escrow addresses used would collide was sufficient, but I'm wondering if there is a more sustainable fix in place?

[robert-zaremba]

ADR-28 is implemented and being released in v0.43. I've just updated the checkboxes.

• If you want to generate a module account account (eg: ibc/some_key) then you should use Module(moduleKey, []byte("some key")).
• if you want to create a subaccount (eg: account1/subkey), then you should use Derive(account1, subkey). Note: account1 can be a module account.

[colin-axner]

Awesome, thank you for the response @robert-zaremba!