acolytec3
acolytec3
@ScottyPoi putting this on my todo list for tomorrow. I'll need to see what `leveldb` supports.
Should be done with #593
#537 should partially fix this. It at least deals with the `ContentAdded` message redundancies.
Will close for now. We have bigger fish to fry.
@holgerd77 I'm guessing [this question](https://github.com/ethereumjs/ultralight/issues/527#issuecomment-1816997248) is related to this tracking issue maybe? If so, then this is specifically the [lodestar light client](https://github.com/ChainSafe/lodestar/blob/unstable/packages/light-client/src/index.ts) and not the full beacon client. It's quite...
Have added: - `beacon_getHead` - returns the capella fork Light Client Header corresponding to the current known head block - `beacon_getFinalized` - returns the capella fork Light Client Header corresponding...
Added `beacon_getLightClientUpdate` was added in #530
This [PR](https://github.com/ethereum/portal-network-specs/pull/322) documents all the official beacon RPC endpoints we should implement. I think we have most of them already but should confirm against this list.
We're missing quite a few after referencing the list above. But, we're missing lots of endpoints all around, the entire `trace` sub-namespace is missing so we should think about implementing...
This is still happening and the logging is weird. We need something in the `handleFinPacket` method that closes the socket so if we get a dup `FIN` packet we don't...