bug: "specified block must exist on Ethereum" for wrong network

[jamesondh]

Do you want to request a feature or report a bug?

bug

What is the current behavior?

My subgraph is set to use aurora testnet. When I set the startBlock to 92549542 (which exists on aurora testnet) and deploy, I get the error subgraph validation error: [the specified block must exist on the Ethereum network]. When I set it to 15000000 (which exists on ethereum mainnet), it deploys fine. This leads me to believe this requirement is using the wrong network to determine the maximum possible startBlock.

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem.

clone https://github.com/fluxprotocol/fpo-evm-subgraph , set the startBlock in subgraph.yaml to 92549542, and deploy to the hosted service to get the error message.

What is the expected behavior?

The subgraph should deploy with the specified startBlock since the block exists on aurora testnet.

[jamesondh]

update: subgraph is stuck syncing at block 90956348 when the most recent block is >94M, this is the in the logs:

Ethereum endpoint is behind, url: b3c5663d1633.relayer.testnet.partners.aurora.dev, component: BlockStream

[JamesEarle]

@jamesondh Any additional updates or possible work arounds?

[ctindogaru]

any updates on this? I'm having the same issue

[ctindogaru]

also, does this happen with aurora network as well? or is it just the testnet?

[azf20]

Hi @ctindogaru this should be fixed now, are you seeing this issue on aurora mainnet

[ctindogarus4f]

is it fixed on testnet as well? Because I was having problems with testnet, not mainnet.

There are 2 problems here:

1. if the startBlock is after the last block mined in Ethereum you get: subgraph validation error: [the specified block must exist on the Ethereum network]. What does Aurora have to do with Ethereum?
2. You can overcome 1 if you pick a startBlock that is mined also on Ethereum (let's say 15500000). However, when the subgraph is syncing, it doesn't sync until the very last block of the Aurora Testnet. (it stops at 97 mil, although there are 101 mil blocks)

I'll try the deployment once again today and let you know how it went.

[ctindogarus4f]

I've just retried a full deployment on Aurora Testnet. All the subgraph bugs got fixed, it worked like a charm.

Thank you for taking care of it guys!

[kunalroute]

@ctindogarus4f I'm facing same issue on Aurora mainnet. Set startBlock in subgraph.yaml 75586003 and deploy. For many valid blocks it is giving error as invalid block on Ethereum network.

[ctindogarus4f]

for me, it started working on testnet...

For mainnet I didn't try yet, but it should work as well since there are fewer blocks on mainnet than they are on testnet.

[maihao1997]

for me, I changed the rpc and it can work.