# IPFS 0.5 Content Routing Improvements: Deep Dive

**URL:** <https://discuss.ipfs.tech/t/ipfs-0-5-content-routing-improvements-deep-dive/8712>\
**Category:** Blog Posts\
**Created:** [July 20, 2020, 1:48pm UTC](https://discuss.ipfs.tech/t/ipfs-0-5-content-routing-improvements-deep-dive/8712 "2020-07-20T13:48:43Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex020/uploads/ipfs1/original/1X/035cb0e41547e8c019cdfd4466a4736c843af1c9.png) [@system](https://discuss.ipfs.tech/u/system)\
**Post date:** [July 20, 2020, 1:48pm UTC](https://discuss.ipfs.tech/t/ipfs-0-5-content-routing-improvements-deep-dive/8712/1 "2020-07-20T13:48:43Z")

</div>

by Adin Schmahmann on 2020-07-20

At the end of April, we released our largest update to go-ipfs to date: [IPFS 0.5](https://blog.ipfs.io/2020-04-28-go-ipfs-0-5-0/). While there have been many improvements, the changes to IPFS’s Distributed Hash Table (DHT) were especially critical to improving the performance and stability of finding data in IPFS. For some background on how we arrived at the most recent set of DHT changes, take a look at [The Road to the New DHT](https://blog.ipfs.io/2020-05-19-road-to-dht/), or try them out yourself in the [latest version of go-ipfs](https://dist.ipfs.io/#go-ipfs).

* * *
This is a companion discussion topic for the original entry at [https://blog.ipfs.io/2020-07-20-dht-deep-dive](https://blog.ipfs.io/2020-07-20-dht-deep-dive)

---

<div class="post-metadata">

**Author:** ![hali](https://avatars.discourse-cdn.com/v4/letter/h/aeb1de/32.png) [@hali](https://discuss.ipfs.tech/u/hali)\
**Post date:** [April 11, 2021, 1:56am UTC](https://discuss.ipfs.tech/t/ipfs-0-5-content-routing-improvements-deep-dive/8712/2 "2021-04-11T01:56:58Z")

</div>

> [@system](#):
>
> The peer adds all new providers it has learned about and continues until the lookup terminates. Depending on which API is used, the lookup can also be forced to abort after receiving a certain number of provider records.

What happened if someone announces a sea of invalid provider records?

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex020/uploads/ipfs1/original/1X/035cb0e41547e8c019cdfd4466a4736c843af1c9.png) [@system](https://discuss.ipfs.tech/u/system)\
**Post date:** [April 11, 2021, 1:56am UTC](https://discuss.ipfs.tech/t/ipfs-0-5-content-routing-improvements-deep-dive/8712/3 "2021-04-11T01:56:58Z")

</div>


