Eth2 Networking Call 5

[djrtwo]

Call 4

Meeting Date/Time:

Meeting Date/Time: Wednesday 2020/9/9 at 13:00 GMT

Meeting Duration:

1.25 hours

Agenda

1. Opening
2. Seqno/Sig/Key omit plan for gossipsub
3. gossipsub v1.1 param progress
4. Migrate gossip message-id to not use Base64
5. discv5.1
6. Updates
7. Open discussion
8. Closing remarks and plans for next call or other organizational items

[protolambda]

I'd like to discuss various concerns with the Seqno/Sig/Key omit plan for gossipsub messages, and new related things that came up. See ethereum/consensus-specs#1981 (comment)

• Progress/plans of clients updating to omit intentionally unused fields
• Enforce omitting the fields Yes/No
• What if these are not in the protobuf definition to begin with? These are optional. Does each implementation have support for them?
• How unrecognized fields are handled. In Go they are kept around, and encoded back as necessary. If that works, it may be used by malicious actor to add tracking info (add some kind of ID as an unrecognized protobuf key-value entry: ignored, but passed along).

[AgeManning]

Also lets add this to the agenda: ethereum/consensus-specs#2039

[mkalinin]

We’d like to discuss discv5 DoS vectors and 5.0 vs 5.1 version, cc @jrhea

[richshalabh]

Need to know 2.0 implementation and medalla deploy on mainnet. . GAS FEE ? BLOCK SIZE ? TPS ?