⚡️ 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.
Yes, I’m cooking some stuff.
It’s at least an alternative to 100% custodial.
#[4]
Yes, that would be pretty epic.
Lnd REST in Blixt is unfortunately broken for the time being, because of the way Blixt and lnd is set up.
But I’m trying to figure it out.
Example of Receiving Non Custodial Zap and Self-Hosted NIP-05 in Mobile Phone (Zero Additional Cost)
Please help me (zap 1 sats) to test this account, let me know if you found any problems
#[0]
Complete tutorial will be delivered after this test.
List of Tools:
1. Termux Apps on Android (Fdroid version)
2. LND (ARM64 version)
3. Satdress Fork - https://github.com/believethehype/satdress by #[1]
4. #[2] - ZEUS Wallet
5. Thunderhub - https://github.com/apotdevin/thunderhub
6. Cloudflared Tunnel - https://github.com/cloudflare/cloudflared
#nostr #bitcoin #zap #selfhost
This is very based 👏
⚡️ 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.
Yes, I’m working on a solution for y’all.
#[3]
Indeed, having many custodial solutions is also a form of decentralization.
Every Bitcoiner should NOT run a Lightning node.
Running a good routing node takes a lot of care and putting up a half-assed node with bad internet connection actually harms the network more than it does any good.
You will very likely not see any Return On Investment either.
Use a private node wallet, like Blixt Wallet, OBW, Breez and Phoenix, that opens private channels and does not route payments for others.
You don’t need to be a routing node to use Lightning.
No, LNURL authentication is done via your seed.
So if you restore with the same seed, there’s nothing to worry about.
It unfortunately sounds like too many, yes.
In Blixt Wallet 0.6.3 (and an attempt in 0.6.2), we addressed some lnd channel pruning issues, where lnd would mark too many channels as “not suitable for payments”.
This has been causing payment issues for users as the pathfinding has less channels and nodes to work wth.
You can read more about our findings in the changelog for 0.6.2 and 0.6.3
https://github.com/hsjoberg/blixt-wallet/releases/tag/v0.6.2
https://github.com/hsjoberg/blixt-wallet/releases/tag/v0.6.3
Any installation running 0.6.3 and newer has this fix.
But if you had Blixt Wallet installed before that, you will unfortunaetly have to reinstall Blixt in order for the fix to properly work for all channels that has already been pruned.
Here’s a step-to-step guide:
https://blixtwallet.github.io/faq#pruned-zombies
So in order words, reinstalling Blixt (remember to save the seed and close channels) will make your Blixt work a lot better.
But I understand if this is a bit cumbersome.
#[0] guys… why do you only support payouts to Wallet of Satoshi and Alby?
This is completely unecessary and is very harmful for LN decentralisation.
Please support payouts to any Lightning Address.
#[1]
Rolling 🎲🎲.....
.............|
.......🎲|
.....🎲..|
Results!
⬜️⬜️⬜️⬜️⬜️⬜️⬜️ ⬜️⬜️⬜️⬜️⬜️⬜️⬜️
⬜️⬛️⬜️⬜️⬜️⬛️⬜️ ⬜️⬛️⬜️⬜️⬜️⬛️⬜️
⬜️⬜️⬜️⬜️⬜️⬜️⬜️ ⬜️⬜️⬜️⬜️⬜️⬜️⬜️
⬜️⬛️⬜️⬜️⬜️⬛️⬜️ ⬜️⬜️⬜️⬛️⬜️⬜️⬜️
⬜️⬜️⬜️⬜️⬜️⬜️⬜️ ⬜️⬜️⬜️⬜️⬜️⬜️⬜️
⬜️⬛️⬜️⬜️⬜️⬛️⬜️ ⬜️⬛️⬜️⬜️⬜️⬛️⬜️
⬜️⬜️⬜️⬜️⬜️⬜️⬜️ ⬜️⬜️⬜️⬜️⬜️⬜️⬜️
Total: 11
Payout: 3000 sats!
We support payouts to walletofsatoshi.com and getalby.com lightning addresses. Please respond with your walletofsatoshi.com or getalby.com lightning address and we will pay you out there.
Once confirmed, your lightning address will be saved for future games so payouts will be automatic!
Verifiably Fair:
Our games are verifiably fair. The method for getting the result is shown in the GitHub link below.
You can run the code for yourself to verify the fairness and final result.
https://gist.github.com/NostrCasino/c9dc1a21ac419d79ed04ca171be73f97
seed_hash = '4bd8636f0b3b824cca510c84e4d80773e6e02d5aa53212f1ae9ef942cc6a1d29'
seed = b'3b570f31430729975a0adbb15c45eebac6aae39f50b4fd634f6c41f00a8403462df677a5c1cd62bb70e95b5a35e44d61018860f2c585a303e2c46ee3587cb2c3'
signature = '07fb6102832148679f660310a849954e06bdec05317b85e10cec1611b5e65df4161f79fdfc79eb3f7f5770933a697bdb808c9a30eecabaecad37e68e02e2998c'
hampus@blixtwallet.com
#[1] Starting simplified craps game for 1000 sats!
Steps to play:
1. Pay the invoice below
2. Reply to this comment with either:
'roll' or 'shoot'
3. A fair dice roll (two six-sided dice) will occur based on your comment signature.
lnbc10u1pjpvxlgsp5p0rufjds0x4mw7m0ael4za8laxzv2qp4fujflged8aa8d86sym6qpp5mygxgdy05az2cr2vp3vdyrn9h0d08f704fa6d6t7hs9dhd6q90tsdpyvdexzurnypnkzmt98gsrgcny8qmrxdnxxp3qxqyjw5qcqpjrzjq07wze2n0t4pyzllapg9sa45f4g3jd20sfdnatpjndmpl3trd0engzm6duqqdcqqqyqqqqqqqqqqqzqq9q9qyysgqyqs33qfdz675qqhg2ahzrdfdeghfs6w0wzs83w6cf2gz2yqv5avymfs696wcft2ngwxdpuz29aak4gd47ls5hwlp23mx2uy4jpxw52qqsmy27t
The payouts are as follows:
Roll: 2, payout: 4x1000 = 4000 sats
Roll: 3, payout: 2x1000 = 2000 sats
Roll: 4, payout: 2x1000 = 2000 sats
Roll: 10, payout: 3x1000 = 3000 sats
Roll: 11, payout: 3x1000 = 3000 sats
Roll: 12, payout: 6x1000 = 6000 sats
Roll: 5, payout: 0x1000 = 0 sats
Roll: 6, payout: 0x1000 = 0 sats
Roll: 7, payout: 0x1000 = 0 sats
Roll: 8, payout: 0x1000 = 0 sats
Roll: 9, payout: 0x1000 = 0 sats
Our games are verifiably fair. The method for getting the result is shown in the GitHub link below.
You can run the code for yourself to verify the fairness and final result.
https://gist.github.com/NostrCasino/c9dc1a21ac419d79ed04ca171be73f97
seed_hash = '4bd8636f0b3b824cca510c84e4d80773e6e02d5aa53212f1ae9ef942cc6a1d29'
roll
#[0] 1000
Around 3-6 lightning peers is normal and enough.
It will help you have an up-to-date LN channel and node database.
I had to put down the Blixt node for some time yesterday, perhaps that is the reason why it didn’t work yesterday?
Also, please check Settings -> Show network info under the Lightning Network category.
What is the number of zombie channels being reported?
For sure!
I’m well aware of the enthusiasm surrounding this feature. ⚡️
⚡️ 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.
Cheers!
Yes I’ve seen a couple of payments popping up in my Blixt Wallet, courtesy of #[4]
A couple of releases left, but we are approaching Blixt Wallet v0.6.9-420, which will include some great stuff for y'all. ⚡️🟡
Does it still not work?
Still wrapping my head around the description_hash affair with Core Lightning (see https://twitter.com/callebtc/status/1635216854577991681 by #[0] ), but as much as I understand the devs concerns, it seems to me that bolt11 makes it quite clear that it is the lightning implementation's responsibility to check that the description and its hash match.
https://github.com/lightning/bolts/blob/master/11-payment-encoding.md?plain=1#L215
No. It says it must be checked through “some unspecified means”.
This unspecified means in practice always means the LNURL-pay server.