Comparison table of software implementations

ImplementationsLNDCore Lightning


written in C with plugins in various languages



IRC #c-lightning

Main advantages

bigger networkshare and team more services built on top detailed documentation bundled with services and GUI in lit binaries provided for various platforms

specs driven modular development ensures flexibility very modest hardware need even as a routing node built with privacy as a priority in mind

Multiple channels between two peers


yes since v0.11.0



on by default


most efficient in finding the shortest path best success rate a cost function takes recent failures into consideration

prefers low locktimes takes channel sizes into account since v0.10.2 (Pickhardt Payments) Slightly more expensive due to randomization for privacy the logic can be replaced with plugins

MPP (multi part payments)


on by default


Loop service (with daemon) (with daemon) PeerSwap through website + API PeerSwap


built in, but limited

CLBOSS plugin with advanced logic


built in not incentivised

available as a plugin for Eye of Satoshi not incentivised

Dymanic fee settings

solved by external tools like charge-lnd and Balance of Satoshis

feeadjuster plugin, CLBOSS

Dual funded channels

manual, using PSBTs and/or Balance of Satoshis

experimental feature automated with liquidity ads

Paid incoming channels

Pool service including sidecar channels Voltage Flow Magma plugin liquidity ads Magma


full Tor support


RTL Thunderhub Lightning Terminal

RTL Spark Wallet / Sparko

Mobile Apps

Zeus Fully Noded (iOS only) Zap Android (iOS unmaintained)

Zeus Fully Noded (iOS only)

Database format

bbolt by default (restarts needed to compact) experinemtal etcd full postgres support

sqlite3 by default (compacts on-the-fly) full postgres support

Backups and recovery

hsmsecret hex (optional seedwords) + append-only (low wear) backup of the sqlite3 database with the backup plugin sqlite3 replication to a custom path or NFS mount


Last updated