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. (by ethereum)

Annotated-spec Alternatives

Similar projects and alternatives to annotated-spec

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better annotated-spec alternative or higher similarity.

annotated-spec reviews and mentions

Posts with mentions or reviews of annotated-spec. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-02-17.
  • Daily General Discussion - February 17, 2023
    5 projects | /r/ethfinance | 17 Feb 2023
  • Can't the Sync Committee be cheaply bribed, and therefor serves no real purpose for security?
    1 project | /r/ethdev | 14 Jan 2023
    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
    6 projects | news.ycombinator.com | 24 Aug 2022
    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
    11 projects | news.ycombinator.com | 7 Jul 2022
    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?
    1 project | /r/ethstaker | 27 Apr 2022
    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
    2 projects | /r/ethfinance | 20 Feb 2022
  • My First Impressions of Web3
    12 projects | news.ycombinator.com | 7 Jan 2022
    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
    2 projects | /r/ethstaker | 23 Dec 2021
    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
    3 projects | news.ycombinator.com | 28 Nov 2021
    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
    1 project | /r/ethstaker | 19 Nov 2021
    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.
  • A note from our sponsor - SaaSHub
    www.saashub.com | 26 Apr 2024
    SaaSHub helps you find the best software and product alternatives Learn more →