ethclient: support networkID in hex format

[kkqy]

Some chains’ network IDs use hexadecimal such as Optimism ("0xa" instead of "10"), so when converting the string to big.Int, we cannot specify base 10; otherwise, it will encounter errors with hexadecimal network IDs.

[lightclient]

I get 10 when querying Optimism's RPC:

$ curl -X POST https://mainnet.optimism.io -H 'Content-Type: application/json' -d '{"jsonrpc": "2.0", "id": 0, "method": "net_version", "params": []}'
{"jsonrpc":"2.0","result":"10","id":0}

[fjl]

I think we should support hex.

[fjl]

The problem is, there is no spec for this method. While Geth has been returning decimal, most other methods return numbers as hex.

[fjl]

There is an issue for adding a spec here (and the proposed spec uses hex...): ethereum/execution-apis#540

[kkqy]

I get 10 when querying Optimism's RPC:

$ curl -X POST https://mainnet.optimism.io -H 'Content-Type: application/json' -d '{"jsonrpc": "2.0", "id": 0, "method": "net_version", "params": []}'
{"jsonrpc":"2.0","result":"10","id":0}

Maybe it depends on the RPC server.
please try: https://optimism.llamarpc.com

curl -X POST https://optimism.llamarpc.com -H 'Content-Type: application/json' -d '{"jsonrpc": "2.0", "id": 0, "method": "net_version", "params": []}'
{"jsonrpc":"2.0","id":0,"result":"0xa"}

[karalabe]

SGTM

[holiman]

LGTM