September 4, 2026
gm, builders! Here’s your roundup of this week’s insights.
Highlights
-
Improved WalletConnect Support
-
EIP-1193 Fallback for Wagmi Mode
-
Reading List
Improved WalletConnect Support
The Web SDK (1.38.2) can now track wallets your app constructs in code, not just the ones a browser injects from EIP-1193.
Wallet discovery covers wallets that announce themselves and wallets that sit at window.ethereum , which is every injected browser wallet and nothing else. A provider your app builds in code, such as WalletConnect, announces nothing.
Hand the provider over with registerProvider and it takes the same path a discovered wallet does: connect and disconnect lifecycle events, and signature and transaction autocapture.
formo.registerProvider(provider);
Using Wagmi mode ? This is automatically handled for you and you don’t need to make any changes.
See the WalletConnect integration guide to get started.
EIP-1193 Fallback for Wagmi Mode
Wagmi mode captures signature and transaction events from Wagmi hooks. However, if your app also sends imperatively through viem, with sendTransaction , .signMessage , or .writeContract , those calls create no Wagmi mutation and were never captured.
Opt in with eip1193Fallback and the SDK instruments the active connector’s provider with the same request wrapper the EIP-1193 mode uses:
wagmi: { eip1193Fallback: true }
Upgrade to the latest SDK to get started.