[Bug] Stopped indexing at the block number 6404191, 6404192 in Bittensor EVM network.

Bug report

I deployed the uniswap v3 subgraph for the Bittensor EVM network (chain id 964) and until now it is working well.
But yesterday, I noticed that it is stopped at the block number 6404191.
I tried too many times re-syncing but every time it was stopped at the block number 6404191.
Only 6404191 and 6404192 has this problem.
From 6404193, Syncing is working well.

This is the logs of graph node.

Relevant log output

INFO Syncing 0 blocks from Ethereum, code: BlockIngestionStatus, blocks_needed: 0, blocks_behind: 1, latest_block_head: 6416281, current_block_head: 6416280, provider: subtensor-rpc-0, component: EthereumPollingBlockIngestor
INFO Syncing 0 blocks from Ethereum, code: BlockIngestionStatus, blocks_needed: 0, blocks_behind: 1, latest_block_head: 6416282, current_block_head: 6416281, provider: subtensor-rpc-0, component: EthereumPollingBlockIngestor
INFO Syncing 0 blocks from Ethereum, code: BlockIngestionStatus, blocks_needed: 0, blocks_behind: 1, latest_block_head: 6416283, current_block_head: 6416282, provider: subtensor-rpc-0, component: EthereumPollingBlockIngestor
WARN Trying again after load block 0x716b…6b99 failed (attempt #10) with result Err(Decoder error: Error("missing field `storageKeys`", line: 0, column: 0)), sgd: 7, subgraph_id: Qme6NH6mTFMmTyKvSwHkXejrQzwHnLz637MoA5sSxHRmCE, component: BlockStream
INFO Syncing 0 blocks from Ethereum, code: BlockIngestionStatus, blocks_needed: 0, blocks_behind: 1, latest_block_head: 6416284, current_block_head: 6416283, provider: subtensor-rpc-0, component: EthereumPollingBlockIngestor
INFO Syncing 0 blocks from Ethereum, code: BlockIngestionStatus, blocks_needed: 0, blocks_behind: 1, latest_block_head: 6416285, current_block_head: 6416284, provider: subtensor-rpc-0, component: EthereumPollingBlockIngestor
INFO Syncing 0 blocks from Ethereum, code: BlockIngestionStatus, blocks_needed: 0, blocks_behind: 1, latest_block_head: 6416286, current_block_head: 6416285, provider: subtensor-rpc-0, component: EthereumPollingBlockIngestor
INFO Syncing 0 blocks from Ethereum, code: BlockIngestionStatus, blocks_needed: 0, blocks_behind: 1, latest_block_head: 6416287, current_block_head: 6416286, provider: subtensor-rpc-0, component: EthereumPollingBlockIngestor
INFO Syncing 0 blocks from Ethereum, code: BlockIngestionStatus, blocks_needed: 0, blocks_behind: 1, latest_block_head: 6416288, current_block_head: 6416287, provider: subtensor-rpc-0, component: EthereumPollingBlockIngestor
INFO Syncing 0 blocks from Ethereum, code: BlockIngestionStatus, blocks_needed: 0, blocks_behind: 1, latest_block_head: 6416289, current_block_head: 6416288, provider: subtensor-rpc-0, component: EthereumPollingBlockIngestor
INFO Syncing 0 blocks from Ethereum, code: BlockIngestionStatus, blocks_needed: 0, blocks_behind: 1, latest_block_head: 6416290, current_block_head: 6416289, provider: subtensor-rpc-0, component: EthereumPollingBlockIngestor
INFO Syncing 0 blocks from Ethereum, code: BlockIngestionStatus, blocks_needed: 0, blocks_behind: 1, latest_block_head: 6416291, current_block_head: 6416290, provider: subtensor-rpc-0, component: EthereumPollingBlockIngestor
INFO Syncing 0 blocks from Ethereum, code: BlockIngestionStatus, blocks_needed: 0, blocks_behind: 1, latest_block_head: 6416292, current_block_head: 6416291, provider: subtensor-rpc-0, component: EthereumPollingBlockIngestor
INFO Syncing 0 blocks from Ethereum, code: BlockIngestionStatus, blocks_needed: 0, blocks_behind: 1, latest_block_head: 6416293, current_block_head: 6416292, provider: subtensor-rpc-0, component: EthereumPollingBlockIngestor
INFO Scanning blocks [6404191, 6404191], target_range_size: 1, sgd: 7, subgraph_id: Qme6NH6mTFMmTyKvSwHkXejrQzwHnLz637MoA5sSxHRmCE, component: BlockStream
INFO Syncing 0 blocks from Ethereum, code: BlockIngestionStatus, blocks_needed: 0, blocks_behind: 1, latest_block_head: 6416294, current_block_head: 6416293, provider: subtensor-rpc-0, component: EthereumPollingBlockIngestor
INFO Syncing 0 blocks from Ethereum, code: BlockIngestionStatus, blocks_needed: 0, blocks_behind: 1, latest_block_head: 6416295, current_block_head: 6416294, provider: subtensor-rpc-0, component: EthereumPollingBlockIngestor
INFO Syncing 0 blocks from Ethereum, code: BlockIngestionStatus, blocks_needed: 0, blocks_behind: 1, latest_block_head: 6416296, current_block_head: 6416295, provider: subtensor-rpc-0, component: EthereumPollingBlockIngestor
INFO Syncing 0 blocks from Ethereum, code: BlockIngestionStatus, blocks_needed: 0, blocks_behind: 1, latest_block_head: 6416297, current_block_head: 6416296, provider: subtensor-rpc-0, component: EthereumPollingBlockIngestor
INFO Syncing 0 blocks from Ethereum, code: BlockIngestionStatus, blocks_needed: 0, blocks_behind: 1, latest_block_head: 6416298, current_block_head: 6416297, provider: subtensor-rpc-0, component: EthereumPollingBlockIngestor
WARN Trying again after load block 0x716b…6b99 failed (attempt #10) with result Err(Decoder error: Error("missing field `storageKeys`", line: 0, column: 0)), sgd: 7, subgraph_id: Qme6NH6mTFMmTyKvSwHkXejrQzwHnLz637MoA5sSxHRmCE, component: BlockStream
INFO Syncing 0 blocks from Ethereum, code: BlockIngestionStatus, blocks_needed: 0, blocks_behind: 1, latest_block_head: 6416299, current_block_head: 6416298, provider: subtensor-rpc-0, component: EthereumPollingBlockIngestor

IPFS hash

Qme6NH6mTFMmTyKvSwHkXejrQzwHnLz637MoA5sSxHRmCE

Subgraph name or link to explorer

http://34.10.242.87/subgraphs/id/Qme6NH6mTFMmTyKvSwHkXejrQzwHnLz637MoA5sSxHRmCE

Some information to help us out

• Tick this box if this bug is caused by a regression found in the latest release.
• Tick this box if this bug is specific to the hosted service.
• I have searched the issue tracker to make sure this issue is not a duplicate.

OS information

None

Start with the graph-node BlockStream path for loading blocks 6404191 and 6404192, using the reported decoder error for missing storageKeys and the EthereumPollingBlockIngestor logs as the reproduction context. Check the provider response for the failing block and verify that syncing advances past it without repeated decoder failures.