Sam Hart

yes exactly. feels like it's kind of important to consider the module/submodule structure in its entirety here, as that would impact how we want to structure capability fields in the...

This is how the sdk will be specifying sdk module configs in the near future btw https://github.com/cosmos/cosmos-sdk/blob/main/simapp/app.yaml

I think we should use a standard that allows for this, most likely [IPLD](https://github.com/cosmos/cosmos-sdk/discussions/9505) ([updating docs](https://ipld.io/docs/schemas/using/migrations/)) or [DID](https://github.com/allinbits/cosmos-cash/blob/main/docs/Explanation/ADR/adr-004-did.md).

> Will be wanting to use chain reg as a sub-module, so this seems increasingly important. Interesting. Can you say more about your use-case @JeremyParish69? A git submodule?

@aaronc definitely not an immediate need, but if there was support for standardisation, creating a multi-stakeholder repo for proto files and related documentation makes a lot of sense.

https://github.com/forbole/cosmos-rust-wallet

yeah, good question. particularly as AIB is building out a new ecosystem page that includes these classifications. maybe @lovincyrus @nassdonald or others at AIB have ideas?

having an understanding of which projects are on which version of the SDK is also useful for the module ecosystem as modules from different point releases currently aren't compatible. unifying...

that's fair. I think a first pass of just getting everything on one page and then making the information more granular is a good strategy.

This is definitely V2