Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to integrate web3 with drizzle #164

Closed
raashidjunaid1 opened this issue Jun 4, 2020 · 7 comments
Closed

Unable to integrate web3 with drizzle #164

raashidjunaid1 opened this issue Jun 4, 2020 · 7 comments

Comments

@raashidjunaid1
Copy link

raashidjunaid1 commented Jun 4, 2020

Hi there, I am trying to use web3modal pointing to local blockchain (truffle develop).

Steps to recreate:

Would be very grateful if anyone could help!

@pedrouid
Copy link
Contributor

pedrouid commented Jun 4, 2020

Is drizzle a frontend framework?

@raashidjunaid1
Copy link
Author

@pedrouid
Copy link
Contributor

pedrouid commented Jun 4, 2020

@miohtama Could you help on this issue? I'm not too familiar with all Truffle tools

@raashidjunaid1
Copy link
Author

apologies, its not a framework but just a library on top of react. Which pretty much auto syncs block data to your app

@rraghees
Copy link

@raashidjunaid1 I have run to similar problem did you find anything ?

@kombos
Copy link

kombos commented Jul 13, 2020

may i know what is the custom provider object that you are passing to the web3 section of the 'drizzle options'? Try this:

  1. do NOT forward this provider object of web3modal:
    const provider = await web3Modal.connect();
  2. instead forward the provider object of web3 after creating a web3 object from web3modal:
const web3ModalProvider = await web3Modal.connect();
const web3 = new Web3(web3ModalProvider);
const provider = web3.currentProvider();

now forward this provider object as the custom provider. not sure if it will work but do try and post the results? tx.

@xzilja
Copy link
Contributor

xzilja commented Jan 21, 2023

With stable version 2.0.0 of Web3Modal now released, we are officially dropping support for version 1.x
Due to this this issue/pr was marked for closing. It is highly recommended to upgrade as 2.x will be receiving further updates that will enable functionality for some of our newer sdks like auth and push as well as support for WalletConnect v2 (See this post about WalletConnect v1 being deprecated https://medium.com/walletconnect/walletconnect-v1-0-sunset-notice-and-migration-schedule-8af9d3720d2e)

If you need to continue using Web3Modal 1.x and require this feature/fix implemented, we suggest adding it via forking V1 branch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants