Simple EOA as SmartAccount owner?

[pepoospina]

I'm setting up my app prototype, and I would like users to use email/OTP or EOA (metamask) to authenticate. Independently of the method, the app will work using SmartAccounts and User Operations.

I configure AlchemyAccountProvider UI to support external wallets, but when I get the client using:

  const { client, address } = useSmartAccountClient({});

I see a warning on the console when I connect with metamask:

"EOA is connected, will not return an SCA client".

From the docs, it seems I can use an EOA as a signer, but I will have to create a new client again, instead of using the one from <AlchemyAccountProvider>.

I'm confused. What is the simplest way to have one client manage my user operations, independently of the origin of the signer? EOA or email/otp?

[pepoospina]

In fact, when I try to send a UserOp I endup sending a Transaction instead, and I see the warning

TransactionManager.tsx:32 useSendCalls: connected to an EOA, sending as a transaction instead

[pepoospina]

I tried mixing useSmartWalletProvider with the manual modular account apprach described here, but it is tricky as the useSendOperation hook thinks the EOA is connected and skips the user operation management logic.

I think I will start with EOA-only for now, and avoid the user operations. I really need to support external wallets (and hardware wallets)