Skip to content

Conversation

@a-mpch
Copy link

@a-mpch a-mpch commented Aug 20, 2025

In order to run LNDK along side my umbrel LND node I needed to modify manually the umbrel-lnd.conf to make it work (ssh into it and then modify it).

I would like to publish an app for LNDK to Umbrel but users would need to do some manual modification of their node or have a trigger button for it. Then, I thought adding these settings makes sense so their modification are only done through the same UI of their node and we could walkthrough them to it.

Then, this PR has 3 parts:

  1. Updates the default development LND so we can make use of this apps.
  2. Add support of the custom message and feature bits in the backend side. Handle the null value not writing it on disk.
  3. Add the UI in the AdvancedSettingsModal that takes care of adding the configuration.
image

Happy to discuss if this approach makes sense.

a-mpch added 3 commits August 20, 2025 17:44
This commit adds backend support for `protocol.custom-message`,
`protocol.custom-init`, and `protocol.custom-nodeann`, allowing node
runners to handle messages separately from the LND instance.
This enables running LNDK to handle onion messages in a shim
alongside LND.
This commit adds a new "Protocol" settings group to the
`AdvancedSettingsModal` with three new configuration options:
- protocol.custom-message: Custom message handling number
- protocol.custom-init: Custom feature bit for init messages
- protocol.custom-nodeann: Custom feature bit for node announcements

Each setting accepts a number or null value and updates the
umbrel-lnd.conf file accordingly.
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