Steps to reproduce:

Defineevm_node datasource:

datasources:
  evm_node:
    kind: evm.node
    url: ${RPC_URL}

Use w3 inside handler:

w3 = ctx.get_evm_node_datasource("evm_node").web3

Interact with w3.

What did you expect to happen:

Request doesn't return error.

What actually happened:

Request return error:

web3.exceptions.BadResponseFormat: The response was in an unexpected format and unable to be parsed. "id" must be an integer or a string representation of an integer. The raw response is: {'jsonrpc': '2.0', 'id': 'fb9bef5f7a5d40029924a3e72f65fa26', 'result': '0x1'}

I'm not sure if this issue affects only on newer versions of web3. I've tested with another RPC provider using web3==7.2.0, but the issue persists.

Environment

• Python version: 3.12
• DipDup version or commit hash: 8.1.3
• Database engine version: n/a
• Hasura version: n/a
• Are you in docker? no
• Can you reproduce this issue on next? n/a