Update enr.md

This commit is contained in:
Jimmy Debe 2024-07-09 06:29:40 -04:00 committed by GitHub
parent b21a743147
commit 4bc0f0d2bb
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194

View File

@ -8,7 +8,7 @@ contributors:
## Abstract
This RFC describes the usage of the ENR (Ethereum Node Records) format for [10/WAKU2](https://rfc.vac.dev/waku/standards/core/10/waku2) purposes.
This RFC describes the usage of the ENR (Ethereum Node Records) format for [10/WAKU2](https://github.com/vacp2p/rfc-index/blob/main/waku/standards/core/10/waku2.md) purposes.
The ENR format is defined in [EIP-778](https://eips.ethereum.org/EIPS/eip-778) [[3]](#references).
This RFC is an extension of EIP-778, ENR used in Waku v2 MUST adhere to both EIP-778 and 31/WAKU2-ENR.
@ -41,7 +41,7 @@ Would carry some ambiguity: Is the certificate securing the websocket port valid
the ipv4 address?
the ipv6 address?
The [10/WAKU2](https://rfc.vac.dev/waku/standards/core/10/waku2) protocol family is built on the [libp2p](https://github.com/libp2p/specs) protocol stack.
The [10/WAKU2](https://github.com/vacp2p/rfc-index/blob/main/waku/standards/core/10/waku2.md) protocol family is built on the [libp2p](https://github.com/libp2p/specs) protocol stack.
Hence, it uses [multiaddr](https://github.com/multiformats/multiaddr) to format network addresses.
Directly storing one or several multiaddresses in the ENR would fix the issues listed above:
@ -162,7 +162,7 @@ Copyright and related rights waived via [CC0](https://creativecommons.org/public
## References
- [1](https://rfc.vac.dev/waku/standards/core/10/waku2)
- [1](https://github.com/vacp2p/rfc-index/blob/main/waku/standards/core/10/waku2.md)
- [2](https://github.com/status-im/nim-waku/pull/690)
- [3](https://github.com/vacp2p/rfc/issues/462#issuecomment-943869940)
- [4](https://eips.ethereum.org/EIPS/eip-778)