3rd Party Bundlers
The SmartAccountClient
within @aa-sdk/core
is unopinionated about which bundler you use, so you can connect to any RPC provider really simply.
Usage
If we look at the example for creating a SmartAccountClient
:
You can see that we set the transport
to http("https://polygon-mumbai.g.alchemy.com/v2/demo")
. You can swap out that the url in the http
function to
any other provider’s URL.
Depending on your provider, you may have to pass in custom logic for the
gasEstimator
and feeEstimator
properties when calling
createSmartAccountClient
. Consult with your provider on what the correct
logic is.
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:
Using Alchemy Bundler and Gas Manager with 3rd Party Node RPCs
If you want to split your node traffic from Alchemy’s Bundler traffic, you can do this with the alchemyTransport
Using two different 3rd Party Bundler and Node RPCs
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.
See this guide for more information on using AA only chains with Account Kit.