go-ethereum

Commit Graph

Author	SHA1	Message	Date
Guillaume Ballet	0183256e7f	all: fix warning flagging the use of DeepEqual on error (#23624 ) * core: fix warning flagging the use of DeepEqual on error * apply the same change everywhere possible * revert change that was committed by mistake * fix build error * Update config.go * revert changes to ConfigCompatError * review feedback Co-authored-by: Felix Lange <fjl@twurst.com>	3 years ago
Péter Szilágyi	6ef3a16869	p2p/enode: use unix timestamp as base ENR sequence number (#19903 ) This PR ensures that wiping all data associated with a node (apart from its nodekey) will not generate already used sequence number for the ENRs, since all remote nodes would reject them until they out-number the previously published largest one. The big complication with this scheme is that every local update to the ENR can potentially bump the sequence number by one. In order to ensure that local updates do not outrun the clock, the sequence number is a millisecond-precision timestamp, and updates are throttled to occur at most once per millisecond. Co-authored-by: Felix Lange <fjl@twurst.com>	3 years ago
Felix Lange	524aaf5ec6	p2p/discover: implement v5.1 wire protocol (#21647 ) This change implements the Discovery v5.1 wire protocol and also adds an interactive test suite for this protocol.	4 years ago

Author

SHA1

Message

Date

Guillaume Ballet

0183256e7f

all: fix warning flagging the use of DeepEqual on error (#23624 )

* core: fix warning flagging the use of DeepEqual on error

* apply the same change everywhere possible

* revert change that was committed by mistake

* fix build error

* Update config.go

* revert changes to ConfigCompatError

* review feedback

Co-authored-by: Felix Lange <fjl@twurst.com>

3 years ago

Péter Szilágyi

6ef3a16869

p2p/enode: use unix timestamp as base ENR sequence number (#19903 )

This PR ensures that wiping all data associated with a node (apart from its nodekey)
will not generate already used sequence number for the ENRs, since all remote nodes
would reject them until they out-number the previously published largest one.

The big complication with this scheme is that every local update to the ENR can
potentially bump the sequence number by one. In order to ensure that local updates
do not outrun the clock, the sequence number is a millisecond-precision timestamp,
and updates are throttled to occur at most once per millisecond.

Co-authored-by: Felix Lange <fjl@twurst.com>

3 years ago

Felix Lange

524aaf5ec6

p2p/discover: implement v5.1 wire protocol (#21647 )

This change implements the Discovery v5.1 wire protocol and
also adds an interactive test suite for this protocol.

4 years ago

3 Commits (20356e57b119b4e70ce47665a71964434e15200d)