The ENR can also be populated with arbitrary data organized as key-value pairs. The ENR contains a signature, sequence number and fields detailing the identity scheme used to generate and validate signatures. These are especially useful because they allow greater informational exchange between nodes. In the following example, the node URL describes a node with IP address 10.3.58.6, TCP port 30303 and UDP discovery port Ethereum Node Records (ENRs)Įthereum Node Records (ENRs) are a standardized format for network addresses on Ethereum. If the TCP and UDP (discovery) ports differ, the UDP port is specified as a query parameter 'discport' The port in the hostname section is the TCP listening port. The hostname can only be given as an IP address DNS names are not allowed. The hexadecimal node-ID is encoded in the username portion of the URL separated from the host using an sign.

ip4/192.168.22.27/tcp/33000/p2p/5t7Nv7dG2d6ffbvAiewVsEwWweU3LdebSqX2y1bPrW8br EnodeĪn enode is a way to identify an Ethereum node using a URL address format. For example, the multiaddr for a node with IPv4 address 192.168.22.27 listening to TCP port 33000 looks like:įor an Ethereum node, the multiaddr contains the node-ID (a hash of their public key): Addresses are represented as key-value pairs with keys and values separated with a forward slash. Multiaddr is a universal format designed for peer-to-peer networks. The original Ethereum node address format was the 'multiaddr' (short for 'multi-addresses'). Some understanding of Ethereum's networking layer is required to understand this page. ENRs are the current standard for Ethereum network addresses. To ensure any potential peer can interpret this information, it is relayed in one of three standardized formats that any Ethereum node can understand: multiaddr, enode, or Ethereum Node Records (ENRs).

Ethereum nodes have to identify themselves with some basic information to connect to peers.

Ethereum public key from address