g11tech
g11tech
> @g11tech do you mind having a look here if we still want to keep this issue (please otherwise close)? yes @holgerd77 most probably this is taken care of, will...
yes handled in while syncing forward (pre-merge) - https://github.com/ethereumjs/ethereumjs-monorepo/pull/2230 else beacon sync's skeleton handled here: https://github.com/ethereumjs/ethereumjs-monorepo/blob/master/packages/client/lib/sync/fetcher/reverseblockfetcher.ts#L61 Both cases lead to banning of peer and sync tries to sync from other...
Wow! really amazing PR! @acolytec3, @jochem-brouwer :heart: :fire: :rocket: successfully able to hookup the jsonrpc to my local mainnet node and able to run this block successfully: https://etherscan.io/block/15496421  Feels...
> This seems directly related to something I encountered in the `miner` test during: #1995. > > There is a test in `miner.spec.ts` where we build a `FakeChain`, and assign...
> When calling `getAccountRange`, the `proof` and `accounts` arrays contain data elements that look like this: > > ``` > { > account: { > hash: , > ..... >...
yes we need separate fetchers for fetching each of the ranges :+1:
> @g11tech I wasn't able to get `forceSnapSync` option to work. I would set it like this: > > ``` > DEBUG=devp2p:* npm run client:start:dev2 -- --forceSnapSync=true ... > ```...
:tada: the fetcher syncs range on mainnet! (and then create new tasks and sync them further) 
> @g11tech We already have a delay set for such cases of errors. > > https://github.com/ChainSafe/lodestar/blob/6ac8c07023bc72c7ef54a6ea66884790793eda21/packages/beacon-node/src/eth1/eth1DepositDataTracker.ts#L182-L186 > > And the http errors `UNAVAILABLE` or `TIMEOUT` can actually be fatal. We...
> @g11tech can I assume that this one is (completely) outdated? thinking Or has this "uphold itself" over all refactors? joy lol, yea i think there are enough tests covering...