Hi Alexander, this is really great!<p>I&#x27;ve started `registry-mirror` to demonstrate how a Content-Addressed file structure and P2P discovery, can bring a lot of speed improvements, specially when the bottleneck is low bandwidth&#x2F;latency to the backbone, by connecting to more local peers that have the content that we are looking for.<p>Right now, the goal with `registry-mirror` is to have a very large IPFS node in the network with the entire npm and that keeps replicating it, while end user machines only download the modules they need (and if they agree, provide them to the network as well). Each end user will be able to get the latest state of the registry, through a IPNS hash, a mutable pointer, that changes each time the mirror is updated.<p>The nix package manager model layers perfectly on top of IPFS&#x27; MerkleDAG (<a href="https:&#x2F;&#x2F;github.com&#x2F;ipfs&#x2F;specs&#x2F;tree&#x2F;master&#x2F;merkledag" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;ipfs&#x2F;specs&#x2F;tree&#x2F;master&#x2F;merkledag</a>), it can be a very awesome transport for ied. An example of a package manager that uses IPFS to distribute the packages is GX <a href="https:&#x2F;&#x2F;github.com&#x2F;whyrusleeping&#x2F;gx" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;whyrusleeping&#x2F;gx</a> - Still a WIP.<p>If this is interesting to you, join us at IRC Freenode #IPFS, it would be great to bounce more ideas! :)