# IPFS can't realize its promise **URL:** \ **Category:** Uncategorized\ **Created:** [June 8, 2019, 1:05pm UTC](https://discuss.ipfs.tech/t/ipfs-cant-realize-its-promise/5607 "2019-06-08T13:05:23Z")\ **Posts on this page:** 1\ **Showing post:** 12
**Author:** ![jasonzhouu](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/jasonzhouu/32/2682_2.png) [@jasonzhouu](https://discuss.ipfs.tech/u/jasonzhouu)\ **Post date:** [June 10, 2019, 12:06am UTC](https://discuss.ipfs.tech/t/ipfs-cant-realize-its-promise/5607/12 "2019-06-10T00:06:16Z")
> [@leerspace](#): > > What do you think are insurmountable technical challenges that can’t be solved Performance of existing DHT algorithms. I don’t think it can’t be solved. And yeah, many existing issues can very probably be solved in the future, such as unlimited energy, and there are already many plans. But it don’t mean that you can boast that you can reach there before you have a good enough solution. > [@leerspace](#): > > maybe you’re just using it to refer to issues you can’t think of a solution to (or haven’t yet). Do you already have a solution to solve the performance problem? - [What is the reason for very slow · Issue #6382 · ipfs/kubo · GitHub](https://github.com/ipfs/go-ipfs/issues/6382) - [Can't access published IPNS record, config problem?](https://discuss.ipfs.tech/t/cant-access-published-ipns-record-config-problem/5476) Solutions in [Content Resolution And Gateway Performance · Issue #6383 · ipfs/kubo · GitHub](https://github.com/ipfs/go-ipfs/issues/6383) are not enough, they can’t solve the basic problem. And [GitHub - libp2p/research-dht: Moved discussion notes to https://github.com/libp2p/notes](https://github.com/libp2p/research-dht) don’t have an applicable plan too. > [@leerspace](#): > > Reference sections 2.1 and 3.3. - section 2.1: it’s like state of art - section 3.3: there is not that much useful information there --- _[View the full topic](https://discuss.ipfs.tech/t/ipfs-cant-realize-its-promise/5607)._