bug: custom rpc requests eip-1193 gets sent to the RPC provider instead of to the wallet with web3modal

[Sednaoui]

Is there an existing issue for this?

• I have searched the existing issues

Package Version

1.3.3

Current Behavior

Hello,

I am looking to send a custom rpc request to a smart contract wallet wallet connected through web3modal / walletconnect. I am using the hook useWalletClient .

The error happens then useWalletClient sends the custom requests the default rpc provider instead of to the wallet. So the request is being rejected with the following error, when connected with a wallet through walletconnect.

I have tried metamask mobile, rainbow mobile, and candide wallet.

Expected Behavior

The expected behavior is to send the custom request to the wallet directly. Using metamask browser injected provider, the request is sent to the wallet directly, and the error is correct as expected:

Steps To Reproduce

const customRequest = {
    method: "wallet_customRequest",
    params: [..]
}

useWalletClient() hook

import { useWalletClient } from 'wagmi"

const { data: walletClient } = useWalletClient();
..
await walletClient.request(customRequest);

Link to Minimal Reproducible Example (StackBlitz, CodeSandbox, GitHub repo etc.)

https://github.com/Sednaoui/wagmi-web3modal-custom-rpc-error

Anything else?

I am testing on optimism network.

No response

[tmm]

At the moment, the WalletConnect Connector does not support adding additional methods so only the ones defined in the init function are valid. Moving to feature request.

[joanseg]

Hi @tmm thanks for your feedback. Please, could you let us know what is the best way to reach Wagmi team in order to explain what we are trying to achieve, so you have all the information required to prioritize it?
Thanks for your help.

[tmm]

Feel free to drop some info on what you are looking to accomplish here. (FYI we only prioritize feature requests when they seem of general interest to the community.)

[Sednaoui]

Thanks @tmm for the clarification. We are personally trying to integrate EIP-5792 for batch transactions. TWith smart contract wallets now getting popular, dapp frontend can now communicate JSON-RPC method for sending multiple function calls from the user’s wallet. Dapps are able to offer one-click experience for multi-step interactions of bundled calls. The following methods are the ones we are using:

• wallet_sendFunctionCallBundle
• wallet_getBundleStatus
• wallet_showBundleStatus

I can't speak for the general community. But with this bug open, I believe no one can experiment with new ERCs for the ethereum provider API with wagmi library and web3modal.

[joanseg]

Adding to @Sednaoui .
A concrete example we want to achieve is to Approve, and confirm payment in the same call.
This way we achieve same experience as tradicional payment methods.
We will also add the call to the paymaster to sponsor transaction.
This will enable any Dapp that uses Wagmi and Web3modal (or Rainbowkit,...) To create experiences with less friction for the user, and enable mass adoption.
Please let us know if your team can review and prioritise and let us know, without any commitment, if will be done at all, short or long term.
We use extensively Wagmi and Viem now💪. And we want to avoid using ethers.js work arounds in our code😅.
Many thanks for your help and attention beforehand🙏.
Cheers.

[joanseg]

Dear @tmm, any update on this? We are willing to collaborate and support this request. If needed, we can help to develop or pay for it.
Thanks for your support in advance.