Feature Request: Out of the box Account Abstraction support about build-onchain-apps

[uneeb123]

if possible, I think it would be best to not rely on a 3rd party embedded wallet service for this

Disagree because this implies that embedded wallets (hence MPC) is an alternative to account abstraction. It's not. In fact, MPC will work together with AA. AA happens at the contract level whereas MPC is relevant at the key abstraction level. Unfortunately, most AA demos as of today are also demo-ing key abstraction. Benefits of AA are batched txs, paymasters etc.

EDIT: I agree that there is should optionality to choose the right embedded wallet service for your needs. But ultimately, they need to work together somehow.

[Zizzamia]

I agree 100% on this: Account Abstraction is a must.

I love that you played with a few options out there. I would love to hear more about your experience with them and what the trade-offs you saw are.

Besides the two you mentioned, I also heard about https://www.privy.io, https://web3auth.io/ and https://www.dynamic.xyz.

As of right now, something I want to triple-check is the Javascript dependency they have. Build Onchain Apps loves Viem and Wagmi because they care about being lightweight, a trade-off I want to remember when picking something out there.

What are other trade-offs that are worth to count?

[uneeb123]

+1 to this. I don't have much to add to this since I think AA is still in early days. But there is also a way to combine Privy with AA: https://docs.privy.io/guide/frontend/account-abstraction/zerodev

[MrKevinOConnell]

@Zizzamia

As of right now, something I want to triple-check is the Javascript dependency they have. Build Onchain Apps loves Viem and Wagmi because they care about being lightweight, a trade-off I want to remember when picking something out there.

Both account kit and biconomy use viem, I'd imagine that it might be good to at some point setup functionality to index events from a contract(s). In this case account kit might be better since alchemy supports this also, thus you could use the same alchemy account for both. I have heard plenty of great things about biconomy though.

Besides the two you mentioned, I also heard about https://www.privy.io/, https://web3auth.io/ and https://www.dynamic.xyz/.

Hypeshot uses privy: its very great in my experience, they don't have a full passkey flow yet if that is important. Dynamic has this, and they have account abstraction (its in beta though). I personally haven't interacted with web3auth so can't comment on them.

if possible, I think it would be best to not rely on a 3rd party embedded wallet service for this. Given this will hopefully be the default for those making projects on base, I'd rather not eventually have a situation where that service is the default to use, and can trigger vender lock in at any point. Implementing one of the aa services above though would be great, as imo its more flexible to change between them if wanted.

[artivilla]

I personally like how nextjs showcases each integration in their examples directory which makes it easy to dissect which vendors a developer wants to integrate. There are certainly maintainability tradeoffs here.