Support for EIP-7702 (External Smart Accounts)

[FarajiOranj]

Hi team,

First of all, thank you for providing such an excellent widget, it’s been a pleasure integrating it into our stack.

I’m a Next.js/React developer working on an application that relies on EIP-7702 smart-session accounts to enable a fully gasless user experience. Our entire authentication and transaction flow is built around this model using the Thirdweb SDK, which internally manages wallet connections through Wagmi.

When using standard injected or extension wallets, the LiFi Widget integrates correctly and recognizes the external wallet connection.
However, when switching to or exclusively using the EIP-7702 account model, the widget no longer detects the active external wallet and it simply shows “Connect Wallet” even though a session and signer are already active.

I understand that the docs mention EIP-5792 support for batched transactions, but there is no mention of EIP-7702 anywhere in the widget or SDK documentation.

Because EIP-7702 is rapidly becoming a major UX improvement across the ecosystem, native support for external 7702-based accounts inside the LI.FI Widget would significantly enhance the user experience for teams like ours.

Would it be possible to clarify whether LiFi Widget plans to support external EIP-7702 sessions as a valid wallet provider, or whether there are known limitations preventing it?

Native support would be extremely valuable for developers adopting modern gasless UX patterns.

Thank you in advance, any guidance or clarification would be greatly appreciated.

[chybisov]

@FarajiOranj Hi, thanks a lot for the detailed report and for the kind words about the widget. We appreciate it ☺️

To clarify: both the LI.FI Widget and the LI.FI SDK have supported EIP-7702 and EIP-5792 from day one. From the widget’s perspective, an EIP-7702 account does not differ from a standard EOA in terms of how the wallet connection and signer are consumed. As long as Wagmi exposes an active connector and signer, the widget should be able to pick it up just like any other externally connected wallet.

To help us investigate, could you share a minimal reproducible example or point us to the relevant repository if it’s public? That will allow us to trace how the signer and connection state flow through Wagmi and identify where the detection might be breaking.

[FarajiOranj]

Thank you for your support and responsiveness.
I’m sending the issue in a video format, and I’d appreciate it if you could take a look.

https://jumpshare.com/share/g2MD7YeXi7tiZtHDHBrg

[chybisov]

@FarajiOranj In the video, when you connect via X, I briefly see a wallet appear in the top-right corner before it disappears. Could this be related to how thirdweb is implemented for that flow on your side?

From what I can see, there is nothing in the video that explains why this flow behaves differently from the MetaMask connection earlier in the video. If both flows rely on the same Wagmi context to pass the wallet state, it should work consistently. Might be worth checking whether the thirdweb connection is properly updating or persisting state in that context.