All authentication flows are routed through Privy, including external/native wallets.
As a result, even the native EOA path (EOAHandler, which already talks to window.ethereum directly) cannot run unless Privy is initialized and authenticated.
We want to fully decouple the native wallet login from Privy:
Native wallet (EOA) → own stack eg: (wagmi + WalletConnect v2), independent of Privy.
Smart accounts (SCA) → Privy + Alchemy remain, powering email / google / passkey → smart-contract-account flows only.
All authentication flows are routed through Privy, including external/native wallets.
As a result, even the native EOA path (EOAHandler, which already talks to window.ethereum directly) cannot run unless Privy is initialized and authenticated.
We want to fully decouple the native wallet login from Privy:
Native wallet (EOA) → own stack eg: (wagmi + WalletConnect v2), independent of Privy.
Smart accounts (SCA) → Privy + Alchemy remain, powering email / google / passkey → smart-contract-account flows only.