Dark | Light
[GUEST ACCESS MODE: Data is scrambled or limited to provide examples. Make requests using your API key to unlock full data. Check https://lunarcrush.ai/auth for authentication information.]

![realsrt_ Avatar](https://lunarcrush.com/gi/w:24/cr:twitter::1613099942477979649.png) SRT [@realsrt_](/creator/twitter/realsrt_) on x 1705 followers
Created: 2025-07-21 13:11:47 UTC

Are we getting an @infinex wallet extension?

In my opinion, this isn't what most people think. It likely won’t be a typical wallet extension.

We can look at it in two ways:
X. Connect UX enhancement
X. A full-fledged Infinex wallet extension

Let’s start with the Connect UX enhancement angle:

If you’ve used dApps on Connect, you know each one is built using the Connect SDK. This SDK abstracts all the signing and handles gasless transactions, which is the core of Infinex's UX.

Now, about the extension in this context:

From my testing of the alpha version, there's a popup that starts a session with the dApp. To make this more seamless, the team might be working on an extension to manage these signings and interactions more smoothly.

However, based on what we've seen so far, this won’t let us connect to dApps that aren’t part of the Infinex Connect. That’s because external dApps won’t support Connect unless they integrate the SDK.

Even in the screenshot shared by Ben, it clearly says “Infinex Connect” not “Infinex Wallet.” That suggests it only works with dApps built on the Connect SDK. (I'm just speculating)

Now, let’s talk about the idea of a full Infinex wallet extension:

If it ends up being a separate browser wallet like others, it might offer a better UX than the existing ones. But this would shift Infinex’s core vision.

Their approach so far has been:
> No extension required
> No tab switching
> Full account abstraction

So in my view, this won’t be a complete standalone wallet extension. It’s more likely a addition to enhance the Connect experience.

If Infinex chooses the traditional wallet path, it might help them find product-market fit faster, but it would come with certain trade-offs.

All of this is based on my experience with Connect, what we’ve seen so far, and how the team has been positioning it.

If they do decide to go with a full extension route, that’s possible too. But as of now, we don’t have confirmation.

One reason that could make things challenging for the team is getting external dApps to adopt Infinex Connect. This could be one reason why the team might consider going the extension route, to support a wider range of dApps without needing SDK integration.

This is my view on the Infinex Extension.

![](https://pbs.twimg.com/media/GwYc3zXbUAAeppr.jpg)

XXXXX engagements

![Engagements Line Chart](https://lunarcrush.com/gi/w:600/p:tweet::1947283363934752839/c:line.svg)

[Post Link](https://x.com/realsrt_/status/1947283363934752839)

[GUEST ACCESS MODE: Data is scrambled or limited to provide examples. Make requests using your API key to unlock full data. Check https://lunarcrush.ai/auth for authentication information.]

realsrt_ Avatar SRT @realsrt_ on x 1705 followers Created: 2025-07-21 13:11:47 UTC

Are we getting an @infinex wallet extension?

In my opinion, this isn't what most people think. It likely won’t be a typical wallet extension.

We can look at it in two ways: X. Connect UX enhancement X. A full-fledged Infinex wallet extension

Let’s start with the Connect UX enhancement angle:

If you’ve used dApps on Connect, you know each one is built using the Connect SDK. This SDK abstracts all the signing and handles gasless transactions, which is the core of Infinex's UX.

Now, about the extension in this context:

From my testing of the alpha version, there's a popup that starts a session with the dApp. To make this more seamless, the team might be working on an extension to manage these signings and interactions more smoothly.

However, based on what we've seen so far, this won’t let us connect to dApps that aren’t part of the Infinex Connect. That’s because external dApps won’t support Connect unless they integrate the SDK.

Even in the screenshot shared by Ben, it clearly says “Infinex Connect” not “Infinex Wallet.” That suggests it only works with dApps built on the Connect SDK. (I'm just speculating)

Now, let’s talk about the idea of a full Infinex wallet extension:

If it ends up being a separate browser wallet like others, it might offer a better UX than the existing ones. But this would shift Infinex’s core vision.

Their approach so far has been:

No extension required No tab switching Full account abstraction

So in my view, this won’t be a complete standalone wallet extension. It’s more likely a addition to enhance the Connect experience.

If Infinex chooses the traditional wallet path, it might help them find product-market fit faster, but it would come with certain trade-offs.

All of this is based on my experience with Connect, what we’ve seen so far, and how the team has been positioning it.

If they do decide to go with a full extension route, that’s possible too. But as of now, we don’t have confirmation.

One reason that could make things challenging for the team is getting external dApps to adopt Infinex Connect. This could be one reason why the team might consider going the extension route, to support a wider range of dApps without needing SDK integration.

This is my view on the Infinex Extension.

XXXXX engagements

Engagements Line Chart

Post Link

post/tweet::1947283363934752839
/post/tweet::1947283363934752839