Core Lightning

• Name: Core Lightning
• URL: https://docs.corelightning.org/docs/installation
• Category: Bitcoin Lightning node implementation / plugin-extensible node-operations stack / Lightning JSON-RPC infrastructure
• Tags: bitcoin-ecosystem
• Summary: Core Lightning is a Lightning node-and-ops substrate, not a wallet app and not just a reference binary. The useful split is the lean core plus the plugin surface around it: Unix-socket JSON-RPC, extensibility, reproducible builds, and deployment paths that let operators or packaged stacks shape the rest.
• What it does:
  • Runs a Lightning Network node on top of a synchronized local or remote bitcoind instance and supports both mainnet and test environments such as testnet and regtest
  • Exposes a JSON-RPC 2.0 interface over a Unix domain socket, with lightning-cli and a Python client library for programmatic control
  • Supports core node operations including address generation, fund tracking, peer connections, channel funding, invoice creation, payment sending, and plugin management
  • Supports plugin-based extensibility and maintains a broader plugin ecosystem for adding operational and application-layer capabilities
  • Offers multiple deployment paths including precompiled binaries, Docker images, source builds, nixOS packaging, and third-party GUI/operator environments such as Ride the Lightning, Umbrel, BTCPay Server, RaspiBlitz, and Start9
  • Documents HD-wallet-seed encryption, reproducible builds, and optional Rust-based plugins such as cln-grpc, clnrest, cln-bip353, and wss-proxy
• Key claims:
  • The official README describes Core Lightning as a lightweight, highly customizable, specification-compliant implementation of the Lightning Network protocol
  • The README says the implementation has been in production use on Bitcoin mainnet since early 2018 and is considered stable enough for mainnet, even though new users are encouraged to start on testnet or regtest
  • The README says Core Lightning works on Linux and macOS and requires a fully synchronized bitcoind instance at version 25.0 or above with transaction relay enabled
  • The README says Core Lightning exposes JSON-RPC 2.0 over a Unix domain socket and highlights operational RPC methods such as newaddr, listfunds, connect, fundchannel, invoice, pay, and plugin
  • The README says Core Lightning does not require ZeroMQ or txindex for synchronization, which is a meaningful architectural distinction versus some other Bitcoin-node-adjacent tooling
  • The installation docs show supported distribution through GitHub release binaries, Docker images, and source compilation, plus GUI/operator integrations through Ride the Lightning, Umbrel, BTCPay Server, Raspiblitz, and Start9
  • The installation docs show Core Lightning’s build and extension surface now includes optional Rust-backed components like cln-grpc, clnrest, cln-bip353, and wss-proxy, while still allowing operators to disable Rust if those plugins are unnecessary
• Whitepaper: No canonical standalone Core Lightning whitepaper or litepaper surfaced in this pass. The clearest current sources of truth were the official README and installation docs; see ../whitepapers/core-lightning-primary-sources-2026-05-01.md.
• Sources:
  • https://docs.corelightning.org/docs/installation
  • https://github.com/ElementsProject/lightning
  • https://raw.githubusercontent.com/ElementsProject/lightning/master/README.md

Internal linkages

• Company boundary for the broader implementation / service / wallet shell around this codebase: blockstream.
• Canonical implementation contrasts: lnd and eclair

Protocol / company boundary

• Keep this note on the implementation surface: the daemon, JSON-RPC model, plugin ecosystem, build and packaging choices, and the ways operators can compose Core Lightning into larger merchant, wallet, or node stacks.
• Use blockstream when the sharper question is who still stewards and packages this implementation inside a broader company shell that also includes Greenlight, wallet products, enterprise workflow, and commercial support paths.
• That split matters because what capabilities and composition points does Core Lightning expose? and which company sits closest to the release, support, and commercialization shell around it? are related but not identical questions.

Control surface

• Practical leverage sits in plugin choice, JSON-RPC exposure, bitcoind coupling, wallet-seed and build-verification discipline, and which surrounding packages turn the daemon into a friendlier merchant or node stack.

• Core Lightning matters because it keeps more of that composition visible instead of burying it in one blessed product shell.

• The company note matters separately because Blockstream still packages and markets this implementation inside Greenlight and a broader company product surface without reducing Core Lightning itself to a mere vendor feature.

• Read it as a modular Lightning backend, not as a complete operator experience on its own.

• Last reviewed: 2026-08-06 UTC