Releases: libp2p/go-libp2p-kad-dht
Releases · libp2p/go-libp2p-kad-dht
v0.11.1
v0.11.0
v0.10.0
- Removed the
/kad/2.0.0protocol ID as it's not being used currently and we'd like to avoid potential confusion. It can be re-added once we have a protocol breaking DHT change (similarly removed the V1CompatMode option since everything is only v1) - Added a V1ProtocolOverride function to be used by existing networks that do not have protocol IDs of the form
/app/kad/1.0.0new networks SHOULD NOT use this function.- As DHT protocol versions are bumped in the future expect that we will not be adding override functions and that protocol IDs will look like
/app/kad/2.0.0
- As DHT protocol versions are bumped in the future expect that we will not be adding override functions and that protocol IDs will look like
v0.9.0
- Reduced routing table churn #668
- We now lock peers into the routing table once they enter the routing table unless they are:
- Found in the early bootstrapping stages (in which case they are added on a probationary basis)
- They fail to respond to a query from us (in which case they are evicted)
- We now lock peers into the routing table once they enter the routing table unless they are:
- Added peer diversity to the routing table #658
- Allows us to restrict the routing table to only hold a limited number of peers with particular network attributes (e.g. IP address range, or ASN)
- Allow passing custom dual-dht options #671, #688
- Fixed key log encoding, now outputs keys in base32 encoded multibase #682
- Updated dependencies #689
v0.8.3
v0.8.1
v0.8.0
- Changes the
BootstrapPeersoption to takepeer.AddrInfostructs instead of multiaddrs. This makes it easy to pass multiple addresses for each peer. - Alters connection manager tagging such that:
- Useful peers in low buckets are "protected". These are the most useful peers to us as they're the ones we usually contact when starting DHT queries.
- Useful peers in higher buckets are given higher weights.