Decode and use waku2 key in ENRs.
#405
Assignees
Comments
D4nte
changed the title
waku key in ENRs.waku2 key in ENRs.
status-bors-ng bot
added a commit
that referenced
this issue
Mar 24, 2022
620: Implementing RFC 31/WAKU2-ENR (Part 1) r=jemboh a=jemboh ## Problem As per the [spec](https://rfc.vac.dev/spec/31/#waku2-enr-key), adding the capabilities (E.g. relay, store, filter, lightpush) of a node to the DNS discovery mechanism. ## Solution Added the ability to get/set `waku2` field on the enr. The `waku2` field needs to be encoded/decoded (`Waku2` object <-> `Uint8Array`) so added a _codec_ to do so. ## Notes - Related to #405 Co-authored-by: jemboh <[email protected]>
|
Done with #632 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Problem
The
waku2key was added to Waku's ENR: https://rfc.vac.dev/spec/31/ to convey the capabilities of a node (Relay, Store, etc).This is currently not used in the DNS Discovery implementation. Meaning that we hope for the best that the node we connect to has the capabilities we need
DoD
waku2field inENR.{ store: true, relay: true, lightPush: false, filter: false }enrtree.tsto retrieve nodes with specific capabilities:DnsNodeDiscovery.getPeersto take in account capabilities when walking the tree: https://github.com/status-im/js-waku/blob/279837677627732d4249c275e6673aa12ac2e765/src/lib/discovery/dns.ts#L46The text was updated successfully, but these errors were encountered: