⚡️ 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.

Reply to this note

Please Login to reply.

Discussion

Great works Hampus, middle-ground for non-custodial mobile users. Available for next version of Blixt?

Thank you! Yes, I do the trade-offs being made are sound.

Not next version, but soonish. Are you in in our Telegram group @BlixtWallet?

I will start an internal alpha eventually with people that are interested to try it out.

Great to hear that. Yeah, previously i'm used to be in Blixt Telegram Group. But, somehow i got kicked out. Maybe, because i don't use any profile picture so it seems like a bot account. 😅

Thank you, i will try to join again later

Haha yeah we have some harsh ban waves because of the amount of bots.

Please tell me your handle here or in DMs and I’ll unban you.

Wow, thats very nice. I'm already looking forward to it 🔥

Blixt is one of my most used LN wallets⚡ ⚡

Hot take: foreground services will make Blixt the best android lightning wallet hands-down

This is big news for non-custodial lightning. Very cool!

#[0]

Congratulations this is fantastic!

Interesting.

Does this mean you have the actual invoice paid on your phone wallet (if online)?

Yes, an invoice is literally created inside my Blixt Wallet app and then gets paid.

Check this out:

https://twitter.com/hampus_s/status/1630231931726987265

Wow 😍

just joined the test flight🍻

blixt wallet is very good. recommended.

it is the second time. alby is also self-custodial and supports a lighting address. alby runs on computers

does blixtwallet run on android emulation? will you convert it to linux?

Sorry, the text was copied verbatim from my Twitter thread where I didn’t have space to properly explain within the tweet contraints.

This is the first time a mobile LN node wallet (like Blixt Wallet, OBW, Breez, Phoenix etc) supports this.

Alby does this, but it requires a separate normal Lightning node running, which increases the barrier to entry drastically.

Yes, Blixt should run just fine in Android emulation.

Linux port is WIP.

jag alskar sverige .all i know but i did not need more because everyone was smart and spoke english

No excuse for people to keep using Wallet of Satoshi for lnurl when a user friendly noncustodial LN wallet (Blixt) supports it:

#[0]

I should’ve been clear that this is not publicly released yet. My apologies.

But yes I agree with your message. When this is out, you shouldn’t need to use custodial Lightning Address solutions anymore.

In fact, this complaint of custodial LN being on nostr was partly the reason why I started looking into my Lightning Box service again.

Can I give a recommendation for a #[2] shoutout? Developer #[3] for developing Blixt wallet (open source, non custodial). Doing great things.

#[1]

LNURL-pay was first developed for commerce/B2C.

Years later Lightning Address came along and became a success, because it allowed for an easy to write & read handle.

Soon even custodial wallets started using Lightning Address and this later lead to widespread usage on nostr.

It's a succession of events that lead to the current situation.

So as it stands now, non-custodial LN wallets are losing on walkover to custodial wallets, where you have easy access to a Lightning Address.

My Lightning Box solution tries its best to work within this framework that has been developed and gives a sound alternative to using a 100% custodial and trusted Lightning Address solution.

#[0]

Other technologies such as BOLT12, especially with "async payments", could help steer people away from Lightning address.

But it cannot fully replace it, because the primary value proposition of Lightning Address is an easy to read and write handle, which BOLT12 doesn't have.

It's possible we can do some neat "spacechain DNS with BOLT12/BOLT11 AMP" and whatnot, so I'm open to possible ideas.

Cheers!

Yes I’ve seen a couple of payments popping up in my Blixt Wallet, courtesy of #[4]

Yes, I’m working on a solution for y’all.

#[3]

Yes, I’m cooking some stuff.

It’s at least an alternative to 100% custodial.

#[4]

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.

#[2]

👀⚡⚡⚡⚡⚡⚡⚡

#[0]