g11tech
g11tech
@dapplion yes this is the current expected behavior, if EL is unavailable or not responding or throwing error on a block, process block/process segment fails and it gets retried., and...
~~Metrics i will review and add 👍~~ I think that PR (retry PR) also had metrics regarding the requests.
> > but that PR by @dadepo has never got merged. > > Which PR? this one: https://github.com/ChainSafe/lodestar/pull/3854, i think @dadepo was waiting for your final :heavy_check_mark: . will rebase...
my 2 cents: I actually like that we got, helps us recover lots of random scenarios by restarting, especially where local EL can be buggy in post-merge world by having...
usage doc: https://github.com/ChainSafe/lodestar/blob/unstable/docs/usage/mev-integration.md tl-dr: 1. Provide lodestar BN with a Builder endpoint (which corresponds to the network you are running) via these additional flags: ```shell --builder.enabled --builder.urls ``` 2. Run...
> Issues found during testing: > > * [MaxListenersExceededWarning: Possible EventTarget memory leak detected. ChainSafe/lodestar#4394](https://github.com/ChainSafe/lodestar/issues/4394) > > * [error: Error updating eth1 chain cache Timeout request ChainSafe/lodestar#4395](https://github.com/ChainSafe/lodestar/issues/4395) > > *...
> Thank you @g11tech. My beacon node has 3 more days left for syncing. I'll share anything weird that happens. which networ are you syncing? may be I can provide...
> I'm in kiln. Now I should actually stop and restart with goerli. And yes please, how do I make this faster? :) DM me on discord pls will share...
i feel that v1.1.0 has shown auto peer recovery on my installations even after dropping to low double digits because of network turbulence, without requiring me to clear peerstore that...
This error seemed to be have thrown the URL from where its being synced, its *should* not be a problem with lodestar but worth checking out