Ethereum 2.0 Beacon Chain Simulation

Project Name

Beacon Thugs n Harmony

Project Tagline/Description

Ethereum 2.0 Beacon Chain Simulation.

Team Members. First and Last Names

Richard Ma, Nathan Frenette, Poming Lee, Derek Alia

Status.im ID for Each Team Member

https://get.status.im/user/0x04eb427697caf4cf2334aa814657801b1f138f908f180cc4f60a7e87d5fd45fc0963416a91aa943cd8edfd232c866b0bd0eaab1a9c6168ee781f8bf79c85a821c9

Detailed Project Description

Implements a simulation for the sharded pos ethereum 2.0.

The Eth 2.0 Spec is very difficult to understand and we thought making it easier to visualize is one of the most impactful things we could do to drive scalability development forward for the community, and make it easier for people to use Dapps

The challenging research task involved pulling together incomplete outlines and disparate sources, including ethresear.ch, presentations from Justin Drake, as well as papers from Vitalik.

The React web app at www.beacon-chain.com created using the simulator allows a developer to step forwards and backwards through 2.0 ETH Beacon Chain randomness generation, and see how it feeds into the shard validator selection at each epoch.

Beacon Chain Web App Image

Describe your tech stack (e.g., protocols, languages, API’s, etc.)

Python, Apache Server, Javascript, React, pycrypto, RSA library

Track for which you’re submitting (Open or Impact)

Open

Bounties

This is a pure ETH 2.0 research project, so it didn't fit the project bounties

https://github.com/beacon-thugs-harmony/beacon_chain_simulator

https://github.com/beacon-thugs-harmony/beacon_thugs_frontend

Web Application: http://www.beacon-chain.com/

Important note

We found a potential attack vector to the beacon chain while we were building the simulation - a malicious actor can DDoS the validator during their RANDAO slot, between the hash submission and the reveal - and cause them to lose money via the penalty. This shows the value of having a simulation