Incorrect check for parent block hash in EVM datasets

[kalabukdima]

The check itself works but the output error looks like

unexpected base block: expected <provided hash>, but got 0#0x0000000000000000000000000000000000000000000000000000000000000000

It seems that query engine always uses "parent_number" column for this check, and it doesn't exist for EVM.

data/crates/query/src/plan/plan.rs

Line 107 in 4c089d8

let mut refs: Vec<_> = if block_scan.schema().column_with_name("parent_number").is_some() {

[eldargab]

Output looks correct.

Note, that at the moment we don't have a way to validate the hash of block 0. It's parent_hash is literally 0x000...0.

[kalabukdima]

Output looks correct.

Note, that at the moment we don't have a way to validate the hash of block 0. It's parent_hash is literally 0x000...0.

It may be correct for block 1, but it's exactly the same for any block, e.g.

{
  "fromBlock": 100,
  "parentBlockHash": "0xdb10afd3efa45327eb284c83cc925bd9bd7966aea53067c1eebe0724d124ec10",
  "type": "evm",
  "fields": {
    "block": {
      "number": true,
      "timestamp": true,
      "hash": true
    }
  },
  "includeAllBlocks": true
}