Closed cortze closed 2 months ago
There is no need to use it internally while the Hermes is running, but it's useful when you import Hermes as an EthNode service.
I could add some testing function if you think is necessary
If it isn't too complicated it would be good to add some tests 👍🏻
My bad, I've added some tests for all the ReqResp calls, but it relies on a local Prysm node. It is working locally:
probe-lab/hermes $ go test ./eth
ok github.com/probe-lab/hermes/eth 3.230s
Is it okay to Skip the test? I think that adding a docker image of Prysm to the test setup just to run these tests is overkill.
Yes it is totally fine to skip this test.
Description
We currently support all the libp2p protocols defined at the spec (when the requests are incoming); however, the current code doesn't allow us to request some of them actively (we miss requesting Blocks and Blobs).
This PR extends the list of Request that
Hermes
can do to support requestingBlocksByRangeV2
:The Trace would look like this:
OPTIONAL: If needed, I could also add the three missing calls (ref):
BlocksByRoot
,BlobSidecarByRange
, andBlobSidecarByRoot
), but I'll save the work bandwidth for now.