-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for other libp2p implementations #70
Comments
Would you mind opening PR? |
Oops, seems like we needed more information for this issue, please comment with more details or this issue will be closed in 7 days. |
In a triage meeting with @achingbrain, we discussed this would be a great self contained project to do. Something like a lighter version of testground. Next steps are to get buy in from other implementers (rust, etc) to start this. The go-libp2p interop works because the go-libp2p-daemon exposes an RPC port to orchestrate. |
Additional notes from that triage meeting: As a sort of "Testground Lite", this would certainly be useful. This can be resolved with a form of smoke testing: "Can I just dial a rust-libp2p node and send one packet?" (does not need to be millions of packets)
|
This will be addressed as a part of libp2p/test-plans#61 |
It would be useful to catch interop bugs earlier on other implementations:
The text was updated successfully, but these errors were encountered: