{
  "context": "Evaluates how well the Block Lookup Reporter leverages web3-eth for block and transaction lookups. Focuses on correct client setup, block retrieval with/without hydration, and transaction plus receipt queries needed to satisfy the spec behaviors.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Client setup",
      "description": "Constructs or accepts a `Web3Eth` instance from `web3-eth` (with provider URL or injected client) and reuses it for all queries instead of issuing raw RPC requests.",
      "max_score": 15
    },
    {
      "name": "Block fetch",
      "description": "Retrieves blocks via `getBlock`, using the `hydrated` flag to return hashes by default and full transaction objects when `includeTransactions` is true; handles block refs like numbers, hashes, and tags.",
      "max_score": 25
    },
    {
      "name": "Count accuracy",
      "description": "Derives transaction counts through `getBlockTransactionCount` for hash-only views or via the `transactions.length` from `getBlock(..., true)` rather than manual tallying, keeping counts aligned with block data.",
      "max_score": 15
    },
    {
      "name": "Tx by hash",
      "description": "Uses `getTransaction` to fetch details and pairs it with `getTransactionReceipt` to report block number and success status; returns null when `getTransaction` yields no result.",
      "max_score": 25
    },
    {
      "name": "Tx by index",
      "description": "Looks up transactions by block + index through `getTransactionFromBlock` (or hydrated `getBlock` fallback) and confirms status via `getTransactionReceipt`, keeping the hash aligned with the hydrated block entry.",
      "max_score": 20
    }
  ]
}