Implement debug_traceChain

[yaziciahmet]

Description

Implements debug_traceChain subscription rpc.

Linked Issues

• Fixes Implement trace_filter #704

[codecov]

Codecov Report

Attention: Patch coverage is 73.65269% with 44 lines in your changes missing coverage. Please review.

Project coverage is 79.1%. Comparing base (d69cfa2) to head (67aec5e).

Additional details and impacted files

Files	Coverage Δ
crates/ethereum-rpc/src/lib.rs	81.7% <73.6%> (+1.1%)	⬆️

... and 1 file with indirect coverage changes

[eyusufatik]

single nit. merge after fix. also, have you tested this query with something like ethers.js?

[rakanalh]

LGTM

[yaziciahmet]

single nit. merge after fix. also, have you tested this query with something like ethers.js?

I wasn't able to. ethers.js doesn't support this out of the box. It supports custom rpc requests with custom method and params, and it supports custom subscription topics for eth_subscribe, but it doesn't support debug_subscribe. When I sent rpc request with simply provider.send("debug_subscribe", [<args>]), it just returns the subscription id as that is the first response returned, but it doesn't know that it should wait, hence it ignores the rest.

I tested with wscat using the following command:

wscat -c ws://localhost:12345 -w 10 -x '{"jsonrpc": "2.0", "id": 1, "method": "debug_subscribe", "params": ["traceChain", "0x1", "latest"]}'

[eyusufatik]

  wasn't able to. ethers.js doesn't support this out of the box. It supports custom rpc requests with custom method and params, and it supports custom subscription topics for eth_subscribe, but it doesn't support debug_subscribe. When I sent rpc request with simply provider.send("debug_subscribe", []), it just returns the subscription id as that is the first response returned, but it doesn't know that it should wait, hence it ignores the rest.

I am suspecting more and more if this is going to replace trace filter 😅

anyways let's call it the more the merrier