nsfminer VS lodestar

wget https://github.com/no-fee-ethereum-mining/nsfminer/releases/download/v1.3.14/nsfminer_1.3.14-ubuntu_20.04-cuda_11.3-opencl.tgz tar xzvf nsfminer_1.3.14-ubuntu_20.04-cuda_11.3-opencl.tgz cd nsfminer ./nsfminer -P stratum1+tcp://[email protected]:6688 --retry-max 0

I discovered ethminer that time and was happy to see great example of collaboration in crypto dev community, it was outdated for newest CUDA, so I found nsfminer, that's the fork updated by one of previous contributors. It has no DEV fee and based on original ethminer, so I pretty much trust the code, even if it has no maintenance since mid of 2021.

This one's better: https://github.com/no-fee-ethereum-mining/nsfminer

I've never used it, but NSFMiner is supposed to be a fork of Ethminer, except the author updated it to support 30 series. https://github.com/no-fee-ethereum-mining/nsfminer

Not really. There are protocols between miner software and pool operators. There are also some miner software out there that can evaluate prior to submission to the pool if a hash result is invalid or not. The open source ethminer used to do it until it's development stopped. Pretty sure some devs forked the code into NSFminer.

I would not risk it. If you need to use one on a device with sensitive info, I'd go with an open source version https://github.com/no-fee-ethereum-mining/nsfminer

Here is link number 2 - Previous text "Two"

Happens because of this devfee bullshit. Get a miner that does not steal from you. Open source https://github.com/no-fee-ethereum-mining/nsfminer

I switched to flexpool with nsfminer.

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