Hi everyone, I’m developing ReTransICP and experiencing some trouble with the rpc canister: [30467. 2024-07-09T09:55:30.780289441Z]: Timer has finished, running job 4 now. [30468. 2024-07-09T09:55:40.790182797Z]: [TRAP]: Error: HttpOutcallError(IcError { code: SysTransient, message: "No consensus …

No consensus could be reached. Replicas had different responses. This error message occurs when calling the same RPC endpoint from different subnet nodes return different results. The most common reason for eth_getBlockNumber is that the block number changes partway through the HTTP request. It’s a…

I am also seeing this. “Waiting a few minutes” does not seem to change anything, the issue is quite persistent. I am using one rpc service only, on Arbitrum. Ok((Consistent(Err(HttpOutcallError(IcError { code: SysTransient, message: "No consensus could be reached. Replicas had different responses. …

Which RPC service and method(s) are you using? I’ll see if we can fix this if it’s possible for us to repro the issue. The reason we (currently) can’t return an inconsistent error message here is that HTTPS outcall consensus happens at the protocol level of the Internet Computer. Essentially, each …

[image] rvanasa: Which RPC service and method(s) are you using? I’ll see if we can fix this if it’s possible for us to repro the issue. Thanks! I had this issue today with the following configs: Arbitrum: BlockPi Base: Ankr/BlockPi Method used was eth_getBlockByNumber. Code is mostly copie…

[image] kristofer: The RPC responses are consistent but the nodes did not reach consensus. That would mean some of the nodes did not get any responses, right? So, a timeout issue or overload issue? This is usually caused by timeouts or rate limits on the individual JSON-RPC services. It’s als…

Thanks for looking into this, it is the last blocker preventing me from launching. I am … almost … certain though that when I first saw this error it happened a bit further down in the flow of the run_create canister function. Here, when I run the queries in the recipe to estimate gas usage for cre…

ps. I do some in canister logging that can be accessed in the logs() function here: https://a4gq6-oaaaa-aaaab-qaa4q-cai.raw.icp0.io/?id=7w3i7-3iaaa-aaaal-qi2iq-cai … and with the help of those can confirm that the issue happens for regular http_request outcalls also.

Thanks for the info! I tried running “Zero Eth Balance” several more times and got successful EVM RPC eth_getBlockByNumber responses in the logs. I’m seeing “Error creating run” on the webapp with a 500 status code in the dev console. It’s unclear what’s specifically causing this error. Is there an …

[image] kristofer: Most other eth functions you can tie to a block number to decrease this risk. But to establish a “starting point” to be used in coming calls you need to be able to get the latest block (or there around) reliably. As a quick follow-up question, do you encounter the “No conse…

So, I had an issue with the recipe query proxy as well that most likely caused the error you saw. That is fixed now. I had some consensus error earlier today but now the EVM RPC calls seems to go through. So I guess it was some load /quota issue before? I am running only one RPC provider per chain …

Evm rpc httpOutcallError No consensus could be reached

Developers Rust

kristofer August 23, 2024, 10:36pm 12

Hrm. EVM RPC calls fail again, now using one provider only. This time on Optimism/BlockPi.

Topic		Replies	Views
Intermittent Success and Failure in Sending get_transaction to Solana via Http Outcall Developers	6	203	September 9, 2024
HTTP POST outcalls consensus not working , only one is working Rust	12	589	August 4, 2023
HTTP request error. RejectionCode: SysTransient, Error: Canister http responses were different across replicas, and no consensus was reached Developers	8	447	January 14, 2025
EVM rpc canister issue while getting block_number Rust	0	30	July 9, 2025
HTTPS outcalls no response Developers	5	224	July 5, 2024

Evm rpc httpOutcallError No consensus could be reached

Related topics