feat: switch from http to ws connection (eth execution client)

[Vid201]

Some other things in this PR:

• switch from anyhow to eyre
• update bundler spec tests to latest commit
• update geth version from to v1.12.0

[zsluedem]

What if the websocket connection is lost because of network issue? Do you have plans to address that?Does ethers ws handle that internally?

The problem with websocket is that we need to provide a way when the connection is lost. If we don't have that, when the situation happens, the bundler would just crash and got no more data from websocket. As for normal http request, if one of the http request is lost, it would just got one task crash(maybe this task would crash the whole bundler. It is possible. But http leave codes easier to write)

[zsluedem]

I am curious whether env variable http_proxy and https_proxy are applied to the lib we used. Do you know that.

[Vid201]

Hmm, I am not sure what you mean by that

[Vid201]

What if the websocket connection is lost because of network issue? Do you have plans to address that?Does ethers ws handle that internally?

The problem with websocket is that we need to provide a way when the connection is lost. If we don't have that, when the situation happens, the bundler would just crash and got no more data from websocket. As for normal http request, if one of the http request is lost, it would just got one task crash(maybe this task would crash the whole bundler. It is possible. But http leave codes easier to write)

Yes, that is the problem that still needs to be addressed in this PR. At the moment, if the connection is dropped, the bundler doesn't crash (same as HTTP). But if the eth client is up again, the connection is not reestablished. I am planning to make a wrapper around eth_client, that offers a way to do healthcheck and connect if connection is not live. Then the bundler pings eth_client every x seconds. What do you think?

I think websockets will be useful when we subscribe to blocks to check which user operations are included onchain.

[Vid201]

What if the websocket connection is lost because of network issue? Do you have plans to address that?Does ethers ws handle that internally?
The problem with websocket is that we need to provide a way when the connection is lost. If we don't have that, when the situation happens, the bundler would just crash and got no more data from websocket. As for normal http request, if one of the http request is lost, it would just got one task crash(maybe this task would crash the whole bundler. It is possible. But http leave codes easier to write)

Yes, that is the problem that still needs to be addressed in this PR. At the moment, if the connection is dropped, the bundler doesn't crash (same as HTTP). But if the eth client is up again, the connection is not reestablished. I am planning to make a wrapper around eth_client, that offers a way to do healthcheck and connect if connection is not live. Then the bundler pings eth_client every x seconds. What do you think?

I think websockets will be useful when we subscribe to blocks to check which user operations are included onchain.

@zsluedem I fixed the reconnection problems (https://github.com/Vid201/silius/blob/feat/ws/Cargo.toml#L43). This is now handled in ethers-rs internally (gakonst/ethers-rs@d9c2baf). When the connection is lost, it tries to reconnect every 2 seconds. When the node becomes online again, it works normally onwards. The behavior is similar now to lost http requests.

[zsluedem]

Awesome!~!!