kdeme

I think it would be a good plan to already put this PR in a cleaned-up state that would be ready to review / ready to merge. Your changes into...

> Just my thoughts, curious to hear what others in the team think. Verified proxy is definitely lacking a good set of tests which currently makes it difficult making changes...

I think one other important item is adding the REST version of the consensus light client sync. The web3 purifier makes most sense in web and mobile wallets, where the...

> Is "reduce code duplication between fluffy and nimbus verified proxy" still salient? I'm not sure what the current situation for Fluffy is in that regard, in particular. No, it...

Might want to wait here to see what comes out of the EraE & EraC effort. Or implemented e2hs (+ generation of those): https://github.com/eth-clients/e2store-format-specs/blob/main/formats/e2hs.md

> 2\. `129` is invalid exit code number because it falls into the signals range. For Linux `SIGHUP` signal sent to process could also return exit code `129` I don't...

Part 1: https://github.com/status-im/nim-eth/pull/707 More parts to do: - Rework also the decoding of an ENR (need to move id key check and possibly others?) and then make toTypedRecord no longer...

> I'm not sure if it ever checks for which type to use: It does not. Unused config setting.

After further debugging this, it seems that the issue is not in the lookup mechanism as the those nodes that have the data do get contacted. However the uTP connection...

The node is hitting specifically this error: https://github.com/status-im/nim-eth/blob/aa92ad4f42d772c53ce4a2d9c76cf760b4450031/eth/utp/utp_socket.nim#L587 With a `retransmitCount=2`, so it appears that no ACK on the uTP is not received.