bug: zksync system logs crash the sync engine

[typedarray]

ZKSync Era has logs that don't have a corresponding transaction. This currently fails one of our validations and crashes the sync engine.

Potential solution

The Graph Node solution was to relax the validation with a special case that allows logs that have a missing transaction as long as log.transactionHash is 0x00....

If we followed the same approach, we would technically need to make the entire event.log.transaction object nullable, which would suck. I think a decent short-term solution is to allow the type to be incorrect for now, and at some point we'll add chain-specific configuration/types to handle situations like this.

Repro

Error

Error: Detected inconsistent RPC responses. 'log.transactionHash' 0x0000000000000000000000000000000000000000000000000000000000000000 not found in 'block.transactions' 0x8f1b3e111f462cfb17e887ab67db92311d2d887cd8e6ca11c5bb85f2847c274f

eth_getLogs returns one log

curl -X POST https://sepolia.era.zksync.dev \
-H "Content-Type: application/json" \
-d '{
  "jsonrpc": "2.0",
  "method": "eth_getLogs",
  "params": [{
    "blockHash": "0x8f1b3e111f462cfb17e887ab67db92311d2d887cd8e6ca11c5bb85f2847c274f"
  }],
  "id": 1
}'

eth_getBlockByHash returns zero transactions

curl -X POST https://sepolia.era.zksync.dev \
-H "Content-Type: application/json" \
-d '{
  "jsonrpc": "2.0",
  "method": "eth_getBlockByHash",
  "params": [
    "0x8f1b3e111f462cfb17e887ab67db92311d2d887cd8e6ca11c5bb85f2847c274f",
    true
  ],
  "id": 1
}'