I’d like to get a sense for who’s working on what across both eth1.x and eth2. My goal is to identify areas of work where we know things need to be done but that nobody is actively working on.
Hi, this is Afri from the Görli Testnet Initiative.
After following ETH 2.0 client development loosely, we noticed there might be some coordination wanted towards a multi-client phase-0 testnet in the coming months.
We have resources available to support client teams in coordinating:
Coming up with a testnet spec that would work across multiple clients
Getting clients up to speed with networking, validating, synchronization, or anything else if necessary
We had a call previously with Danny and Hsiao-Wei two weeks ago, notes: hackmd io Nx204wkTSgeGB0UzNXhz9g
We explored the feasibility launching a beacon chain using the Lighthouse client this week, notes: hackmd io GIwaFeGaQn6q7VYb_n94LA
And published The-Practical-Dev article:
We’ve put multi-client testnet on the ETH-2.0-Call-36 agenda for next week and will eventually spin out dedicated calls for client teams to focus on joint testnet efforts in future: github.com ethereum eth2.0-pm issues 135
The overall goal would be, as opposed to previous interop efforts, to have a persistant state of interoperability across all clients, i.e., by not having a specially patched branch but rather having a baseline compatibility in the master/development code.
Please, hit me up if you want to discuss or coordinate. I’m @q9f on Discord and Github. (Sorry, can’t post more than two links here.)
I’m Alex Vlasov, from TX/RX team, ConsenSys/Pegasys.
I’m working on Clock Synchrronization Protocol for Eth2, right now.
Additionally, on fork choice tests.
More generally, I want to make sure that the subprotocols, that beacon chain relies on or requires (clock sync, node/topic discovery, libp2p) are BF tolerant and cannot be used to perform attacks on beacon chain protocol/Ethereum 2.
That includes (more detailed) Ethereum 2.0 security model.
I am Franck from ConsenSys/PegaSys, Consensus Protocol team, Sydney, Australia.
We are working on a formal specification of the Eth2.0 specifications using the Dafny verification-aware programming language.
Our first aim is to provide a formal specification/correctness proof of Eth2.0 Phase 0.
This is work in progress and we have started with SSZ and Merkleisation.
More generally, we endeavour to foster the use of formal methods in the development Blockchain systems.
Hello! I’m Ivan Martinez, an engineer for Prysmatic Labs.
I’ve been working mainly on the Slasher client lately, but I’m very familiar with our beacon chain and validator clients as well.
I’m extremely excited by EIP1559, and would like to help however I can. I would also like to help with the stateless effort but my cryptography knowledge still needs work. Particularly I’m interested in state providers but happy to help where I can.
Terence from Prylabs. I thought I’d drop by and say hi. Had a brief chat with Danny last week about supporting phase 1 implementation on Prysm. In my spare time, I’m building a proof of concept phase 1 client on top of Prysm
The goal of this proof of concept is to build 1-2 shard chains along side beacon chain to simulate what phase 1 will look like. Hopefully it serves to be useful to validate eth1.x core ideas and eth1.x -> eth2 migration, Feel free to ping me on telegram @terencechain if there’s any questions
Horacio from Team X (Enterprise, Cross Shard & Stateless - ECSS, pronounced X) in ConsenSys/PegaSys.
Cross-Shard: We implemented a PoC for Atomic Cross-Chain Function Calls for sidechains on Eth1, and are working on applying our learnings to Cross-Shard transactions on Eth2. Currently with focus on how to transfer Eth as part of the function call, building on the netting proposal.
Stateless: we are starting work on witness spec proposals, compression techniques, charging strategies and tiling; researching hexary-to-binary Merkle trie transition possibilities; and analysing the “three network” strategy and protocols.
Hello, this is Jonny Rhea from the TX/RX team (Consensys).
I am working on network health monitoring and testing strategies. A brief description of the plan:
Deploy a swarm of semi-autonomous network agents masquerading as an Eth2 node that communicate with a command & control service. This service will collect, aggregate and analyze information from individual agents to evaluate network health. Additionally the command & control service can coordinate the agents to perform attacks to the network, evaluating the security and resilience of the protocol.
