Repository navigation
Add Lampo as a Lightning implementation - #5
Merged
Merged
Conversation
kwsantiago
force-pushed
the
lampo-node
branch
2 times, most recently
from
October 8, 2026 13:07
24154ba to
37e05c3
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds Lampo, an LDK-based node, as a third Lightning implementation next to LND and Core Lightning.
docker/lampobuildslampod-cli,lampo-cliand thelampo-bitcoindchain plugin from a privkeyio/lampo.rs tag, and fails if the tag has moved, as the LND image does. The entrypoint writeslampo.confon 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.src/lib/lightning/lampo). That API has no authentication, so its port is published on 127.0.0.1 only. It needs privkeyio/lampo.rsv0.1.0-blake2b.1, which adds thepeersroute and reports which side opened each channel.nodes.jsonmove 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 lintand the full test suite pass.