Reduce packages coupling

[robert-zaremba]

Summary

This is a meta issue to track and solve tight coupling between packages, notably:

• core importing x/*
• simapp
• simapp "master config".

Description

Coupling is a source of the evil in many projects. Though it is helpful at the beginning, because we put things together and can iterate faster. Once the project grows and goes out of few packages level coupling start to be problematic. Usually the bigger a project is, the worse effect of coupling we have. The problems grow exponentially, because one change can induce a waterfall of other changes or even problems.

Items

• Proof of concept for breaking module packages per responsibility Proof of concept for breaking module packages per responsibility #7368
• simapp -> get inspiration from Band protocol.
• Decouple auth module from other SDK top-level core packages Decouple auth module from other SDK top-level core packages #7318
• Limit the creation of uncessary EncodingConfigs Limit the creation of uncessary EncodingConfigs #7631
• Remove global amino codec instances Remove global amino codec instances #7310

---

For Admin Use

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

[robert-zaremba]

I had a look at the Band Protocol code, and it seams that they found fine design for to packages organization and app creation.

[alexanderbez]

I had a look at the Band Protocol code, and it seams that they found fine design for to packages organization and app creation.

Would you like to elaborate @robert-zaremba?

core importing x/*

What is "core"?

[robert-zaremba]

core SDK packages are packages which are not in x/* and not a simapp.

Ideally, core should be self contained. I a significant amount of time in #7318. Moving things creates new import cycles. Also, there are many structures related to auth which are spanned across packages. This caused some hacks in the SDK.

Similarly EncodingConfigs, especially the MakeTestEncodingConfigs. It's at the center of many tests. Moreover, even in single test context we have few codec objects, because we don't manage them properly. There should be only one codec instance in one "runtime".

Finally, we mix a testing functions in the production packages. I already cleaned some parts when doing the bech32 PK removal.

[alexanderbez]

Ideally, core should be self contained.

Yes, as much as possible!

What does Band do differently that you'd like to adopt?

[robert-zaremba]

It feels less messy then the simapp.

[tac0turtle]

part of app wiring we are doing now