Proteus

honestly kind of dumbfounded this isn't already part of the scripts... why would anyone want their vpn to be able to drop and have virtually no clue its happened? with...

> besu keeps on displaying over and over again: > > ``` > 2022-09-18 14:45:49.324+00:00 | vert.x-worker-thread-0 | INFO | EngineForkchoiceUpdated | SYNCING for fork-choice-update: head: 0xeb65bbec224374d13e8afe868656f1d0c7bb7a4d765e1f813f977df547c7b198, finalized: 0x3b50cfe3e2882f21f909baef91c53d1105c77639d02dcc9346f7e08351b2dd90, safeBlockHash:...

> I think besu requires a full validator node (teku). I removed my teku validator keys from the config to test. and besu is no longer syncing/importing blocks. > >...

> For those interested I was able to solve this, turns out Besu needs an in-sync consensus client in order to continue the sync past the "stuck" block and since...

> > I had already done this (loaded beacon state from my already sync'd nimbus on teku). It does appear my issue may have cleared up. I'm getting progress just...

Update - still unable to fully sync. It appears it just never completes the Worldstate download. It imports blocks up to the current block and then just hangs while it...

> It appears that it's not possible to synchronize Besu post-merge independently as a standalone Execution Client at this time. > > Had a fully synchronized Besu node to post-merge...

Same happening to me also on Ubuntu 22.04.3