Skip to content

EIP-778: simplify ENR for v4 compatibility #1049

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.

Sign up for GitHub

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

Merged
Arachnid merged 1 commit into from
May 2, 2018
Merged

EIP-778: simplify ENR for v4 compatibility #1049

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
41 changes: 20 additions & 21 deletions EIPS/eip-778.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -61,26 +61,25 @@ Records are signed and encoded as follows:
The keys in key/value pairs can technically be any byte sequence, but ASCII text is
preferred. The following keys are pre-defined:

| Key | Value |
|:-------------|:-------------------------------------------------|
| `id` | name of identity scheme, e.g. "secp256k1-keccak" |
| `secp256k1` | compressed secp256k1 public key, 33 bytes |
| `ip4` | IPv4 address, 4 bytes |
| `ip6` | IPv6 address, 16 bytes |
| `discv5` | UDP port for discovery v5 |

### secp256k1-keccak Identity Scheme

This specification defines a single scheme to be used as the default: "secp256k1-keccak".

- To sign record `content` with this scheme, apply the keccak256[^1] hash function to
`content`, then create a signature of the hash. The resulting 64-byte signature is
encoded as the concatenation of the `r` and `s` signature values.
| Key | Value |
|:------------|:------------------------------------------|
| `id` | name of identity scheme, e.g. "v4" |
| `secp256k1` | compressed secp256k1 public key, 33 bytes |
| `ip` | IP address, 4 or 16 bytes |
| `tcp` | TCP port |
| `udp` | UDP port |

### "v4" Identity Scheme

This specification defines a single scheme to be used as the default. The "v4" scheme is
backwards-compatible with the cryptosystem used by Node Discovery Protocol v4.

- To sign record `content` with this scheme, apply the keccak256 hash function (as used by
the EVM) to `content`, then create a signature of the hash. The resulting 64-byte
signature is encoded as the concatenation of the `r` and `s` signature values.
- To verify a record, check that the signature was made by the public key in the
"secp256k1" key/value pair.
- To derive a node address, take the keccak256 hash of the public key.

[^1]: As used by the EVM
- To derive a node address, take the keccak256 hash of the uncompressed public key.

# Rationale

Expand All @@ -94,9 +93,9 @@ The format is meant to suit future needs in two ways:
get it implemented. The scheme can be used as soon as most clients accept it.

The size of a record is limited because records are relayed frequently and may be included
in size-constrained protocols such as DNS. A record containing IPv4 address, when signed
using the "secp256k1-keccak" scheme occupies roughly 120 bytes, leaving plenty of room for
additional metadata.
in size-constrained protocols such as DNS. A record containing a IPv4 address, when signed
using the "v4" scheme occupies roughly 120 bytes, leaving plenty of room for additional
metadata.

# Copyright

Expand Down