After researching block speed scanning improvements, I stumbled upon the startBlock feature in the docs. This feature is a hidden gem that saves a significant amount of time during development as it skips unnecessary block scans.
The docs do mention: Note: The contract creation block can be quickly looked up on Etherscan: 1. Search for the contract by entering its address in the search bar. 2. Click on the creation transaction hash in the Contract Creator section. 3. Load the transaction details page where you'll find the start block for that contract. This can be automated and inserted directly into the yaml configuration during graph init time.
If automatic fetching turns out to be too complex, then the above note should at least be printed to the user during the init stage. Currently, thorough reading of the docs is required to discover it which may deter new users who have to wait hours for blocks to sync.
After researching block speed scanning improvements, I stumbled upon the startBlock feature in the docs. This feature is a hidden gem that saves a significant amount of time during development as it skips unnecessary block scans.
The docs do mention:
Note: The contract creation block can be quickly looked up on Etherscan: 1. Search for the contract by entering its address in the search bar. 2. Click on the creation transaction hash in the Contract Creator section. 3. Load the transaction details page where you'll find the start block for that contract.This can be automated and inserted directly into the yaml configuration during graph init time.If automatic fetching turns out to be too complex, then the above note should at least be printed to the user during the init stage. Currently, thorough reading of the docs is required to discover it which may deter new users who have to wait hours for blocks to sync.