Update enr.md

This commit is contained in:
Jimmy Debe 2024-02-14 19:00:49 -05:00 committed by GitHub
parent b8e66d8145
commit de6f3f2d66
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 6 additions and 6 deletions

View File

@ -8,7 +8,7 @@ contributors:
## Abstract
This RFC describes the usage of the ENR (Ethereum Node Records) format for [10/WAKU2](/specs/10) purposes.
This RFC describes the usage of the ENR (Ethereum Node Records) format for [10/WAKU2](https://rfc.vac.dev/spec/10/) 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.
@ -40,7 +40,7 @@ Would carry some ambiguity: Is the certificate securing the websocket port valid
the ipv4 address?
the ipv6 address?
The [10/WAKU2](/specs/10) protocol family is built on the [libp2p](https://github.com/libp2p/specs) protocol stack.
The [10/WAKU2](https://rfc.vac.dev/spec/10/) 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:
@ -157,7 +157,7 @@ Copyright and related rights waived via [CC0](https://creativecommons.org/public
## References
- [1] https://github.com/status-im/nim-waku/pull/690
- [2] https://github.com/vacp2p/rfc/issues/462#issuecomment-943869940
- [3] https://eips.ethereum.org/EIPS/eip-778
- [4] https://github.com/ethereum/devp2p/blob/master/discv5/discv5.md
- [1](https://github.com/status-im/nim-waku/pull/690)
- [2](https://github.com/vacp2p/rfc/issues/462#issuecomment-943869940)
- [3](https://eips.ethereum.org/EIPS/eip-778)
- [4](https://github.com/ethereum/devp2p/blob/master/discv5/discv5.md)