Open beemeeupnow opened 11 months ago
This could also be related to the various metadata lookups made through alchemy during initial account load
Yep, first error is due to the querystring carrying the token addresses, with the path + querystring being typically limited to 64K max on most servers.
The second error is likely due to a multicall that exceeds EVM data or gas limits for return data.
In both cases we'll want to set a batch size for assets past which we run multiple batches instead of trying to do all tokens in one request.
Discord Discussion Link
No response
What browsers are you seeing the problem on?
Chrome
What were you trying to do?
Wallet becomes sluggish and unusable when adding a few read-only addresses that have a large variety of ERC-20 tokens. (easy to find some at https://etherscan.io/accounts)
I suspect some of this may be helped by #3466, but am opening this due to a secondary issue that appears in that scenario.
What did not work?
Errors appear in console that indicate price fetches are failing.
Based on the logs, it seems we may need to adapt these API requests when there are a large number of tracked assets.
A couple of items that appeared:
414 Request-URI Too Large
for getTokenPricesError: missing revert data in call exception
for getTrackedAssetsPricesMore output attached, v0.44.0
Version
None
Relevant log output