You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
What is the best way to determine which modules should be included in the supported modules repo?
Is there a better way of getting the proper code setup?
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?
The text was updated successfully, but these errors were encountered:
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:
The text was updated successfully, but these errors were encountered: