Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reseaerch high-impact custom chain modules and how to include them #4

Open
pharr117 opened this issue Sep 1, 2024 · 0 comments
Open

Comments

@pharr117
Copy link
Collaborator

pharr117 commented Sep 1, 2024

The modules make use of protobuf type definitions and code-generation to include new custom message types in the set of available modules.

Each Cosmos SDK module can include new Transaction message types, which the application will need to know how to decode in order to pull the data out.

We should research some of the following:

  1. What is the best way to determine which modules should be included in the supported modules repo?
  2. Is there a better way of getting the proper code setup?
  3. The application is Apache 2.0 licensed and opensource, are there modules that we would need to consider licensing for that may prevent/make it difficult to include in the modules list?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: No status
Development

No branches or pull requests

1 participant