Open llllllluc opened 7 months ago
Hi, thanks for the reference. We'll take this into account.
Hi, thanks for the reference. We'll take this into account.
Awesome, recently I'm thinking about creating a generalized version of osmosis-std, so it can be used for all cosmos sdk chains to generate rust proto and have out of box support in cw with stargate msg, maybe I can experiment that with babylon.
@maurolacy @SebastianElvis
Wonder if you guys have seen this discussion on deprecating osmosis binding. Recently when I'm building something that interact with contracts like cw20 or cw721, response of execution is pure
CosmosMsg
. I also use Neutron SDK to use token factory and response of execution isCosmosMsg<NeutronMsg>
. It caused some headache to define a response that can handle both. This makes me think it's probably a good idea to not have binding (e.g.NeutronMsg
orBablyonMsg
) in the first place, and just use proto generated type as stargate msg which is pureCosmosMsg
, similar to the osmosis-std.So in conclusion I guess the benefit of not having binding are: