P2P Networking #008

Sergi added read.ai meeting notes to the meeting. Read provides AI generated meeting summaries to make meetings more effective and efficient. View our Privacy Policy at https://www.read.ai/pp Type "read stop" to disable, or "opt out" to delete meeting data.

Read isn't recording yet. The Zoom host needs to grant recording permission in the meeting dialog.

https://github.com/OffchainLabs/prysm/pull/17348

https://hackmd.io/@aarshshah/rkZTUeVdGe

https://github.com/OffchainLabs/prysm/pull/17410

great work Aarsh!

Reacted to "great work Aarsh!" with ❤️

Thanks Raul !

Read wasn't granted recording permission, so no part of this meeting was recorded. Read is now leaving.

this is how ethp2p broadcast works btw

https://github.com/OffchainLabs/prysm/pull/17348

Also curious to see waggle branch once it is public🙂

I'd be really happy to discuss and help with a waggle impl for this once i made more progress with batched attestations :)

Reacted to "I'd be really happy to discuss and help with a waggle impl for this once i made more progress with batched attestations :)" with 🔥

@Csaba did you try visualizing this in https://netviz.ethp2p.dev/ ?

if not i can help with that

Csaba, i've thought a lot about exactly these points when designing ethp2p broadcast, and a lot of what you've presented is already implemented. in fact, you can easily plug in a noop Encoder/Decoder to simply chunk without EC. how can we align going forward?

Would be happy to learn more about both :)

What is the current roadmap atm? Waggle? Ethp2p? is there any clear direction?

We are also interested on ethp2p (Lambdaclass)

Replying to "@Csaba did you try v..." Not yet. But I should try :-)

Replying to "@Csaba did you try v..." this was made with claude 4.6 😄 maybe i should clean it up

Replying to "Csaba, i've thought ..." Just to be clear, I also think we want EC, but I can sacrifice it if that’s a blocker for Hegota

Replying to "@Csaba did you try v..." but the trace schema is stack agnostic you can create decoder that maps the trace to the visual language (and agents are great at that)

i would like to think that Hegotá, being over 15mo out, can adopt ethp2p broadcast

the risk is also extremely contained (and i'll explain why next)

but there was no EIP submitted before the deadline (i missed it because i was looking at an old post 🙁)

Replying to "the risk is also ext..." I agree, fully. It is the “if others think that’s too much” part :-)

that said, there's a world in which it is non-breaking for consensus (therefore technically no EIP needed)

tbd honestly i'm not super plugged into Eth politics and red tape these days

i have a quick presentation too on some ethp2p stuff

We have a WIP implementation in Rust: https://github.com/lambdaclass/ethp2p-rs

Reacted to "We have a WIP implementation in Rust: https://github.com/lambdaclass/ethp2p-rs" with 👀

I have to leave on time today. Thanks for the presentations everyone!

This is the stream equivalent of what we do for discv4/discv5 dispatch at the datagram level … streams definitely sound more complex ;-)

Apologies, I have to head out too, thanks everyone!

I think we could evaluate one-by-one where breaking the existing API is worthwhile.

Can’t we just upgrade libp2p to what ethp2p provides? I.e. unidirectional streams, what else?

Replying to "Can’t we just upgrad..." I guess also datagram streams?

Replying to "Can’t we just upg..." there's a PR for it: https://github.com/libp2p/specs/pull/680

Reacted to "there's a PR for it: https://github.com/libp2p/specs/pull/680" with 👍

https://github.com/ethp2p/ethp2p