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
Currently there are some third party dependency protos that are part of data on chain associated with our releases that are not included in our proto zip file release
Problem Definition
By not capturing all of the protos from third party dependencies like wasmd in our proto files clients are required to track down these dependencies when they need to decode this data. This is extra complicated because some of the protos change with the dependency version changes
Proposal
Ensure that all third party dependency protos are copied into the release proto zip file.
For Admin Use
Not duplicate issue
Appropriate labels applied
Appropriate contributors tagged
Contributor assigned/self-assigned
The text was updated successfully, but these errors were encountered:
Note on this: we want to make sure we use ultimate source of truth on the protos. so cosmos comes from cosmos, ibc comes from ibc, and wasm comes from wasm. Also, pulling ALL protos, not just used protos.
Summary
Currently there are some third party dependency protos that are part of data on chain associated with our releases that are not included in our proto zip file release
Problem Definition
By not capturing all of the protos from third party dependencies like wasmd in our proto files clients are required to track down these dependencies when they need to decode this data. This is extra complicated because some of the protos change with the dependency version changes
Proposal
Ensure that all third party dependency protos are copied into the release proto zip file.
For Admin Use
The text was updated successfully, but these errors were encountered: