dir improvements: move some stuff from params

[yperbasis]

Part of #14554

[antonis19]

What do you think about having all constants such as configs, parameters etc. in the params package?

So instead of having libchain, params, and misc we just have params.

To me this makes imports way easier to remember.

[yperbasis]

What do you think about having all constants such as configs, parameters etc. in the params package?

So instead of having libchain, params, and misc we just have params.

To me this makes imports way easier to remember.

What I want to arrive to eventually is something like this – a set of cohesive and loosely coupled modules. Ideally the more foundational modules should know little or nothing about concrete blockchains (e.g. all Polygon-specific stuff should be inside the polygon module). From that viewpoint having all parameters sitting in one place is not desirable (e.g. I'd like to eventually move things like BorMainnetGenesisHash, etc to polygon instead of params/config.go.

[taratorio]

What do you think about having all constants such as configs, parameters etc. in the params package?
So instead of having libchain, params, and misc we just have params.
To me this makes imports way easier to remember.

What I want to arrive to eventually is something like this – a set of cohesive and loosely coupled modules. Ideally the more foundational modules should know little or nothing about concrete blockchains (e.g. all Polygon-specific stuff should be inside the polygon module). From that viewpoint having all parameters sitting in one place is not desirable (e.g. I'd like to eventually move things like BorMainnetGenesisHash, etc to polygon instead of params/config.go.

that will be a great improvement! 🚀