{
  "context": "Evaluates how the solution uses web3-eth to build a reusable provider context, apply default block/return formatting, and drive both instance methods and standalone RPC wrappers without reimplementing Ethereum HTTP calls. Checks that defaults and helper bindings stay attached to the same Web3Context instead of custom RPC plumbing.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Web3Eth URL init",
      "description": "Initializes the client from an endpoint string using `new Web3Eth(<rpc-url>, options?)` (or equivalent Web3Context constructor) instead of custom fetch logic, so RPC calls run through the library.",
      "max_score": 20
    },
    {
      "name": "Provider object init",
      "description": "Accepts a provider object (with `request`/`send`) passed directly into `Web3Eth`/`setProvider` to build the context, avoiding manual wiring when defaults target pending data.",
      "max_score": 20
    },
    {
      "name": "Default configs",
      "description": "Configures `defaultBlock` and `defaultReturnFormat` (or `returnFormat`) via Web3Eth/Web3Context options or `setConfig`, and relies on those defaults rather than post-processing to shape outputs.",
      "max_score": 25
    },
    {
      "name": "Instance RPC usage",
      "description": "Implements balance/height/identity lookups through `eth.getBlockNumber`, `eth.getBalance`, `eth.getChainId`, and `eth.getCoinbase` on the configured Web3Eth instance instead of reimplementing RPC calls.",
      "max_score": 15
    },
    {
      "name": "Shared wrappers",
      "description": "Uses the tree-shakeable RPC wrappers exported by `web3-eth` (e.g., `getBlockNumber`, `getChainId`) bound to the same `web3Context` so helper calls hit the same provider and defaults as the instance.",
      "max_score": 20
    }
  ]
}