ethereum-org-website VS annotated-spec

The "bigger"/more extensive website is ethereum.org (https://github.com/ethereum/ethereum-org-website), guess people aren't as interested in the foundation as they are in the project itself. I think that's pretty standard in the cryptocurrency scene.

In this article, I'll be sharing my journey on how I contributed exactly one line of code to one of Ethereum's open-source repositories, Ethereum.org.

Ethereum

Make sure you understand enough about ethereum to invest in it. Just browse through https://ethereum.org. it's very well written.

Imo this is a big fail by the maintainers of ethereum.org by exposing uninformed users to additional risk that they're likely unaware of, and would love to ignore with the site advertising 9.36% APY.

The ethereum website is open source and project inclusion is kind of transparent. The origin ether inclusion issue is here: Add Origin Ether dapp · Issue #10293 · ethereum/ethereum-org-website · GitHub

https://ethereum.org - No

There can't be a user-controlled internet - which some call Web3 - if the user is not in control of the server. Using Jaxx Liberty infrastructure to create full-node, plug-and-play Andiami blockchain computers for individuals, our goal is to increase the decentralization of Bitcoin, Ethereum, and dozens more.

Community Lead @ ethereum.org

Hey u/cryptojobsgg I noticed you're not on the ethereum.org job sites list, might be worth looking into https://ethereum.org/en/community/get-involved/#ethereum-jobs

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.

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

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:

It's not about validators going offline, it's about the validator set changing. To quote the annotated specs

https://github.com/ethereum/annotated-spec/blob/master/phase...

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