randao
lodestar
randao | lodestar | |
---|---|---|
7 | 27 | |
826 | 1,060 | |
0.0% | 1.6% | |
0.0 | 9.8 | |
about 1 year ago | 5 days ago | |
JavaScript | TypeScript | |
GNU General Public License v3.0 only | 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.
randao
-
Gas is the cheapest it's been in a long time. Imagine that this will be the norm a year or so from now
There's really no "forcing", in sharding validators are randomly assigned to a shard, similarly to how they're currently randomly split up into committees that attest to the validity of blocks. There's no centralizing force: the randomness into the process is provided in a decentralized fashion by the validators themselves, through a mechanism called RANDAO.
-
Explaining Ethereum's consensus mechanism after The Merge
Article author here.
Great questions, should have explored the randomness beacon more. Ethereum uses [RANDAO](https://github.com/randao/randao), which is a distributed commit-reveal scheme where participants in the generation post a hash of their data on the commit portion and then at a later timestamp reveal the data preimage, and get slashed if they do not reveal a correct preimage. Then all participant data is aggregated together. This means if there is at least one honest participant the generation will be random.
A supermajority (2/3rds) of validators is required to finalize a block, in case of a 50-50 network partition blocks would stop being finalized and attestation rewards would stop. Non-participating validators would slowly leak stake through the inactivity leak until online validators once again had a supermajority. This is the "self-healing" mechanism that allows both safety and liveness.
-
How does Eth 2.0 PoS choose block proposer randomly?
https://github.com/randao/randao Is this what youβre referring to? It says itβs a DAO.
-
Proposals on random
So according to this generating randoms for the eth chain is like validating but with shorter cycle and more profitable. Now I have even more questions like: How can I participate Is there software like prysm for using random contracts What is the minimum stake for random contracts Is anyone doing this, is it wort it
-
Suggestion for multiple-user seed
Thank you Eric, I discussed it too in the PoolTogether discord and got this reponse from one of the founders: " What you're describing is a version of "RANDAO". See here: https://github.com/randao/randao Really, the VRF is an unnecessary step if a seed is being selected by all participants If you look through the above project, you'll see they try to handle a few corner cases like if a user refuses to reveal their seed, or preventing a seed from being used twice The trouble with Randao is the amount of coordination and expense that it incurs. " I understand ETH 2.0 will be doing some implementation of RANDAO along VDFs for the Beacon chain. Algorand implements this too. I found this talk from Justin Drake talking about this algorithm: https://www.youtube.com/watch?v=zqL_cMlPjOI
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?
ethereumbook - Mastering Ethereum, by Andreas M. Antonopoulos, Gavin Wood
lighthouse - Ethereum consensus client in Rust
openzeppelin-solidity - OpenZeppelin Contracts is a library for secure smart contract development. [Moved to: https://github.com/OpenZeppelin/openzeppelin-contracts]
nimbus-eth2 - Nim implementation of the Ethereum Beacon Chain
openzeppelin-contracts - OpenZeppelin Contracts is a library for secure smart contract development.
web3-react - A simple, maximally extensible, dependency minimized framework for building modern Ethereum dApps
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.
go-ethereum - Go implementation of the Ethereum protocol
teku - Open-source Ethereum consensus client written in Java
zksync - zkSync: trustless scaling and privacy engine for Ethereum
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.