annotated-spec
nimbus-eth2
annotated-spec | nimbus-eth2 | |
---|---|---|
44 | 70 | |
312 | 492 | |
0.0% | 1.0% | |
0.0 | 9.8 | |
3 months ago | about 9 hours ago | |
Nim | ||
- | GNU General Public License v3.0 or later |
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.
annotated-spec
- Daily General Discussion - February 17, 2023
-
Can't the Sync Committee be cheaply bribed, and therefor serves no real purpose for security?
My current understanding: The Sync Committee selects 512 validators to continually sign off on block header. Any block headers that get >2/3 are "valid"1, such that Light Clients using this header for verification can trust it.
-
Ethereum Mainnet Merge Announcement
https://github.com/ethereum/annotated-spec/blob/master/phase...
Here we have slashing fields in the block body where you insert your proofs of slashable offense. There are functions with a “slash” in the name that describes precise state transition.
The hard part of slashing is finding these proofs because you have to do more work than necessary to detect slashing and produce proofs - that’s what this software does. It’s more expensive to run a slasher but you need only one and it does not matter who runs it, anyone can run it. The link that you sent says that this slasher broadcasts proofs by default - that way anyone can include it.
-
Explaining Ethereum's consensus mechanism after The Merge
According to Eth docs:
> One validator is randomly selected to be a block proposer in every slot. This validator is responsible for creating a new block and sending it out to other nodes on the network. Also in every slot, a committee of validators is randomly chosen, whose votes are used to determine the validity of the block being proposed.
The annotated code for this can be found in [2].
[1] https://github.com/ethereum/annotated-spec/blob/master/phase...
[2] https://notes.ethereum.org/@vbuterin/Sys3GLJbD#Misc
-
Daily staking income was irregularly high, anyone knows why?
Here's some more info on Sync committees if you are interested. https://github.com/ethereum/annotated-spec/blob/master/altair/sync-protocol.md
- Daily General Discussion - February 20, 2022
-
My First Impressions of Web3
The crux of the article is that the front-ends are all routing calls through centralized APIs to get their message included on the blockchain. Infura and Alchemy don't do much. They just pass a JSON-RPC message to an Ethereum node running on their servers. There is some additional indexing services they provide, but there are many open, decentralized alternatives for that such as TheGraph Protocol. And it's not unfeasible for an application to run its own Postgres instance to index data from the ETH blockchain.
As for full-fat clients on normal mobile devices, the main issue is the data requirements. Running a full node can take hundreds of gigabytes. It is possible on light hardware. People are running Beacon chain nodes on Raspberry Pis. But you do need the storage and that tends to be scarce on mobile.
Meanwhile, the Ethereum core devs are aware of this issue and are actively working towards it. They shipped the Altair hard fork this year that has adds sync committees which make it possible to do without needing the whole chain history (using merkle trees): https://github.com/ethereum/annotated-spec/blob/master/altai...
The light client to follow from those improvements is forthcoming:
-
ETH2.0 withdrawal roadmap post merge
It's not about validators going offline, it's about the validator set changing. To quote the annotated specs
-
Proof of stake is a scam and the people promoting it are scammers
Even a relatively light reading of the Annotated Spec[1] for Eth2 and/or the Eth Org's Proof of Stake FAQs[2] suggests the designers (and independent implementer-teams who gave feedback to designers... lather, rinse, repeat) understand it's important to consider the overall system "outside of the comfort zone".
[1] https://github.com/ethereum/annotated-spec/blob/master/phase...
[2] https://eth.wiki/en/concepts/proof-of-stake-faqs
-
Help understanding staking factors
Alpha leak: I am currently finishing up a full revision of my annotated specification for Altair, and plan to get it published in a couple of weeks. Meanwhile Vitalik's annotated spec has some info on how base rewards work under Altair.
nimbus-eth2
- Nim v2.0 Released
-
Crystal 1.9.1 Is Released
Agreed! There's a couple of fairly large projects in Nim: https://nimbus.team/ (https://github.com/status-im/nimbus-eth2) or https://github.com/zedeus/nitter
Though there's still friction points I've been happy seeing the ecosystem grow lately. The compiler has seen a lot of bug fixes lately too which helps.
-
Daily General Discussion - June 22, 2023
Pretty big update for Nimbus out today, it's been a long time coming: https://github.com/status-im/nimbus-eth2/releases/tag/v23.6.0
-
erigon sync log correct?
consensus client/execution client -> ERIGON v2.45.2 and NIMBUS v23.5.1
-
[1 Year Review] Status still hasn't released anything or gained any real market share in private messaging
In the same year their beacon chain client followed Bellatrix (Merge) and Capella upgrades without a hitch, which is in many ways more impressive than a messenger.
-
Daily General Discussion - May 19, 2023
Nimbus claims to have a solution to the loss of finality problem that was caused by old attestations, by dramatically speeding up the verification of those attestations: https://github.com/status-im/nimbus-eth2/pull/4911
- Daily General Discussion - May 12, 2023
-
Daily General Discussion - May 9, 2023
Seems they just released 23.5.0, to fix many of the issues we've been having: https://github.com/status-im/nimbus-eth2/releases/tag/v23.5.0
-
Ethereum's pending withdrawals total $1.34 billion after Shapella
https://github.com/status-im/nimbus-eth2 69 contributors
-
Daily General Discussion - March 31, 2023
Daily Goerli: Was getting a lot of missed attestations with nimbus and after some back and forth with tersec, we confirmed that timeouts communicating with web3signer were the culprit. A fix should be merged soon.
What are some alternatives?
ethmerge.com-content - Markdown formatted content for the ethmerge.com website.
lighthouse - Ethereum consensus client in Rust
consensus-specs - Ethereum Proof-of-Stake Consensus Specifications
prysm - Go implementation of Ethereum proof of stake
pm - Project Management: Meeting notes and agenda items
lodestar - 🌟 TypeScript Implementation of Ethereum Consensus
ens - Implementations for ENS core functionality: The registry, registrars, and public resolvers.
Nethermind - A robust execution client for Ethereum node operators.
crypto-fees - Website for comparing total daily fees of various blockchain protocols.
teku - Open-source Ethereum consensus client written in Java
EIPs - The Ethereum Improvement Proposal repository
libsignal - Home to the Signal Protocol as well as other cryptographic primitives which make Signal possible.