Static Builds (Bitcoin Core Dev Tech, May 2026)

Fully static builds — binaries that bundle their dependencies down to libc, rather than loading shared libraries at runtime — are seen as very desirable and nearly within reach, especially once libevent is removed. The session noted the drawbacks and constraints: statically linking libc has rough edges (for example dlopen behavior), the result would be Linux-only on a subset of architectures, and a fully static build was shown running even on an old distribution like Ubuntu 12.

The GUI is the main complication, because it loads fonts and other resources at runtime, so the likely path is splitting releases into GUI and non-GUI builds. That lets bitcoind and the utility binaries be fully static, while the GUI (possibly with bundled Qt) still depends on the OS — consistent with the multiprocess vision. The GUI is not a blocker for a static bitcoind, and removing libevent would bring fully static Bitcoin Core nearly within reach.