Ethics3606
Ethics3606
> Sounds peering related. Try the following: > > Delete the addressbook.json file in your beacond home directory > > $BEACON_HOME_DIR/config/addrbook.json > Then kill your beacon node, then execution client...
> It's likely still peering but perhaps a different issue to the one my solution solves. Can you dump your beacond and execution logs next time it gets slow. Also...
Happened again today. Were the logs useful?
> It's likely still peering but perhaps a different issue to the one my solution solves. Can you dump your beacond and execution logs next time it gets slow. Also...
I will gladly pay 500$ for a rapid fix to this problem.. Its causing me trading losses
> Hey [@Ethics3606](https://github.com/Ethics3606) thanks for your update: > > * we're looking at this as our top priority > * no need to pay anything. > > A couple of...
> Looking forward to it. The reason I ask if EL is Reth is because we are seeing an unusually high latency over some rpc calls if compared with Geth....
> Looking forward to it. The reason I ask if EL is Reth is because we are seeing an unusually high latency over some rpc calls if compared with Geth....
> Well if anything, v.1.1.3 keeps CL and EL in lockstep, so any latency issue is likely to be amplified wrt 1.1.2 (which has other issues, namely a deposit mismatch...
Trying 1.1.4 with Reth and geth