WalletClient, an EIP-1193 provider, a viem LocalAccount, or an ethers.Wallet qualifies as a signer, which means you can keep using whichever auth or wallet stack you already trust.
Source:
StartaleGroup/scs-aa-sdk. For the full signer matrix, see Installation and setup.Where the auth provider fits
The auth provider’s only job in this diagram is to produce the signer that goes intotoStartaleSmartAccount. Everything downstream (bundler, paymaster, EntryPoint) is identical regardless of how the user logged in.
Why social login + AA is a good combination
First-party integrations
Dynamic
Embedded wallets, social and email login, MPC and WebAuthn key custody. Exposes a viem
WalletClient directly.Privy
Email, OAuth, and external wallet login. Exposes an EIP-1193 provider you can wrap with
createWalletClient.Bring your own provider
Any provider that exposes one of the four signer shapes will work. The integration shape is always:Next steps
Dynamic integration
End-to-end Dynamic + Startale AA SDK setup.
Privy integration
End-to-end Privy + Startale AA SDK setup.
Installation and setup
The full signer matrix and how to choose between options.
Smart account setup
Wire the signer into a persisted React provider.