ZeroDev Account
Enable in Dynamic
Adding Multichain Providers (if desired)
Choose who gets a Smart Contract Wallet (SCW)
Choose if your users see both the signer and smart wallet
Enable Dynamic-powered embedded wallets + Email
Render Dynamic
ZeroDevSmartWalletConnectors
to your existing walletConnectors
array in the DynamicContextProvider
:^2.0.5
. For newer versions, use the latest compatible Dynamic SDK.environmentID
setting.Set up a gas sponsorship rule
Using the Kernel
getAddress()
, getConnectedAccounts()
or getNetwork()
before calling getAccountAbstractionProvider()
.ZeroDevSmartWalletConnectorsWithConfig
connector and pass in the bundlerProvider
prop with the value PIMLICO
.Send a transaction
ZeroDevSmartWalletConnectorsWithConfig
and pass in values for bundlerRpc
and paymasterRpc
:
ZeroDevSmartWalletConnectorsWithConfig
and pass in a value for bundlerProvider
:
getAccountAbstractionProvider()
52.204.85.87
54.145.74.8
107.20.170.238
52.206.26.56
3.232.2.67
44.213.187.169
Can I use an existing wallet as a smart contract wallet with account abstraction?
What networks are supported for deploying smart contract wallets?
Can I change the network for a smart contract wallet after it's deployed?
What happens if I don't want to use a provider i.e. ZeroDev any more?
What pricing package includes this feature?
What does private beta mean in this context, what should I expect?
How are private keys securely managed and stored for smart contract wallets with account abstraction?
What is the process for recovering a smart contract wallet in case of key loss or compromise?
Are your smart contract wallets non-custodial?
Why is it better to do this through Dynamic than integrating ZeroDev directly?