-
Notifications
You must be signed in to change notification settings - Fork 0
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 multiaddrs
key for websocket dns peer info
#1
base: master
Are you sure you want to change the base?
Conversation
multiaddr
key for websocket dns peer info
I explored the possibility of encoding several multiaddresses in the This resulted in RLP encoded size of Removing the peer id from the encoded multiaddr does allow the encoding of 2, even 3 (not 4) multiaddresses while remaining under 300 bytes post RLP encoding. |
multiaddr
key for websocket dns peer infomultiaddrs
key for websocket dns peer info
This can be used to store peer information that cannot be encoded with the pre-defined ENR keys such as websocket details, fqdn, etc. Multiaddresses present in the `multiaddrs` field must not contain a peer id. The `secp256k1` field should be used for the peer id by storing the public key.
Imported from D4nte/discv5#1 Replaced bcrypto backend with secp256k1.
Imported from D4nte/discv5#1 Replaced bcrypto backend with secp256k1.
Imported from D4nte/discv5#1 Replaced bcrypto backend with secp256k1.
Imported from D4nte/discv5#1 Replaced bcrypto backend with secp256k1.
No description provided.