Questions about Web3 API

Technical Issue Reporting
#1

Hi, we’re looking to give Moralis money and are wondering about the following:

  • Is there a way to find out what block the Web3 API for historical data index is synced up to? Similar to what covalent offers: https://www.covalenthq.com/docs/api/#/0/Class-A/Get-block-heights/lng=en

    I know I can specify to_block on some endpoints and if no data is returned then I know the historical data index hasn’t caught up yet, but this isn’t a great way for me to determine the sync status of the historical data index.

  • Is there planned support for Arbitrum / Optimism for this historical data index?

  • When a new token is deployed onto the block chain, a user is given these tokens, how long would I expect for Moralis to return this as a part of their ERC20 balance from the Web3 API endpoint?

Thanks

#2

we are working on making faster the processing of new minted NFT tokens
for a new NFT token it could be few minutes today, I didn’t test recently for ERC20, but we are planning on making it faster in general.

#3

If the turnaround is a few minutes for ERC20s as well, that’s pretty good for our current use case.

Any chance you can answer the other questions I had? Thanks!

  • Is there a way to find out what block the Web3 API for historical data index is synced up to? Similar to what covalent offers: https://www.covalenthq.com/docs/api/#/0/Class-A/Get-block-heights/lng=enI know I can specify to_block on some endpoints and if no data is returned then I know the historical data index hasn’t caught up yet, but this isn’t a great way for me to determine the sync status of the historical data index.

  • Is there planned support for Arbitrum / Optimism for this historical data index?

#4

For the first question I don’t know of an endpoint to return that last block that was processed, usually we process new blocks fast, but in some cases we use a delay so that the result is not affected by a reorg

I don’t know the answer now for the other question