Interoperability between zig-libp2p and py-libp2p focused on ping protocol

[seetadev]

🔄 Zig ↔ Py libp2p Interoperability: /ipfs/ping/1.0.0

This project aims to establish seamless interoperability between zig-libp2p and py-libp2p, starting with the canonical /ipfs/ping/1.0.0 protocol.

We treat ping as the minimal working example to ensure multi-language libp2p compatibility and set the foundation for deeper protocol testing (e.g., hole punching, identify, relay).

🎯 Goal

Enable a py-libp2p node to dial a zig-libp2p node and successfully:

• Open a stream to /ipfs/ping/1.0.0
• Send a 32-byte payload
• Receive an exact echo of the same 32 bytes

🛠️ Tech Stack

Component	Technology
Zig node	zig-libp2p
Python node	py-libp2p
Transport	TCP (initially)
Protocol	/ipfs/ping/1.0.0
Message format	Raw 32-byte echo

✅ Phase 0: Setup & Verification

[ ] Zig

• Implement or verify /ipfs/ping/1.0.0 listener.
• Echo back any 32-byte payload on the stream.
• Print connection events and payloads for debugging.

[ ] Python

• Create a minimal py-libp2p node using TCP transport.
• Dial the Zig node using its multiaddr.
• Send a 32-byte payload and await response.
• Log latency and compare response for correctness.

🔍 Phase 1: Interop Tests

📦 Test Suite

Create a simple interop/ test folder with:

• zig_node.zig — runs the ping server
• py_ping_test.py — dials and verifies ping
• test.sh — launches both nodes and runs test

✅ Interop Success Criteria

• Python connects to Zig peer
• Stream to /ipfs/ping/1.0.0 opens successfully
• Payload is echoed back without modification
• Round-trip latency < 100ms on localhost

🚧 Phase 2: Optional Enhancements

• Implement timeouts and retries
• Add CLI flags for dynamic port/multiaddr configs
• Visualize ping RTTs in real-time using a simple plot
• Create a GitHub Action that runs interop test on every PR

📦 Future Work

After ping is stabilized:

• Implement /libp2p/identify/1.0.0 for peer metadata sync
• Interop test for /libp2p/dcutr + relays (hole punching)
• Add NAT + relay support for testing across networks

[GrapeBaBa]

I want to make sure for this test we don't need protocol negotiation, security, muxer and only a ping protocol on tcp transport, right?

[seetadev]

@GrapeBaBa : ping protocol on tcp transport is a good start. We will later use protocol negotiation, security, muxer when we do hole punching interop and transport interop.