You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add an enable_lnurl_resolution flag to HumanReadableNamesConfig that, when set, attaches an HTTPHrnResolver as a fallback to the configured BIP 353 / bLIP-32 resolver. The fallback is consulted only when the primary resolver returns an error, so it covers LN-Address recipients that don't publish a BIP 353 record and direct LNURL-pay links, while never shadowing a successful primary resolution.
Enabling this opts in to revealing our IP and payment target to the LNURL endpoint, so it defaults to off.
Add an `enable_lnurl_resolution` flag to `HumanReadableNamesConfig`
that, when set, attaches an `HTTPHrnResolver` as a fallback to the
configured BIP 353 / bLIP-32 resolver. The fallback is consulted only
when the primary resolver returns an error, so it covers LN-Address
recipients that don't publish a BIP 353 record and direct LNURL-pay
links, while never shadowing a successful primary resolution.
Enabling this opts in to revealing our IP and payment target to the
LNURL endpoint, so it defaults to off.
Co-developed with Claude Code (claude-opus-4-7).
👋 Hi! This PR is now in draft status.
I'll wait to assign reviewers until you mark it as ready for review.
Just convert it out of draft status when you're ready for review!
The reason will be displayed to describe this comment to others. Learn more.
Hmm, I'm not sure we want this to be a config option to begin with? If this is just due to the possible privacy leak, it should probably be part of the respective variant on the resolution config?
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
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.
Closes#870
Add an
enable_lnurl_resolutionflag toHumanReadableNamesConfigthat, when set, attaches anHTTPHrnResolveras a fallback to the configured BIP 353 / bLIP-32 resolver. The fallback is consulted only when the primary resolver returns an error, so it covers LN-Address recipients that don't publish a BIP 353 record and direct LNURL-pay links, while never shadowing a successful primary resolution.Enabling this opts in to revealing our IP and payment target to the LNURL endpoint, so it defaults to off.
Co-developed with Claude Code (claude-opus-4-7).