# Dependency Conflict Between \`ic-cdk\` and \`sol\_rpc\_client\` When Using Non-Replicated Outcalls

**URL:** <https://forum.dfinity.org/t/dependency-conflict-between-ic-cdk-and-sol-rpc-client-when-using-non-replicated-outcalls/62468>\
**Category:** Rust\
**Tags:** HTTP-Gateways\
**Created:** [January 11, 2026, 3:50pm UTC](https://forum.dfinity.org/t/dependency-conflict-between-ic-cdk-and-sol-rpc-client-when-using-non-replicated-outcalls/62468 "2026-01-11T15:50:08Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Harshal0902](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/harshal0902/32/18495_2.png) [@Harshal0902](https://forum.dfinity.org/u/Harshal0902)\
**Post date:** [January 11, 2026, 3:50pm UTC](https://forum.dfinity.org/t/dependency-conflict-between-ic-cdk-and-sol-rpc-client-when-using-non-replicated-outcalls/62468/1 "2026-01-11T15:50:08Z")

</div>

I want to use **Non-Replicated Outcalls** to make calls to different chain RPCs, as our project runs on a canister and supports multiple chains via their respective RPC endpoints.

However, when I try to use the `sol_rpc_client` crate in my canister, I encounter the following dependency error:

```bash
error: failed to select a version for ic-cdk-executor
… required by package ic-cdk v0.17.2
… which satisfies dependency ic-cdk = "^0.17.2" of package sol_rpc_client v2.0.0
… which satisfies dependency sol_rpc_client = "^2.0.0" of package test_backend v0.1.0

versions that meet the requirements ^0.1.0 are: 0.1.0

package ic-cdk-executor links to the native library "ic-cdk async executor"
(see https://github.com/dfinity/cdk-rs/blob/links-pin/TROUBLESHOOTING.md),
but it conflicts with a previous package which also links to
"ic-cdk async executor":

package ic-cdk-executor v2.0.0
… which satisfies dependency ic-cdk-executor = "^2.0.0" of package ic-cdk v0.19.0
… which satisfies dependency ic-cdk = "^0.19.0" of package test_backend v0.1.0

Only one package in the dependency graph may specify the same `links` value.
This ensures that only one copy of a native library is linked in the final
binary.

failed to select a version for ic-cdk-executor which could resolve this conflict

```

From the error, it looks like **`ic-cdk` version `0.19.0` is not compatible with `sol_rpc_client` version `2.0.0`** , due to conflicting versions of `ic-cdk-executor`.

### My current `Cargo.toml`:

```toml
[package]
name = "test_backend"
version = "0.1.0"
edition = "2021"

[lib]
crate-type = ["cdylib"]

[dependencies]
candid = "0.10.10"
ic-cdk = "0.19.0"
serde = "1.0.228"
sol_rpc_client = "2.0.0"

```

### Questions

- Is `sol_rpc_client` currently incompatible with `ic-cdk >= 0.19.0`?
- Is there a recommended version matrix for using `sol_rpc_client` inside canisters?
- What is the best way to resolve this conflict when using **Non-Replicated Outcalls**?

Any guidance or best practices would be appreciated.

---

<div class="post-metadata">

**Author:** ![lpahlavi](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/lpahlavi/32/28161_2.png) [@lpahlavi](https://forum.dfinity.org/u/lpahlavi)\
**Post date:** [January 12, 2026, 5:05pm UTC](https://forum.dfinity.org/t/dependency-conflict-between-ic-cdk-and-sol-rpc-client-when-using-non-replicated-outcalls/62468/2 "2026-01-12T17:05:37Z")

</div>

Hi @Harshal0902! We’ve just released [`sol_rpc_client@4.0.0`](https://crates.io/crates/sol_rpc_client) which now depends on the `ic-cdk@0.19.0`. Note that although the new version of the client uses `ic-cdk@0.19.0`, the SOL RPC canister does not offer support for non-replicated outcalls yet.

---

<div class="post-metadata">

**Author:** ![Harshal0902](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/harshal0902/32/18495_2.png) [@Harshal0902](https://forum.dfinity.org/u/Harshal0902)\
**Post date:** [January 16, 2026, 6:29pm UTC](https://forum.dfinity.org/t/dependency-conflict-between-ic-cdk-and-sol-rpc-client-when-using-non-replicated-outcalls/62468/3 "2026-01-16T18:29:41Z")

</div>

Hi @lpahlavi thank you for the update. After upgrading to `sol_rpc_client@4.0.0`, everything is working fine now.
