2020-07-09 Eth2 Call 44

2020-07-09 Eth2 Call 44.txt

Agenda: https://github.com/ethereum/eth2.0-pm/issues/169

Nimbus

Audit:
- Consensys Diligence
- Trail of Bits
- NCC

3 phases, 2 weeks audit, 2 or 3 weeks fixes.
- Networking
- Beacon Core
- Validator Core

=> Fresh take on audits, similar to Eth2, have multiple auditors in collaboration
=> Fixing issues as they are raised

Beacon core:
- Reducing memory usage (smarter caching), below Lighthouse
- Sync speed, not satisfactory yet

Networking:
- Attestation not properly propagated (biggest issue on Altona)
- several improvement like better handling stale connections
- Discv5 fixes

Beacon/Validator split:
- Fix finalisation issues

Crypto:
- Key management EIP2333
-> Wallet implies to hold withdrawal keys
-> deposits compatible to the Ethereum Launchpad
- Reviewed BLS backends
	- Updated to Milagro to use Miracle/core following license change
	- BLST wrapped

Doc: blog post on “the case for running your own validator”, https://our.status.im/case-for-running-your-own-validator/

———————

Testing release updates

Update rumor into a tester

Unpublished attester slashing tests
Some found in fuzzing, for example Nimbus

———————

Attacknets

———————

Testnets

Client metrics: https://ethresear.ch/t/ethereum-2-0-client-metrics-07-2020/7699
Next: public launch v0.12.2
Specs on goerli
Sunday 1PM UTC?

TODO: track slashing events to fix bugs
https://github.com/goerli/medalla

———————

Lodestar

Finished with Gossipsub
Need more tests to update with Go implementation
All hands on deck for new testnet

Prysm

Remote signing
Key management (was weakest)
Fuzz, Clusterfuzz, found bugs
Networking improvement

Teku

Work on memory usage
…
Almost complete BLST library integration
Increase sync speed by 3 times
Teku RFP is out, for 3rd of August

Trinity

Goal: Altona’s head
Fork choice refactor
Speeding things up
Sync speed 0.2 slots/sec
Right now 13 slots/sec

Lighthouse

New team member: Benedikt/Black Templar
Stability improvement
Key management system improvement
Fixing attestation inclusion bugs
Panic in discv5
Security hardening of networking infra
Setting up internal testate to prepare for multi testnet

——————

Research updates

Joseph: Everybody should put some resources to attacking the attacknets

Leo: Snappy compression ratio and blocks/s speed with snappy
https://docs.google.com/spreadsheets/d/1SoXvmPfm1BRVcdDm7CuwaWDjxp5a3NzGMBLViQjBNqA/edit?usp=sharing

Will run different clients on the same network
https://altona.beaconcha.in/validator/a2b60b956869fd5dfe9874546b3cc4bc2ca42bcc3b9c48c8473b7881c4e94b4a57917b07bf0b22117c90daf2f59c2dde#overview

——————

Networking

New specs is mostly some updates on gossips param
More gossipsub changes will be introduced later
Verification, sequence numbers will be standardised (currently some propagated, dropped or randomized depending on the client)

——————

Vitalik: how to kickstart phase 1 implementation?
Danny: currently clients focused on shipping
V: slower clients may make sense to start working on phase 1
Terence: Annotated phase 1 spec?
Joseph: Working on phase 1 client, transpiring the spec

——————
Closing
Next call probably 2days after testnet launch launch