-
Notifications
You must be signed in to change notification settings - Fork 95
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
deployed uniswap issue with metamask conneted #4
Comments
I have tried this and have this same issue. Viewing the in browser console, I can see that when the connection is lost there is the error @tpmccallum I've seen that you have also had this error with this issue makerdao/multicall#14 (comment) I got the error using this repo but also when I forked the uniswap interface myself manually. Does anyone know what causes this error and how it could be fixed? |
Hi, ben did you solve the error ? |
Alas I did not, because of this issue and because I wanted to have a code base I understood from the ground up, I decided to make my own interface from scratch, which works pretty well for the network I was using (Autonity Bakerloo testnet). Code for that is here, hope it helps. |
Awesome, @Ben-Haslam |
Hey @tpmccallum, its 444900. Have a go! |
@Ben-Haslam Can you make me a simple tutorial on installing and modifying the files needed to work on the matic network? |
Hey there. At the moment the smart contract addresses are hard coded for the Autonity network, but soon I will change how it works by adding a network dictionary, so when the network id is found it will choose the right addresses from there. That will be very easy to modify to add a new network |
same issue on here. |
After initial metamask connection, balance is displayed on dApp, but after maybe 15-20 second all balances displayed in dApp ho to zero and stay like that stopping me to do any activity inside dApp
Just connected...
After 15 seconds...
The text was updated successfully, but these errors were encountered: