# How a Hypercore P2P innovation could bring more privacy to IPFS **URL:** \ **Category:** Related News\ **Tags:** privacy\ **Created:** [January 25, 2022, 2:19pm UTC](https://discuss.ipfs.tech/t/how-a-hypercore-p2p-innovation-could-bring-more-privacy-to-ipfs/13256 "2022-01-25T14:19:24Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![da2w](https://avatars.discourse-cdn.com/v4/letter/d/f4b2a3/32.png) [@da2w](https://discuss.ipfs.tech/u/da2w)\ **Post date:** [January 25, 2022, 2:19pm UTC](https://discuss.ipfs.tech/t/how-a-hypercore-p2p-innovation-could-bring-more-privacy-to-ipfs/13256/1 "2022-01-25T14:19:25Z")
> **[How a Hypercore P2P innovation could bring more privacy to IPFS](https://www.ctrl.blog/entry/dht-privacy-discovery-hash.html)** > > IPFS want’s to replace HTTPS as the web’s content delivery protocol. However, it can’t do that without improving on user privacy. Hypercore has the solution. **TL;DR:** IPFS should migrate to announcing a discovery hash constructed from the content hash (the CID) on DHT. Peers find each other using the public discovery hash. Once two peers have established a enencrypted connection, they’d ask each other for the actual content hash. As long as the content hash remains a secret, no one monitoring the network will know the hash/CID needed to make other peers transfer them the data. It’s a simple fix that introduces some sorely needed privacy. ---
**Author:** ![adin](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/adin/32/2679_2.png) [@adin](https://discuss.ipfs.tech/u/adin)\ **Post date:** [January 25, 2022, 9:38pm UTC](https://discuss.ipfs.tech/t/how-a-hypercore-p2p-innovation-could-bring-more-privacy-to-ipfs/13256/2 "2022-01-25T21:38:31Z")
Some discussion on this is in [Hypercore DHT privacy enhancement · Issue #263 · ipfs/specs · GitHub](https://github.com/ipfs/specs/issues/263)