-
Notifications
You must be signed in to change notification settings - Fork 447
HELP - Failed to fetch multicall chunk #14
Comments
Hi Timothy, you're more likely to get a helpful response from the Uniswap team. This doesn't appear to be an issue with multicall itself. Wishing you luck! |
Hello Timothy, |
Hi @DevObs1 Things to check would be params like your chainId i.e. it seems that the front end gets params like chainId from external files like this
If you are using an Ethereum compatible network which is not one of the networks listed in the Sorry I can't be more helpful, hope this makes sense. Kind regards |
Hello @tpmccallum , |
Hey @tpmccallum, I am forking the uniswap interface for a new testnet, and am also having this same issue. I have tried changing constants in the node modules like you suggest. Please update here if you fund a solution, I will do the same if I find a solution on my side. Ben |
it is relatively straightforward to solve this issue. we were able to resolve this issue in CoinSwap. Check the returned error parameters etc. For the same smart contract, different compiler (remix/waffle/truffle) all compile in a different way. It is a disaster that the system is not compatible. So the way it is working on uniswap does not mean it will work on your contract if you use a different platform to compile your contract and deploy them (of course, could be challenging to get verified on Etherscan) |
@coinswapapp what platform did you use to compile the contracts? |
do not use truffle or remix. the compiled contract by truffle/remix may not work correctly even if you try to call these methods manually on Etherscan. try wallfe |
After using waffle to compile all the contracts, I dont have an error concerning Multicall anymore but still do have the error with Metamask:
|
then it will really depend on what kind of contract you are using or testing. E.g., are you using the exact copy of Uniswap contract or you have modified it.. but at least, it shows that you are on the right track. |
@Ben-Haslam Hi,Ben.Have u fix this issue now?I stuck on it too. |
Unfortunately I never did. Instead I just started building my own interface from the ground up |
The problem here from my experience is that multicall smart contract you are using is not the exact match for Binance smart chain. You need to deploy the exact copy of Uniswap multicall contract to Smartchain mainnet or testnet for it to work appropriately. |
Thanks a lot! you saved my day 🚀 |
Release job for ABIs
Hi, |
Thanks a lot. I redeployed the multicall contract and change the multicall contract address in my project and now it's working! |
this is the address of the multicall that the uniswap team uses to call |
Thanks for your response.
Good day and take care.
kelvin0x ***@***.***>于2022年11月16日 周三17:39写道:
… this is the address of the multicall that the uniswap team uses to call
0x1F98415757620B543A52E61c46B32eB19261F984
—
Reply to this email directly, view it on GitHub
<#14 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AXFWBJ25YEVPDRHHFDSTBUTWISTVRANCNFSM4RVLS5OQ>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Hi,
I have written an installer that allows Uniswap to be deployed on any Ethereum compatible blockchain.
It works great except for one error line 190 in Uniswap's multicall/updater file
I would love some assistance with this, I am unsure why it does not work. As you will see in my installer I have diligently deployed all of the contracts and have provided significant config.
Any information/assistance would be greatly appreciated.
Many thanks
Tim
The text was updated successfully, but these errors were encountered: