lodestar
lighthouse
Our great sponsors
lodestar | lighthouse | |
---|---|---|
27 | 124 | |
1,053 | 2,718 | |
2.8% | 2.6% | |
9.8 | 9.7 | |
7 days ago | 6 days ago | |
TypeScript | Rust | |
GNU Lesser General Public License v3.0 only | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
lodestar
-
Help needed to navigate in lodestar code
I think I found it. This pull request helped me: https://github.com/ChainSafe/lodestar/pull/3782
-
Daily General Discussion - May 21, 2023
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.
- Lodestar v1.8.0 released!
-
Ethereum's pending withdrawals total $1.34 billion after Shapella
https://github.com/ChainSafe/lodestar 63 contributors
-
Daily General Discussion - April 6, 2023
My mainnet lodestar node crashed today. Thankfully, the validator process switched over to my backup lighthouse node without missing a single attestation.
- Lodestar v1.7.0 released (Shapella ready)
-
Daily General Discussion - December 28, 2022
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.
-
How to merge an Ethereum network right from the genesis block
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.
-
Gnosis Merge-ready release clients
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
lighthouse
-
On Implementation of Distributed Protocols
Lighthouse β an Ethereum consensus client (written in Rust);
- Daily General Discussion - July 5, 2023
- Lighthouse Release v4.3.0
-
Daily General Discussion - May 25, 2023
Daily Goerli: A whole lot more detail on the lighthouse db corruption issue I posted about previously. There's a warning that's been quite frequent on my erigon nodes for a while that doesn't seem to have any impact on its performance. I asked if it should be downgraded to INFO here.
- Lighthouse Release v4.2.0 (Fast Aging Alien)
-
Did I really waited 259 days and missed a 2,29 ethereum block proposal?
According to lighthouse team, the root cause was beacon node waited too long before requesting the payload header. All details here : https://github.com/sigp/lighthouse/issues/4312
- Lighthouse Release v4.1.0 (Uncle Steve)
-
Various validator issues around Shapella
Update LH to 4.0.2-rc.0 More info here https://github.com/sigp/lighthouse/releases/tag/v4.0.2-rc.0
-
Cryptoβs Ethereum Network Completes Key Software Upgrade Without a Hitch
Which is not true... full nodes are consuming a lot of CPU now... hot-fix was released, but didn't solve the problem completely: https://github.com/sigp/lighthouse/releases/tag/v4.0.2-rc.0 ... more hot-fixes will be needed
-
Ethereum's pending withdrawals total $1.34 billion after Shapella
https://github.com/sigp/lighthouse 142 contributors
What are some alternatives?
nimbus-eth2 - Nim implementation of the Ethereum Beacon Chain
prysm - Go implementation of Ethereum proof of stake
web3-react - A simple, maximally extensible, dependency minimized framework for building modern Ethereum dApps
go-ethereum - Official Go implementation of the Ethereum protocol
zksync - zkSync: trustless scaling and privacy engine for Ethereum
Nethermind - A robust execution client for Ethereum node operators.
teku - Open-source Ethereum consensus client written in Java
Parity - (deprecated) The fast, light, and robust client for the Ethereum mainnet.
nitter-instances - Automated uptime monitoring of Nitter instances.
ethers-rs - Complete Ethereum & Celo library and wallet implementation in Rust. https://docs.rs/ethers