Repository navigation
Unified send doesn't support lnurl #870
Description
Activity
Note there will be quite a bit of resolution-related changes coming as part of #630.
However, it seems to me that either one of these might be the way to go
- Update
LDKOnionMessageDNSSECHrnResolverto optionally support lnurl through providing a http resolver - Update bitcoin-payment-instructions to support providing multiple resolvers.
We definitely shouldn't revert he BIP353 changes in favor of LNURL.
Not sure if @TheBlueMatt has an opionion on the preferred approach?
- Update
Update LDKOnionMessageDNSSECHrnResolver to optionally support lnurl through providing a http resolver
IMO we should do this, though I'm not sure that we want to just provide a full HTTP resolver vs just turn on an option that automatically falls back to it?
We use ldk's
LDKOnionMessageDNSSECHrnResolverto resolve HRNs which doesn't support lnurl.Some options to fix this:
LDKOnionMessageDNSSECHrnResolverwithHttpResolver: simplest but loses privacy benefitsLDKOnionMessageDNSSECHrnResolverto optionally support lnurl through providing a http resolver