Felix Lange 2adcc31bb4 p2p/discover: new distance metric based on sha3(id) ...

The previous metric was pubkey1^pubkey2, as specified in the Kademlia
paper. We missed that EC public keys are not uniformly distributed.
Using the hash of the public keys addresses that. It also makes it
a bit harder to generate node IDs that are close to a particular node.

2015-05-06 16:10:41 +02:00

..

database_test.go

p2p/discover: track sha3(ID) in Node

2015-04-30 15:02:23 +02:00

database.go

p2p/discover: track sha3(ID) in Node

2015-04-30 15:02:23 +02:00

node_test.go

p2p/discover: new distance metric based on sha3(id)

2015-05-06 16:10:41 +02:00

node.go

p2p/discover: new distance metric based on sha3(id)

2015-05-06 16:10:41 +02:00

table_test.go

p2p/discover: new distance metric based on sha3(id)

2015-05-06 16:10:41 +02:00

table.go

p2p/discover: new distance metric based on sha3(id)

2015-05-06 16:10:41 +02:00

udp_test.go

p2p/discover: new distance metric based on sha3(id)

2015-05-06 16:10:41 +02:00

udp.go

p2p/discover: new distance metric based on sha3(id)

2015-05-06 16:10:41 +02:00