Skip to content

Add Lampo as a Lightning implementation - #5

Merged
kwsantiago merged 1 commit into
masterfrom
lampo-node
Oct 8, 2026
Merged

kwsantiago merged 1 commit into
masterfrom
lampo-node

Conversation

@kwsantiago

@kwsantiago kwsantiago commented Oct 8, 2026 •

Copy link
Copy Markdown
Collaborator

Adds Lampo, an LDK-based node, as a third Lightning implementation next to LND and Core Lightning.

  • docker/lampo builds lampod-cli, lampo-cli and the lampo-bitcoind chain plugin from a privkeyio/lampo.rs tag, and fails if the tag has moved, as the LND image does. The entrypoint writes lampo.conf on every start, waits for the backend before creating the wallet, and removes a wallet database left without its seed by an interrupted first start, which otherwise stops the node from ever starting.
  • Polar talks to Lampo's REST API (src/lib/lightning/lampo). That API has no authentication, so its port is published on 127.0.0.1 only. It needs privkeyio/lampo.rs v0.1.0-blake2b.1, which adds the peers route and reports which side opened each channel.
  • Lampo nodes can be added when creating a network, in the designer and through the MCP tools, on macOS and Linux. SimLN does not support them.
  • The repo state and nodes.json move to version 2 for the new image.

Tested end to end on a network generated by this code (Knots, Core Lightning, LND, Lampo), driving Lampo through the new service: it was funded, opened channels to both peers and accepted channels from both, paid and was paid by both, closed a channel cooperatively by channel point, and kept its identity across a restart, in 3 of 3 runs with no container restarts. yarn tsc, yarn lint and the full test suite pass.

@kwsantiago
kwsantiago force-pushed the lampo-node branch 2 times, most recently from 24154ba to 37e05c3 Compare October 8, 2026 13:07
@kwsantiago
kwsantiago merged commit cd584c6 into master Oct 8, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant