go-ethereum

Official Go implementation of the Ethereum protocol

History

Felix Lange b8040a430e cmd/utils: use eth DNS tree for snap discovery (#22808 ) This removes auto-configuration of the snap..ethdisco.net DNS discovery tree. Since measurements have shown that > 75% of nodes in all..ethdisco.net support snap, we have decided to retire the dedicated index for snap and just use the eth tree instead. The dial iterators of eth and snap now use the same DNS tree in the default configuration, so both iterators should use the same DNS discovery client instance. This ensures that the record cache and rate limit are shared. Records will not be requested multiple times. While testing the change, I noticed that duplicate DNS requests do happen even when the client instance is shared. This is because the two iterators request the tree root, link tree root, and first levels of the tree in lockstep. To avoid this problem, the change also adds a singleflight.Group instance in the client. When one iterator attempts to resolve an entry which is already being resolved, the singleflight object waits for the existing resolve call to finish and returns the entry to both places.		4 years ago
..
discovery.go	core, eth: split eth package, implement snap protocol (#21482 )	4 years ago
handler.go	cmd/utils: use eth DNS tree for snap discovery (#22808 )	4 years ago
peer.go	eth/protocols, prp/tracker: add support for req/rep rtt tracking (#22608 )	4 years ago
protocol.go	eth: fix snap sync cancellation	4 years ago
range.go	eth/protocols/snap: generate storage trie from full dirty snap data (#22668 )	4 years ago
range_test.go	eth/protocols/snap: generate storage trie from full dirty snap data (#22668 )	4 years ago
sync.go	eth/protocols/snap: use storage batch, not account batch in st task	4 years ago
sync_test.go	eth/protocols/snap: generate storage trie from full dirty snap data (#22668 )	4 years ago
tracker.go	eth/protocols, prp/tracker: add support for req/rep rtt tracking (#22608 )	4 years ago