Nostr Web Client

⚡️ hampus@blixtwallet.com

This Lightning Address is special.

When you pay to it, my Lightning Box solution will forward the request to the phone, where Blixt Wallet respond with an invoice.

This is the first time a self-custodial LN wallet supports Lightning Address.

This is part of my on-going work to support receiving via Lightning Address for mobile self-custodial wallets.

https://github.com/hsjoberg/lightning-box

Android supports foreground services, meaning that Blixt Wallet can stay online all the time to answer incoming requests (no effect on battery).

Though the normal mode of operation for Lightning Box is that it'll take the payment on behalf of the user and then next time the user opens wallet, it will auto-withdraw from the Box, thanks to LNURL-withdraw.

But if the wallet is online already, it can just forward the request.

Hampus 2y ago

Well, one of the concerns is the one your raised on Twitter.

Few people seem to understand or know that your channel opening transactions leak in your invoice routehints.

This can be fixed either by blinded routing (BOLT11/12) or alias scid (BOLT11).

Another concern I have is the fact that seemingly no LN wallet today let’s you enforce min X number of hops.

As Lightning is an onion routed payment network, the more hops you do, the more privacy you potentially get.

Fewer hops lead to bigger risk of de-anonymising your payment.

A lot of people are using custodial LN wallets in order to have a Lightning Address, simply by the fact that it’s by far the easiest option. The only options available right now are custodial or a self-hosted routing node (which few have).

I’ve a project called Lightning Box that tries to improve things by forwarding the LNURL-pay request to the phone. Privacy-minded people can use a wallet that has Tor integrated to not leak info.

Reply to this note

Discussion