-
Notifications
You must be signed in to change notification settings - Fork 64
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
Add /webrtc and /certhash #261
Comments
@John-LittleBearLabs Can I move this to Ready, In Progress, or In Review? I think I saw you post on slack about a PR for this. |
@ddimaria But perhaps "In Progress" isn't unreasonable. |
For use with the js implementation of the webrtc transport The most relevant point of info, from [the draft spec](https://github.com/libp2p/specs/blob/4b8e890c49061eb62c9d16a9afd3aa0a738e6285/webrtc/README.md#addressing): > The TLS certificate fingerprint in /certhash is a [multibase](https://github.com/multiformats/multibase) encoded [multihash](https://github.com/multiformats/multihash).
Analagous to the rust implementation:
https://github.com/multiformats/rust-multiaddr/pull/59/files#diff-d8c31d407e43532e4152070bdaf92d7fff58c81b39b4308cad7c769519d31376
And to the go implementation:
https://github.com/multiformats/go-multiaddr/pull/179/files
The goal is to be able to examine and use multiaddrs with these protocols in browserland, too.
Will be useful to the js/ts implementation of the transport.
For reference:
libp2p/specs#412
The text was updated successfully, but these errors were encountered: