kdeme
kdeme
Can reproduce the exact same issue with a Trin node on the requesting side instead of Fluffy so I created an issue there: https://github.com/ethereum/trin/issues/1596
So there seems to be an issue with Trin nodes in case a node is not reachable from the outside and has no IP in its ENR: see this issue...
Yes, this is about not yet canceling the request until we are certain that the current one that we received has been validated and is correct. Practically that would probably...
> Note that the validation handler will need to be passed in to each call to contentLookup because the handler will be different for each type of content being validated...
Yes, you're right. It is not needed and history network already asks the header upfront as is. The code changes I am doing also remain doing it like that, I...
OK, it could also be that we simply copied them from https://data.ethpandaops.io/era1/sepolia/ , which has the same issues
Does seem to be more of a geth issue: https://github.com/ethereum/go-ethereum/blob/1e4b39ed122f475ac3f776ae66c8d065e845a84e/internal/era/eradl/checksums_sepolia.txt#L179-L183
When it says `discv4="disc: msg missing hash" discv5="Invalid protocol id"`, it's actually the case of neither v4 nor v5 worked. - discv4: First thing done is checking the hash of...