Waiting on PR reviews - TorusWalletAdapter & Wagmi Web3Auth Connector bug fixes

PR links:

  1. torus-evm-adapter: missing provider in connect `emit` throws in `no-modal.ts` · Issue #1914 · Web3Auth/web3auth-web · GitHub

Summary: adapter does not emit the correct data when connected. provider is also necessary to be emitted but is currently omitted - no-modal.ts on connection with Web3AuthModal requires this but right now it fails as it is undefined:

  1. web3auth-wagmi-connector: Fixes #147 - error in `blockExplorers.default.url` type: `array` to `string` by W3stside · Pull Request #148 · Web3Auth/web3auth-wagmi-connector · GitHub

Summary: chain config logic is wrong and treats blockExplorerUrl.default.url as an array when it is a string

screenshot belows shows the string url being parsed as an array[0] index call and returns h - “https://blockexplorer-url.io”[0] = h

Reason:
These are blocking integration in wagmi/viem V2

Hey David (W3stside),

Thank you for reaching out!

I see you’re encountering issues with the TorusWalletAdapter and Wagmi Web3Auth Connector, and you’ve provided the respective PR links. Thanks for sharing those; it’s helpful for the team to reference directly.

Quick Summary:

Your provided information is quite detailed. The Web3Auth team will look into these PRs and address the blocking issues.

This response was generated by the Web3Auth Bot. A member of our team will review your query and get back to you shortly.

Thanks for your patience!

Hey @david.sato64

The Torus Wallet has been officially deprecated and hence the adapter is causing the issues. I’d request you to use our default evm adapters package rather, which will help you integrate all wallets possible: Default EVM Adapter | Documentation | Web3Auth

Hi @yashovardhan thanks for the reply.

The package in question is a dependency of the default adapter see:

I understand your point. We’ll be soon deprecating the torus-evm-adapter package as well. For wagmi integrations, we do not recommend using external wallets since wagmi connectors can easily handle that for you. You can use all social login methods from web3auth for that.

OK thanks. Maybe write that somewhere in the documentation if its not there as it’s a little confusing.

Nonetheless, thanks a lot for raising the PRs, I’ll test and accordingly ask the engineering team for a merge. The contribution like yours help the community a lot :heart:

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.