eth-staking-on-aws
lodestar
| eth-staking-on-aws | lodestar | |
|---|---|---|
| 1 | 27 | |
| 10 | 1,060 | |
| - | 1.6% | |
| 4.1 | 9.8 | |
| almost 2 years ago | 6 days ago | |
| TypeScript | TypeScript | |
| MIT No Attribution | GNU Lesser General Public License v3.0 only |
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.
eth-staking-on-aws
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
What are some alternatives?
truffle - :warning: The Truffle Suite is being sunset. For information on ongoing support, migration options and FAQs, visit the Consensys blog. Thank you for all the support over the years.
lighthouse - Ethereum consensus client in Rust
kevlar - Light client-based RPC Proxy for PoS Ethereum
nimbus-eth2 - Nim implementation of the Ethereum Beacon Chain
web3-react - A simple, maximally extensible, dependency minimized framework for building modern Ethereum dApps
go-ethereum - Go implementation of the Ethereum protocol
zksync - zkSync: trustless scaling and privacy engine for Ethereum
teku - Open-source Ethereum consensus client written in Java
nitter-instances - Automated uptime monitoring of Nitter instances.
prysm - Go implementation of Ethereum proof of stake
grandine - High performance Ethereum consensus client
besu - An enterprise-grade Java-based, Apache 2.0 licensed Ethereum client https://wiki.hyperledger.org/display/besu