Error: post failed: Post "http://MY_IP:26657": EOF

[99Kies]

my code:

pub fn execute_batch_publish_message(
    _deps: DepsMut,
    env: Env,
    _info: MessageInfo,
    messages: Vec<Message>,
    enc_pub_keys: Vec<PubKey>,
) -> Result<Response, ContractError> {
    assert!(messages.len() == enc_pub_keys.len());

    let mut msgs = vec![];
    for i in 0..messages.len() {
        let publish_message = ExecuteMsg::PublishMessage {
            message: messages[i].clone(),
            enc_pub_key: enc_pub_keys[i].clone(),
        };

        let msg = WasmMsg::Execute {
            contract_addr: env.contract.address.to_string(),
            msg: to_binary(&publish_message)?,
            funds: vec![],
        };
        msgs.push(msg);
    }

    Ok(Response::new()
        .add_messages(msgs)
        .add_attribute("action", "batch_publish_message"))
}

I need to batch execute a method, but I'm getting this error when calling it.

my command:

log:

Error: post failed: Post "http://MY_IP:26657": EOF

[99Kies]

@webmaster128 anyone can help me. I think it's config problem of chain.

[webmaster128]

I don't know what this means, sorry

[99Kies]

@webmaster128 Sorry, the problem lies in the fact that I don't know what is causing the error to be reported. It doesn't look like a problem with the contract code.

I started a chain that supports cosmwasm, but the rpc says "post failed" when sending this transaction.

What are the chain configurations(config.toml) that affect the contract method calls? I have a feeling that it's taking too long to process the transaction and that's causing the error.

[99Kies]

@webmaster128

It's because of this configuration, I adjusted it to come out with 3 messages in 30s, but as the messages increase, the limit here is going to increase. What should i do....

[99Kies]

I think that I'm here because a transaction body contains too many messages, so it's taking too long for the transaction to take place.
Can I batch send the transaction in the client sdk? (I don't want the user to call the wallet signature many times)

[webmaster128]

timeout_broadcast_tx_commit is relevant when you submit a transaction and wait for the block inclusion. Ideally you don't use that and just return once the transaction is in the mempool. The behaviour will depend a lot on the chain. If you have a 6s block time and your transaction takes too much gas to fit in the next block, it will be in the mempool a bit longer. You should track the gas usage as well as the chain's block gas limit to see how much you can do in one transaction.

[99Kies]

Sure, here I should not put multiple duplicate transactions in a batch method, which would lead to an uncontrollable size of my transaction body.

[99Kies]

@webmaster128 However, does comjs support batch initiating transactions?

such as

let msgs = [client.publish_message(A), client.publish_message(B), client.publish(C)...]
signTxAndSend(msgs, wallet.getSigner())

[webmaster128]

Yeah, with signAndBroadcast you can create a transaction with multiple messages. This is the same that executeMultiple does under the hood. You'd just change the MsgExecuteContracts to MsgInstantiateContracts.

[99Kies]

@webmaster128 I tried this and he still encapsulates multiple messages into a single transaction. so still running into the above problem. Is there a schedule kind of module that automatically splits the message in a big transaction into multiple transactions.

[webmaster128]

Is there a schedule kind of module that automatically splits the message in a big transaction into multiple transactions.

Nope. Transacton execution is always atomic by design. I.e. it is either executed fully or not at all.

[99Kies]

@webmaster128 But some large number of polls and transfers demand this method? Because there is no correlation between each message.

[webmaster128]

It's up to your use case to decide in how many transactions you split your messages

[99Kies]

But this doesn't seem to be user friendly as he needs to do many times to repeat the signature and send the transaction.

[99Kies]

@webmaster128 I actually just want to make it possible for a user to initiate multiple transactions by just evoking the wallet once during a frontend interaction.