UnhandledPromiseRejectionWarning: Error: Returned error: out of gas about ethereum-multicall HOT 14 CLOSED

I was under the impression the code should not fail with tryAggregate: true?

from ethereum-multicall.

Are you trying to call a state changing method here?

from ethereum-multicall.

Are you trying to call a state changing method here?

Thanks for fast response! I am calling standard "tokenByIndex" which exists in ERC20 contracts as read method:

https://etherscan.io/address/0x160c404b2b49cbc3240055ceaee026df1e8497a0#readContract

from ethereum-multicall.

Ok first web3 user here normally ethers users haha

let me try to run this code tomorrow and come back to you.. you are just using a infura or alchemy normal node right? I’m guessing the interface it tried to execute using web3 is a bit off as that error tends to be trying to call a method which is state changing logic (hence out of gas shizzle) but web3 generic error messaging may be this! Will look at fix it tomorrow time thanks for raising

from ethereum-multicall.

Can you confirm which web3 version you are using as well please?

from ethereum-multicall.

Can you confirm which web3 version you are using as well please?

Thanks! its this

"web3": "^1.7.1"

from ethereum-multicall.

you are just using a infura or alchemy normal node right?

Yes correct!

from ethereum-multicall.

Can you try to delete web3Instance for me and pass in nodeUrl instead? (Not on computer but if that works it be down to the web3 version I reckon and could make you carry on without this blocking you).

const multicall = new Multicall({ nodeUrl: INSERT_HERE, tryAggregate: true});

Let me know the outcome

from ethereum-multicall.

Sure outcome didn't all fit in terminal, but:

0000……………..\"},\"latest\"],\"id\":45,\"jsonrpc\":\"2.0\"}","requestMethod":"POST","url":"-----EDITED TO REMOVE URL TO ETHEREUM NODE -----"}, code=CALL_EXCEPTION, version=providers/5.6.6) at Logger.makeError (/Users/eliamorling/Documents/workspace/eth-crawler/node_modules/@ethersproject/logger/lib/index.js:233:21) at Logger.throwError (/Users/eliamorling/Documents/workspace/eth-crawler/node_modules/@ethersproject/logger/lib/index.js:242:20) at checkError (/Users/eliamorling/Documents/workspace/eth-crawler/node_modules/@ethersproject/providers/lib/json-rpc-provider.js:108:16) at JsonRpcProvider.<anonymous> (/Users/eliamorling/Documents/workspace/eth-crawler/node_modules/@ethersproject/providers/lib/json-rpc-provider.js:703:47) at step (/Users/eliamorling/Documents/workspace/eth-crawler/node_modules/@ethersproject/providers/lib/json-rpc-provider.js:48:23) at Object.throw (/Users/eliamorling/Documents/workspace/eth-crawler/node_modules/@ethersproject/providers/lib/json-rpc-provider.js:29:53) at rejected (/Users/eliamorling/Documents/workspace/eth-crawler/node_modules/@ethersproject/providers/lib/json-rpc-provider.js:21:65) at processTicksAndRejections (internal/process/task_queues.js:93:5) (Use node --trace-warnings ...to show where the warning was created) (node:79911) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag--unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1) (node:79911) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

from ethereum-multicall.

Wow hahaha!

And your using the ABI supplied in the etherscan link you sent right?

Also looking at your code I think I may know your issue here, even reads have an max allowance you can fetch from a node, it looks like your passing an insane amount of requests here..

Could you revert back to your code and then maybe do a request with say 5 tokenIds for now and see if it works?

const tokenIDs = [1,2,3,4,5]

Just want to make sure your not requesting a bit too much information

from ethereum-multicall.

Wow hahaha!

And your using the ABI supplied in the etherscan link you sent right?

Also looking at your code I think I may know your issue here, even reads have - max allowance you get fetch from a node, it looks like your passing an insane amount of requests here..

Could you revert back to your code and then maybe do a request with say 5 tokenIds for now and see if it works?

const tokenIDs = [1,2,3,4,5]

Just want to make sure your not requesting a bit too much information

This is the ABI I am using, it's the same as in the etherscan:

const abi = [{'inputs':[{'internalType':'uint256','name':'index','type':'uint256'}],'name':'tokenByIndex','outputs':[{'internalType':'uint256','name':'','type':'uint256'}],'stateMutability':'view','type':'function'}];

Sure it works with just the 5 tokens. But here I can fetch 12K without any problem?

require('dotenv').config();
const { Multicall } = require('ethereum-multicall');
const Web3 = require('web3');

const abi = [{'inputs':[{'internalType':'uint256','name':'index','type':'uint256'}],'name':'tokenByIndex','outputs':[{'internalType':'uint256','name':'','type':'uint256'}],'stateMutability':'view','type':'function'}];

const options = {
  timeout: 10000, // ms
  reconnect: { auto: true, delay: 1000,  maxAttempts: 5, onTimeout: false }
};
const provider = new Web3.providers.HttpProvider(process.env.QUICKNODE_HTTP_URL);
const web3 = new Web3(provider, options);
const multicall = new Multicall({ web3Instance: web3, tryAggregate: true});

async function main() {
  const tokenIDs = Array.from({length: 12000}, (_, i) => i );
  const calls = tokenIDs.map((token_id) => { return { methodName: 'tokenByIndex', methodParameters: [token_id] }; });
  const contractCallContext = [{ reference: 'contract', contractAddress: '0x34d85c9cdeb23fa97cb08333b511ac86e1c4e258', abi, calls}];
  const results = await multicall.call(contractCallContext);
  const extract = results.results.contract.callsReturnContext.map((r) => r.success ? web3.utils.hexToNumber(r.returnValues[0].hex) : null);
  console.log(extract);
}

main();

from ethereum-multicall.

Your problem is down to max response sizes from the node.. it all depend! If I was you I would fine a safe amount which the node likes that could be 1000,2000 and then do many promise.all on a multicall.call instance which means you still get your results back just as fast but won’t be limited by the nodes thinking response is too big! Does that make sense?

This is not down to a coding issue here it’s limitations of the read nodes sizes!

from ethereum-multicall.

I see... but I thought tryAggregate would make it possible to get results without the whole thing crashing?

from ethereum-multicall.

Well the entire thing is throwing so everything would blow up.. it’s actually better it does this here then gives you false for all because it has not executed any of the contract calls.. out of gas === too large I can try to make it a better message but it’s defo better to throw here then give a false positive back to users that everything failed (aka it will look like it executed it on chain).

Solution reduce sizes of requests and bulk call maybe il add a method called bulk call?! Or maybe il try to handle this internally and split the array up.. but for now reduce your size and call .call with promise.all and you get your result. Thanks for raising defo a feature to add here of maybe handling this for you in the lib 👍

from ethereum-multicall.