Since the shut down of Nix-Bitcoin, I have had to integrate the repo into my own. This was important as Sovran_SystemsOS (https://sovransystems.com) uses it for its node implementation. I wanted it to be very simple for a NixOS user to apply a full Bitcoin Sovereign stack.
# configuration.nix — the base node
{
sovran-bitcoin = {
enable = true;
operatorName = "alice"; # your user
};
}Thus, I had to create Sovran_Bitcoin https://github.com/naturallaw777/Sovran_Bitcoin.
It carries all the same security enhancements as Nix-bitcion and adds NWC and LNURL.
It works really well and I just ran it through top AI models for a security audit.
This allows any NixOS user to have a full working Bitcoin and Lighting Node running in just several minutes. Fully Sovereign.
The beauty is, once you get inbound and outbound channels on your LND node, you can easily create a new NWC wallet and connect it right into Zeus for spending and any NOSTR client for zaps!!
The user wants a short. ~lightning
?
Fair enough, that was clumsily put. I meant: Bitcoin node + LND out of the box is useful, and the majority of users run with this setup, ready to plug in Zeus.
Is there a way to import data from current operating systems? Like a tool for migration or something?
Ah, got ya! Right now I don't have a migration tool created. It seems the key part would be the LND back up (channels, etc) from the old machine. RTL handles this. I have never done that before. I imagine it should be fairly straight forward.
Good move, a clean fork is really the only sensible path after Nix-Bitcoin shut down. The module approach you have in that config snippet looks tidy.
One thing I would be curious about is how you handle security updates going forward. With the upstream repo gone, are you pinning to a specific last-known-good commit and patching by hand, or do you plan to keep the module maintained long term? That is usually where these forks quietly rot, not in the initial setup.