WalletConnectProvider not working with Web3.js
See original GitHub issueI was following the code written in here https://docs.walletconnect.org/quick-start/dapps/web3-provider But it seems that the Web3 class cannot be initialized with the WalletConnectProvider class or any of its properties from what I can see.
Argument of type 'WalletConnectProvider' is not assignable to parameter of type 'provider'.
Type 'WalletConnectProvider' is not assignable to type 'string'
I’m using web3 ^1.2.11
and @walletconnect/web3-provider ^1.2.1
on TypeScript.
Is the doc outdated or is there something that I am missing?
Issue Analytics
- State:
- Created 3 years ago
- Comments:7 (1 by maintainers)
Top Results From Across the Web
e is not a constructor - WalletConnectProvider model not ...
i have fixed the problem, by adding const WalletConnectProvider = window.WalletConnectProvider.default; inside constructor().
Read more >Web3 with WalletConnectProvider is not responding when ...
I am using angular with walletconnectprovider and web3 I have this issue with calling any methods from the contract where web3 is not...
Read more >@walletconnect/web3-provider - npm
Start using @walletconnect/web3-provider in your project by running `npm i ... import Web3 from "web3"; import WalletConnectProvider from ...
Read more >Connecting to web3 with Web3Modal, react & ethers.js
I'm writing this article solely with hope that one day it ends up high in web searches for this specific problem & it...
Read more >Web3Modal Demo - CodePen Embed
Web3Modal.default; const WalletConnectProvider = window. ... is a BigNumber instance // https://github.com/indutny/bn.js/ const ethBalance = web3.utils.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I have the same issue with the following versions:
I found the following workaround might be helpful to someone having the issue in the future:
Hope this help.
@hoonsubin, @crypto-yang, @limcheekin are either on of you still experiencing this issue?