Skip to content

Using a different RPC Provider

The SmartAccountClient within @alchemy/aa-core is unopinionated about which bundler you use, so you can connect to any RPC provider really simply.


If we look at the example for creating a SmartAccountClient:

import {
} from "@alchemy/aa-accounts";
import {
} from "@alchemy/aa-core";
import { http } from "viem";
export const chain = polygonMumbai;
export const signer: SmartAccountSigner =
export const rpcTransport = http(
export const smartAccountClient = createSmartAccountClient({
  transport: rpcTransport,
  account: await createLightAccount({
    transport: rpcTransport,

You can see that we set the transport to http(""). You can swap out that the url in the http function to any other provider's URL.

Splitting Bundler traffic and Node RPC traffic

It might be the case that you want to use a different RPC provider for your bundler traffic and your node traffic. This is a common use case, and you can do this by leveraging the split transport and passing it to your createSmartAccountClient call. For example:

import { createSmartAccountClient, sepolia, split } from "@alchemy/aa-core";
import { http } from "viem";
const bundlerMethods = [
const splitTransport = split({
  overrides: [
      methods: bundlerMethods,
      transport: http("BUNDLER_RPC_URL"),
  fallback: http("OTHER_RPC_URL"),
export const client = createSmartAccountClient({
  chain: sepolia,
  transport: splitTransport,

Zora and Fraxtal

Using a split Bundler and Node RPC setup is required for Fraxtal, Fraxtal Testnet, Zora, and Zora Sepolia networks since Alchemy currently only supports Account Abstraction endpoints for those networks. Please refer to documentation from Frax and Zora about RPC options.