Skip to content

Discovery findnode should have hash-sized target#25

Closed
fjl wants to merge 1 commit into
ethereum:masterfrom
fjl:patch-1
Closed

Discovery findnode should have hash-sized target#25
fjl wants to merge 1 commit into
ethereum:masterfrom
fjl:patch-1

Conversation

@fjl
Copy link
Copy Markdown
Collaborator

@fjl fjl commented May 5, 2015

This is mostly a performance concern. With a hash-sized target, it does not need to be hashed by the recipient in order to compute the closest nodes.

The other reason why this might be a good change is that calling it a NodeID is wrong in general.
The lookup target is arbitrary and does not need to be a valid EC public key. We could leave it at 64
bytes, but it then needs to be hashed anyway in order to fit into the distance metric.

@subtly
Copy link
Copy Markdown
Member

subtly commented May 5, 2015

Deferred until after Frontier. It's also moot because, as previously discussed, the target is to be removed and replaced with a pre-calculated integer distance value. We are using this to find random nodes which are only nearby, so an exact target isn't required.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants