Bastien,
Maybe I'm misunderstanding option 1 or perhaps it's not clear. Are you saying
with that option, all it takes is a single DNS entry for "serviceprovider.com"
to service unlimited users? The interchanging between "bob" and "domain owner"
is a bit confusing in your gist. I think it would
Bastien,
For completeness, would you be willing to demonstrate what it might look like
if it were bolt12 in the normal LNURL way? The concern is mostly what you
brought up with relying on DNS entries instead of a typical web server. At
scale, that would be much more difficult for LNURL service
Bastien,
The main concern on the LSP not keeping a reserve is that it's much easier for
them to steal since the offline concern is on the mobile user. We still do not
yet have reliable watch tower integrations/products to help mitigate this. Yes,
there's reputation, but how does a user go
Bastien,
ACK for this. But don't wallets & LSPs already have the option to provide this
UX and have been doing it for years? Are you proposing a network wide switch
away from reserves or just between mobile wallets and LSPs if they opt in? And
what about the dust reserve limit too? From my
Is there a better place to have public communication? Unfortunately since one
off topic email was sent here, it's been a ghost town. It appears that there's
many emails being held and only one moderator that checks them once a week.
Would hate to see this list die but wondering if there's a
Rene,
Thanks for your reply.
> Also wallets tend to have poor utxo management. So looking at the on-chain
> signal one can probably guess for a p2wsh to which two nodes it might belong
> and try them first.
That was going to be one of my next steps. I thought about parsing through the
data
playing field. It is also beneficial to get a
>> better estimate of the unknown size of the Lightning Network.
>
> I love the research and thanks for sharing all the information. I am assuming
> analytic firms would be using this already.
>
> /dev/fd0
>
> Sent with
Hi,
For the past few months I have been working on an LDK probing project that
searches for unannounced channels on the Lightning Network. For the past week,
I have been probing on mainnet and squashing bugs / making optimizations.
So far I have found near 445 unannounced channels totaling
