nix-bitcoin

Go to file

Jonas Nick 81503ebc83 Merge #315 : Use doas instead of sudo `47d257ad3a` docs: add rationale for doas to README and FAQ (nixbitcoin) `b0039d68a0` docs: discourage users from ssh'ing into the root user (nixbitcoin) `2ca92a34a5` services: use doas if enabled (nixbitcoin) `ce2b445777` treewide: use runuser for dropping privileges (Erik Arvstedt) Pull request description: ACKs for top commit: jonasnick: ACK `47d257ad3a` Tree-SHA512: 84bab7de1cc6fb3d405a4fc4589f2be825275f69e48dede6ff62d1a27e3a386fea530c91a234d006ec6305a46d0ec54ca836f52f197541a3df215369c9b7c1e2		2021-02-11 21:28:59 +00:00
ci	ci: use 'cachix watch-exec'	2021-02-07 22:45:37 +01:00
docs	docs: add rationale for doas to README and FAQ	2021-02-09 12:44:08 +00:00
examples	Merge #312 : Refactorings, cleanups	2021-02-08 20:32:03 +00:00
helper	Fetch from the nixpkgs repo instead of nixpkgs-channels	2020-12-06 21:42:20 +00:00
modules	services: use doas if enabled	2021-02-09 12:44:04 +00:00
pkgs	Merge #312 : Refactorings, cleanups	2021-02-08 20:32:03 +00:00
test	treewide: use runuser for dropping privileges	2021-02-09 12:44:01 +00:00
.cirrus.yml	fix build-to-cachix	2021-01-30 11:38:47 +01:00
.gitignore	Fix typo in gitignore	2020-11-24 18:25:12 +01:00
default.nix	simplify overlay.nix	2020-01-09 10:43:29 +01:00
LICENSE	Add license	2019-01-02 14:03:52 +00:00
overlay.nix	simplify overlay.nix	2020-01-09 10:43:29 +01:00
README.md	docs: add rationale for doas to README and FAQ	2021-02-09 12:44:08 +00:00
shell.nix	Clean up development shell.nix	2020-03-30 10:49:15 +02:00

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

A Bitcoin node verifies the Bitcoin protocol and provides ways of interacting with the Bitcoin network. nix-bitcoin nodes are used for a variety of purposes and can serve as personal or merchant wallets, second layer public infrastructure and as backends for Bitcoin applications. 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.

A full installation of nix-bitcoin is usually deployed either on a dedicated (virtual) machine or runs in a container and is online 24/7. Alternatively, the Nix packages, NixOS modules and configurations 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.

Examples

See here for examples.

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

Application services
- bitcoind, with a default banlist against spy nodes
- clightning with support for announcing an onion service
  Available plugins:
  - clboss: automated C-Lightning Node Manager
  - 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
- lnd with support for announcing an onion service
  - lndconnect via a REST onion service
- spark-wallet
- electrs
- btcpayserver
- liquid
- Lightning Loop
- JoinMarket
  - JoinMarket Orderbook Watcher
- recurring-donations: for periodic lightning payments
- 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 operator who has access to client tools (e.g. bitcoin-cli, lightning-cli)

Security

Simplicity: Only services you select in configuration.nix and their dependencies are installed, packages and dependencies are pinned, support for doas (sudo alternative), most packages are built from the NixOS stable channel, with a few exceptions that are built from the nixpkgs unstable channel, builds happen in a sandboxed environment, code is continuously reviewed and refined.
Integrity: Nix package manager, NixOS and 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 options, RPC whitelisting, and netns-isolation. There's a non-root user operator to interact with the various services.
Defense-in-depth: nix-bitcoin is built with a hardened kernel by default, 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.

Docs

Troubleshooting

If you are having problems with nix-bitcoin check the FAQ or submit an issue. There's also a #nix-bitcoin IRC channel on freenode. We are always happy to help.