RT @prylabs: Our first release including a local demo of Ethereum 2.0 so far, is live! https://t.co/4clpes1Dky
Come check out the following:
💎 Spin up a beacon chain node from a genesis config
💎 Connect a validator to the beacon node
💎 Validator gets shuffled into a shard and slot
What you're looking at is an implementation of the sharding and casper consensus protocols. A protocol consists of the rules that need to be followed, in the case of Bitcoin that's Nakamoto Consensus. An implementation can be written in any programming language, but as long as it follows the protocol, then people running the implementation can communicate with other implementations of the protocol. Anyone can make an implementation. The two most widely used in Ethereum 1.0 are go-ethereum and Parity, but there are several others all written in different programming languages.
Awesome thank you so much for that response. What does this mean for the future of ethereum? Is this significant for its development? What can you potentially accomplish with these other languages that you couldn't with the original?
Yes this is incredibly significant. This is the first steps to fully building out an implementation and client for Ethereum 2.0. There are several teams working on their own implementation of the current spec, such as Lighthouse, Prysm, etc.
I would say it's very significant. We're finally seeing what a pure proof of stake protocol would look like on Ethereum. People have been waiting a long time for PoS, but of course it's certainly not a trivial problem to solve. I doubt it's even close to being finalized, but things are progressing rapidly now it seems.
Having multiple implementations is fairly important I would say. It reduces risk somewhat. If there's a bug in one client, it won't affect the entire network. It also allows for clients to run on different operating systems.
No problem! I'm glad that traders/investors/speculators are getting interested in the tech! Here's a link to Lighthouse (the other team that I know of working on an implementation) https://lighthouse.sigmaprime.io
They don't have a public demo or open source code yet though. I imagine there will be even more teams working on clients as the spec is more finalized. These really are the pioneer implementers.
> This chain is synchronized with the current Proof of Work chain’s latest block hashes.
Just to be clear, so the plan is to have an initial hybrid PoW + PoS phase 0 where there's a beacon chain implementing RANDAO + PoW blockhashes as sources of entropy?
I was a little confused on that since the switch from FFG to Shasper, I wasn't sure if there was still going to be an initial PoW/PoS hybrid.
Hmm....my thinking was basically that since RANDAO is potentially manipulable through "last reveal" attacks that prior to using VDFs they might use PoW blockhashes as an additional source of biasable entropy (but maybe that wouldn't actually make a difference if the blockhash is known before the reveal phase of RANDAO is over?).
Justin Drake does [mention](https://ethresear.ch/t/minimal-vdf-randomness-beacon/3566) using PoW blockhashes to get everything rolling since there has to be a way to select block producers to run the scheme through the first time. Maybe that's only a once off though...
My main Q really is about whether there is a plan to have a hybrid PoW/PoS using the beacon chain.