Contract interface and helpers for batching executions?

[dzmitry-lahoda]

Sometimes I have to call 4-5 times one contract execute to setup a lot of configs.

Is there a way people do to send one execute which does executes many messages?

I see options to implement something in contract. May be there is some standard way?

Or use some cosmos batching (non portable) PB messages.

[webmaster128]

This has been discussed quite a bit in CosmWasm/wasmd#72. I think at the end of the day the big question is always: what do you really save compared to individual calls? We have not found convincing arguments other than network roundtrips which can be handled by batching Tendermint RPC requests.

In this particular case, I think you still want a fresh Wasm instance between the messages to ensure no memory is shared between the calls.

[dzmitry-lahoda]

spend couple hours to do batch tx on osmosis from cli as per https://docs.cosmos.network/main/modules/auth#sign-batch . seem osmosis has old version of this. just does not work.

so question why ? because people do not maintain good cli tools, as option.

[webmaster128]

Signing multiple transaction does not seem the right way to do this as it adds unnecessary overhead and makes the operation non-atomic. What you should do is a single transaction with multiple MsgExecuteContract. However, I don't know if there is good CLI support for that. CosmJS allows you to do that via SigningCosmWasmClient.executeMultiple or .signAndBroadcast.

[dzmitry-lahoda]

I am working from bash. I tried to have 3 CW JSON messages to be sent at once. Because there is no way to do online txes and send these. I can do some offline txes, increment sequence numbers, send one by one. Will try again. But it is too hard.

So we did in CW to force batch config https://github.com/ComposableFi/composable/blob/b1a821545e8d062b7007c174c5c90ff2c51dc3dc/code/xcvm/cosmwasm/contracts/gateway/src/contract/execute.rs#L87

For contracts deploy in devnet, will use genesis.

[webmaster128]

But it is too hard

I don't disagree. But this needs to be fixed at a different part of the stack (Cosmos SDK). Sending a multi message tx is the right (tm) way to do this and the CLI should make that easy, no matter if those are CosmWasm messages or any other message type.