Introductions for the Eth1.x research group

Execution Layer Research
4
  1. Piper (pipermerriam in most places), Snake Charmers team lead
  2. Mostly the Trinity client, Lots of Python stuff.
  3. Beam sync, Stateless clients, Making client development easier and making running a client easier.
5
  1. Alexey, Ethereum researcher and developer
  2. Turbo-Geth + Stateless Ethereum prototyping/specifications
  3. Most of the things on this list: https://ledgerwatch.github.io/Ethereum_1_Research_topics.html, particularly those where there is more text :slight_smile: warning - this is not a permalink, it will keep changing
6
  1. Jason Carver (@carver typically)
  2. Trinity, other python things
  3. Reducing friction to launching nodes, so:
    1. Sync Speed
    2. Sync Speed
    3. Sync Speed
    4. Growing disk usage
    5. Sync Speed
7
  1. Danno Ferrin (@shemnon most places)
  2. Hyperledger Besu, and just plain old Besu too.
  3. My interests, in order of importance
    a. Stateless clients and other means to address state size
    b. EVM evolution
    c. EVM performance
8
  1. Griffin Hotchkiss (@gichiba most places)
  2. Writing (technical), documenting the state of 1.x research for a wider audience, asking basic questions.
  3. I’ll follow the pulse of what lines of research seem the most fundamental, which at the moment I believe is stateless clients.
1 Like
9
  1. John Adler
  2. Solving the scalability problem
  3. On the Eth 1.x front, optimistic rollup and improvements to the base chain for rollup schemes, which make state growth a non-issue in practice
    1. Multi-threaded data availability and data pre-processing (research) (first EIP of several)
    2. Integrating data availability proofs to get sharding scalability without sharding (research)
10
  1. Martin Lundfall
  2. Formal semantics (beacon chain), hevm, spec writing
  • Statelessness
  • Concurrent tx processing
  • EVM evolution
11
  1. Matt Garnett
  2. Eth2 virtual machine, stateless execution, and EE design
  3. Understanding the needs of Eth 1.x to help advocate for eth2 VM design decisions
2 Likes
12
  • Thomas Jay Rush
  • TrueBlocks
  • I’m just going to be a watcher. I suspect that stateless clients will make recovery of transaction histories from previously unmonitored addresses in a decentralized way much more difficult if not impossible. Need to educate myself, though.
13
  1. Sina Mahmoodi
  2. ethereumjs/ewasm
  3. stateless execution, eth1 EE
1 Like
15
  1. Guillaume Ballet
  2. Go-ethereum dev, ewasm
  3. Areas:
    3.1 State management features
    3.2 Using WASM to increase feature adoption speed
1 Like
16
  1. Casey Detrio
  2. Ewasm
  3. Cross-chain (eth1 <-> eth2) interop / integration
17
  1. Tim Beiko (@timbeiko on twitter/telegram/etc.)
  2. Product Manager on Hyperledger Besu, an Eth1 client
  3. Specific areas of research you are interested in:
    3.1 ETH 1.0 sustainability (state growth issues, statelessness, etc.)
    3.2 ETH 1 -> ETH 2 transition
18
  1. Trent Van Epps (trent_vanepps on twitter)
  2. Working at Whiteblock on community and product marketing.
  3. node incentivisation, making nodes easier to run, stateless paradigm, the whole 1x effort and the transition to eth2 as well
1 Like
19
  1. Stefaan Ponnet ( @sponnet on twitter / github / telegram / … )
  2. Product development at AVADO (ava.do) - pre-installed blockchain node hardware
  3. areas of interest:
    3.1 point-and-click solution (a.k.a. a wizard) to set up and maintain a residential ETH1.x node
    3.2 create incentives for running hardware at home - making running a node easier
20

Hopefully not too late to the party here.

  1. Diederik Loerakker (@protolambda)
  2. Eth 2.0 researcher, bridging between implementation/phase0 things, and then some light-client/ssz/related things. Python/Go all day.
  3. Everything related to eth2 encoding/merkle proofs, stateless clients, and eth2 spec <> eth2 client support.
21
  1. Wil Barnes
  2. Multi-Collateral Dai
  3. Stateless Ethereum, Eth2 transition
22
  1. Brian McMichael
  2. Smart Contracts @ MakerDAO
  3. Unstoppable code. Stakeholder incentives.
23
  1. Paweł Bylica
  2. C++ / Aleth / EVM / Ewasm / EVMC
  3. EVM and execution engines, testing, fuzzing, APIs
1 Like
24
  1. Wei Tang
  2. Parity Ethereum dev
  3. Backward compatibility, EVM optimizations