u/diornov

I’ve been building dApps for the past 5 years, and if there’s one constant, it’s connector headaches. Stale connections, stuck states, signature requests failing for no obvious reason - we've all been there.

Recently, while building out my ERC-4337 account abstraction interface, these connector issues reached a breaking point. I was heavily relying on Wagmi, but the connectors just weren't reliable enough for the complex flows I was building.

After a lot of debugging, I made a major architectural pivot: I decided to use Wagmi only for injected browser wallets. For WalletConnect, I completely bypassed the Wagmi wrapper and integrated their direct SDK. I did the exact same thing for Privy.

The result? All those weird connector bugs practically vanished overnight.

If anyone here is exclusively relying on Wagmi and pulling their hair out over connector instability, my advice is to strip it back. Try using the direct WalletConnect SDK instead - it gave me significantly more control and stability.

What I'm building (if you're interested in AA):

The project that forced me down this rabbit hole is called NYKNYC (nyknyc.app). It’s an exploration into what the future of wallets should look like using abstract accounts.

Instead of juggling the same seed phrase across multiple devices, NYKNYC lets you deploy a single smart contract wallet and attach multiple independent signers to it. For example, your setup could look like this:

• Signer 1: Your PC browser
• Signer 2: Your mobile phone
• Signer 3: Privy
• Backup Signer: A securely stored mnemonic

Would love to hear if anyone else has moved away from Wagmi wrappers for WC, or if you have any thoughts on multi-signer AA architectures!