libp2p Weekly 2025-05-27

[p-shahi]

Previous occurrence: #3140

Discussion items

1. Evaluate @roamhq/wrtc #3034 @luu-alex - Can't make changes directly to libp2p. @achingbrain suggests to open issue into roamhq to support SDP muxing on listen port & disable fingerprint verification.
2. @seetadev - js-libp2p interop testing; is there a place to learn where document is setup for js-libp2p? - answered
3. Update on introspection from last week: Electron app demo of the introspection module (https://github.com/ipshipyard/js-libp2p-inspector) from @achingbrain

4. @dozyio Discussion about https://github.com//pull/3040 a. What to do about having two registrars? middleware to accept connection handler and wrap and pass it on. middleware handlers would need to have a deep understanding of what's sent over streams. 5. @seetadev update on https://github.com/libp2p/js-libp2p-examples/pull/227 and https://github.com/libp2p/rust-libp2p/issues/6029 6. Discussion on https://github.com//pull/3091

Workstreams Updates

7. @seetadev rust-libp2p and js-libp2p WebRTC interop, @acul71 identify and ping interop between js-libp2p and py-libp2p
   a. Interoperability between js-libp2p and py-libp2p focused on ping protocol py-libp2p#584
   b. feat: add identify protocol example js-libp2p-examples#222

Up next

1. Continue with KAD DHT spec compliance
2. Investigate memory leak

Community PR Review

1. fix: skip perf multiselect negotiation #3091
2. feat(Ed25519-Key): Improve validation speeds in browsers #3100

Other

1. Any callouts/travel/need help

[p-shahi]

Attendees: @seetadev @dhuseby @acul71 @0-th @leny62 @dozyio @achingbrain @luu-alex @p-shahi