consensus-specs
lodestar
consensus-specs | lodestar | |
---|---|---|
158 | 27 | |
3,432 | 1,060 | |
1.3% | 1.6% | |
9.8 | 9.8 | |
7 days ago | 5 days ago | |
Python | TypeScript | |
Creative Commons Zero v1.0 Universal | 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.
consensus-specs
- Daily General Discussion - June 23, 2023
-
Daily General Discussion - May 20, 2023
I think its 1 million: https://github.com/ethereum/consensus-specs/issues/2137
-
Ethereum's pending withdrawals total $1.34 billion after Shapella
how "radically decentralized" the development of the Ethereum core is. In the past half a decade only 133 devs have contributed to Ethereum source code. 2 devs have written 25% of the code. The first 10 developers have written 70% of the Ethereum code. Consensus specifications the ones that all the clients implement. Half are Consensys employees https://github.com/ethereum/consensus-specs
-
Daily General Discussion - February 18, 2023
I think this will be defined here: https://github.com/ethereum/consensus-specs/blob/dev/specs/deneb/fork-choice.md
- Daily General Discussion - February 17, 2023
-
There are over 7000 pending validators on the Ethereum test net. Looks like a lot of people want to practice staking before the Shanghai hardfork
Clients dependent on Consensys core and ETH management repo. A client is just the implementation directed by Consensys written in a different language. Fact is about 10 developers are the only reason those clients will update with staking. https://github.com/ethereum/consensus-specs
-
Set your Ethereum validator withdrawal address with CLWP today
Exits are processed at 7 per epoch (currently). There is no queue for withdrawals. See https://github.com/ethereum/consensus-specs/pull/3068
-
Evolution of the Ethereum Proof-of-Stake Consensus Protocol
https://github.com/ethereum/consensus-specs/blob/dev/specs/p...
-
How to merge an Ethereum network right from the genesis block
For that, we have to take the vanilla deposit contract from the consensus specs: deposit_contract.sol, get the Solidity compiler version 0.6.11, compile the binary of the runtime part, and create an empty deposit tree.
-
Centralization of ETH developer community?
The PoS consensus specification
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?
l2beat - L2BEAT is an analytics and research website about Ethereum layer two (L2) scaling solutions.
lighthouse - Ethereum consensus client in Rust
ethereum-org-website - Ethereum.org is a primary online resource for the Ethereum community.
nimbus-eth2 - Nim implementation of the Ethereum Beacon Chain
ergo - Ergo protocol description & reference client implementation
web3-react - A simple, maximally extensible, dependency minimized framework for building modern Ethereum dApps
annotated-spec - Vitalik's annotated eth2 spec. Not intended to be "the" annotated spec; other documents like Ben Edgington's https://benjaminion.xyz/eth2-annotated-spec/ also exist. This one is intended to focus more on design rationale.
go-ethereum - Go implementation of the Ethereum protocol
scaffold-eth - 🏗 forkable Ethereum dev stack focused on fast product iterations [Moved to: https://github.com/scaffold-eth/scaffold-eth]
zksync - zkSync: trustless scaling and privacy engine for Ethereum
rust-libp2p - The Rust Implementation of the libp2p networking stack.
teku - Open-source Ethereum consensus client written in Java