-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Does lndk still need a custom branch of LND? #94
Comments
Hmm looks like people still have to compile LND with dev flag because of this: this is in the lnd docs.
and then there is this. /// ONION_MESSAGE_TYPE is the message type number used in BOLT1 message types for onion messages.
const ONION_MESSAGE_TYPE:u32 = 513; |
Oh yup we need to update the docs, lndk should work with the latest versions of LND (v17+), no custom branch needed. But iirc you'll still need to add those |
It's still annoying that you have to compile with dev flag though else type 513 won't be supported by LND. And nobody will compile with dev flag manually for production builds. |
Indeed, but the
That's out of our control as a project, sadly. If you want to run experimental software (LNDK), you're going to have to do some experimental things (dev tag), I don't see any getting around that. |
Thanks for pointing out that the docs are out of date (my absolute worst pet peeve that I'm always guilty of ☠️ ), fixed by #95. |
Re: the |
In the readme it says to run a custom branch and add this to the conf file.
LND now has this API, can lndk rely on this instead?
https://lightning.engineering/api-docs/api/lnd/peers/update-node-announcement
The text was updated successfully, but these errors were encountered: