b412de3ad7
Previously, dhcpcd and bitcoind starting up in parallel could lead to the following error in bitcoind: ``` bitcoind: libevent: getaddrinfo: address family for nodename not supported bitcoind: Binding RPC on address 127.0.0.1 port 8332 failed. bitcoind: Unable to bind any endpoint for ``` After the initial failure, the bitcoind service would always restart successfully. This race condition, where both applications were simultaneously manipulating network resources, was only triggered under specific hardware conditions. Fix it by running bitcoind after dhcp has started (by running after `network-online.target`). This bug and the fix only affect the default NixOS scripted networking backend. |
||
|---|---|---|
| docs | ||
| examples | ||
| helper | ||
| modules | ||
| pkgs | ||
| test | ||
| .cirrus.yml | ||
| LICENSE | ||
| README.md | ||
| SECURITY.md | ||
| default.nix | ||
| flake.lock | ||
| flake.nix | ||
| overlay.nix | ||
| shell.nix | ||
README.md
nix-bitcoin is a collection of Nix packages and NixOS modules for easily installing full-featured Bitcoin nodes with an emphasis on security.
Overview
nix-bitcoin can be used for personal or merchant wallets, public infrastructure or for Bitcoin application backends. In all cases, the aim is to provide security and privacy by default. However, while nix-bitcoin is used in production today, it is still considered experimental.
nix-bitcoin nodes can be deployed on dedicated hardware, virtual machines or containers. The Nix packages and NixOS modules can be used independently and combined freely.
nix-bitcoin is built on top of Nix and NixOS which provide powerful abstractions to keep it highly customizable and maintainable. Testament to this are nix-bitcoin's robust security features and its potent test framework. However, running nix-bitcoin does not require any previous experience with the Nix ecosystem.
Get started
- See the examples for an overview of all features.
- To setup a new node from scratch, see the installation instructions.
- To add nix-bitcoin to an existing NixOS configuration, see importable-configuration.nix and the Flake example.
Docs
Hint: To show a table of contents, click the button (
) in the
top left corner of the documents.
- NixOS options search
- Hardware requirements
- Installation
- Configuration and maintenance
- Using services
- FAQ
Features
A configuration preset for setting up a secure node
- All applications use Tor for outbound connections and support accepting inbound connections via onion services.
NixOS modules (src)
- Application services
- bitcoind
- clightning with support for announcing an onion service
and database replication.
Available plugins:- clboss: automated C-Lightning Node Manager
- currencyrate: currency converter
- helpme: walks you through setting up a fresh c-lightning node
- monitor: helps you analyze the health of your peers and channels
- prometheus: lightning node exporter for the prometheus timeseries server
- rebalance: keeps your channels balanced
- summary: print a nice summary of the node status
- zmq: publishes notifications via ZeroMQ to configured endpoints
- clightning-rest: REST server for clightning
- lnd with support for announcing an onion service and static channel backups
- Lightning Loop
- Lightning Pool
- charge-lnd: policy-based channel fee manager
- lndconnect: connect your wallet to lnd or clightning via a REST onion service
- Ride The Lightning: web interface for
lndandclightning - spark-wallet
- electrs
- fulcrum (see the module for a comparison to electrs)
- btcpayserver
- liquid
- JoinMarket
- bitcoin-core-hwi
- Helper
- netns-isolation: isolates applications on the network-level via network namespaces
- nodeinfo: script which prints info about the node's services
- backups: duplicity backups of all your node's important files
- operator: adds non-root user
operatorwho has access to client tools (e.g.bitcoin-cli,lightning-cli)
Security
See SECURITY.md for the security policy and how to report a vulnerability.
nix-bitcoin aims to achieve a high degree of security by building on the following principles:
- Simplicity: Only services enabled in
configuration.nixand their dependencies are installed, support for doas (sudo alternative), code is continuously reviewed and refined. - Integrity: The Nix package manager guarantees that all dependencies are exactly specified, packages can be built from source to reduce reliance on binary caches, nix-bitcoin merge commits are signed, all commits are approved by multiple nix-bitcoin developers, upstream packages are cryptographically verified where possible, we use this software ourselves.
- Principle of Least Privilege: Services operate with least privileges; they each have their own user and are restricted further with systemd features, RPC whitelisting and netns-isolation. There's a non-root user operator to interact with the various services.
- Defense-in-depth: nix-bitcoin supports a hardened kernel, services are confined through discretionary access control, Linux namespaces, dbus firewall and seccomp-bpf with continuous improvements.
Note that if the machine you're deploying from is insecure, there is nothing nix-bitcoin can do to protect itself.
Security fund
The nix-bitcoin security fund is a 2 of 3 bitcoin multisig address open for donations, used to reward
security researchers who discover vulnerabilities in nix-bitcoin or its upstream dependencies.
See Security Fund for details.
Troubleshooting
If you are having problems with nix-bitcoin check the FAQ or submit an issue.
There's also a Matrix room at #general:nixbitcoin.org
and a #nix-bitcoin IRC channel on libera.
We are always happy to help.