Huge thanks to @Ethereum_JP organizers, @adust09, our haskell-@libp2p maintainer, for coordinating the @libp2p workshop on "When AI Finds the Bug: Securing Blockchain Infrastructure Beyond Smart Contracts" at @Ethereum_JP. We also wish to thank our wonderful participants, contributors.
1
4
10
127
We appreciate the response and contribution from our friends from @Ethereum_JP, @ethereumfndn and developers participating at @ETHGlobal hackathon at Tokyo in the @libp2p ecosystem. We also wish to thank @adust09 for enabling us to bring the @libp2p community together at @Ethereum_JP for a workshop on building, testing & securing P2P networks.
1
5
10
230
From protocol design to real-world #interoperability, the workshop started with a discussion on how @libp2p powers open, #permissionless #networks. Finding a suspicious edge case is only the beginning. Can it be reproduced? Is it reachable? What state is required to trigger it? 🔍 We walked through @libp2p security testing: hypothesis → reproduction harness → expert validation → impact assessment → remediation via a case study presentation and a workshop. Special thanks to @adust09 and @Ethereum_JP organizers for their support during the presentation and the workshop.

Sep 25, 2026 · 11:32 PM UTC

1
5
6
64
Sort replies: Relevant Recent Liked
A key lesson: AI can help discover vulnerability hypotheses, but human judgment is essential to establish ground truth & reachability. We explored edge cases: crafted network messages, boundary conditions, timing arithmetic, peer state & paths. “Don’t trust, verify.” We explored testing, interoperability & observability as foundations for dependable P2P infrastructure.
1
4
9
62
Security research also needs responsible disclosure. Vulnerabilities should be shared privately with the @libp2p security team before release. 🔒 A case study on enabling pathways for safe remediation was discussed with focus on the vital steps: patch the issue, preserve protocol behavior, test timing integrity & verify across @libp2p implementations. 🔧 We also walked through the CVE workflow: validation → impact analysis → coordinated disclosure → patch → release tagging → operator guidance.
1
4
6
90