Nix’s guarantee of reproducibility hinges on a simple mechanism: absolute, immutable store paths (i.e. /nix/store). While this rigidity guarantees that binaries always find their exact dependencies, it introduces a massive constraint: it binds the entire ecosystem to a single, global directory. If you want to run a Nix binary on a target system where you don't have root access to create /nix, or where you cannot run an unprivileged user namespace, you are forced to rebuild the world To achieve true portability and friction-free deployment across arbitrary infrastructure, Nix binaries must become fully relocatable. What does that mean ? Why is it hard? Who cares (psst me!)? We will discuss what a fully relocatable Nix ecosystem could look like , and how solving this constraint could allow Nix to be run more easily on more restrictive environments..