lodestar VS nitter-instances

I think I found it. This pull request helped me: https://github.com/ChainSafe/lodestar/pull/3782

Somer's guides are awesome and extremely thorough, but they help you learn to build a validator from scratch. In practice, I always download client binaries rather than building from scratch. You can find the lodestar releases page here.

https://github.com/ChainSafe/lodestar 63 contributors

My mainnet lodestar node crashed today. Thankfully, the validator process switched over to my backup lighthouse node without missing a single attestation.

Daily Goerli: I've been periodically running into some issues when updating nethermind which require force killing the Nethermind.Runner process. Recently had an issue where geth in lodestar-geth thought it was waiting for updates from lodestar, but lodestar was reporting connection refused. A restart of geth fixed it. I'm currently running into No state found for id 'head' in all lodestar instances, which was supposed to be fixed by this PR. I also recently encountered a long stack error from erigon in prysm-erigon when closing to update, but restarting both clients allowed sync to resume.

The following sections outline how to configure an execution-layer client and a consensus-layer client so that they have everything in place to execute the entire merge already in the genesis block. Here, we'll use Geth and Lodestar.

Consensus Layer client ✅ Teku v22.11.0: https://github.com/ConsenSys/teku/releases/tag/22.11.0 ✅ Lodestar v1.2.2: https://github.com/ChainSafe/lodestar/releases/tag/v1.2.2 🟡 Lighthouse: coming soon 🟡 Nimbus: coming soon ❌ Prysm: advised to switch to other clients

There was some change (not known whether intended or not) that twitter links no longer work for non-logged users. So either hope someone will reupload it somewhere, or try using one of the nitter instances https://github.com/xnaas/nitter-instances.

Yes, use a nitter instance.

https://github.com/xnaas/nitter-instances

Searching for twitter usernames isn't working, use the tweet search tab or type a twitter username on the end of the url.

If it says "This nitter instance has been rate limited" then choose a different one from the above list.

Nitter is still working, although searching for users seems to have stopped working you can still use the tweet search tab or manually type a twitter username on the end of the URL.

List of nitter instances:

https://github.com/xnaas/nitter-instances

They unpredictably say "This nitter instance has been rate limited", you can try a few from the above list to find one that is getting less traffic.

I just tested one and the RSS worked fine. Did you try using a different instance?