True. I'd like it to arrive quickly in LND as well. In the meantime LNURLpay over Tor reduced the barrier to entry to use a self-hosted node here or anywhere a static QRcode can work.
Find here a guide to host an LNURLpay code over Tor with you own BTCPayServer:
https://gist.github.com/openoms/9be181ffba14afcfb458cd3e1d726b5e
Help on the lightning wallet front is much needed. Ask all your favorites to add support or help them if possible (FOSS wins).
Improved version reencoded with a http:// prefix and skipping nginx:
lnurl1dp68gup69uhnwarswcehjmnpdf4hvdnrv3hkxmt6d96xxep50gehsunnw3crx6trxeu8ga34daknxerrxfhx2epnvenxvmrvx4ckgtn0de5k7m309emk2mrv944kummhdchkcmn4wfk8qtm0de5k7mn5d9cq045u4j
7tpv3ynajkv6cdocmzitcd4z3xrstp3ic6xtv5om3dc2ned3fffll5qd.onion/.well-known/lnurlp/oniontip
Researching LNURL on an onion domain.
Can anyone pay this LNURL in three different formats? please tell which wallet you use if works
lnurl1xa68qa3n09hxz6ntwcmxxer0vdkh56t5vdjrg73n0pe8xarsxd5kxdncw3mr2mmdxdjxxvnwv4jrxenxvekxcdt3vshx7mnfdahz7tnhv4kxctttdehhwm30d3h82unvwqhk7mnfdah8g6tsn474jp
oniontip@7tpv3ynajkv6cdocmzitcd4z3xrstp3ic6xtv5om3dc2ned3fffll5qd.onion
7tpv3ynajkv6cdocmzitcd4z3xrstp3ic6xtv5om3dc2ned3fffll5qd.onion/.well-known/lnurlp/oniontip
If you come to Advancing Bitcoin pop in to the node workshop on Friday to discuss why you should run a Bitcoin node, take them apart, look inside and get all the tips to build yourself.
Until then they will keep stressing the hotel wifi with the sudden Tor traffic.
I think it depends on Android, because I also have Nostros installed and it doesn't show bbw either as a send option. Bbw is installed via playstore.
I also checked if I can change to open compatible links in it's settings, but there it's toggled active already which is the default.
https://play.google.com/store/apps/details?id=com.galoyapp
Thanks for trying. It might be that installing a new #[5] soon will solve this.
It is also dependent on Android in some way I couldn't work out yet.
For example this is on GrapheneOS when I click a zap icon in Amethyst.
Installed the test version of #[3] from the sandboxed Play Store.
Amethyst from F-droid / Neo Store.
How did you install BBW?
Seems that it does not yet work perfectly, but at this pace we are getting there fast.
@npub1mnjer84a6f7hn7deuvuzxm4kfcuermxpdfn75tuwwqdpn0phejsqqn7dm good sir you need an LNaddress in your profile too.
With zaps now the whole nostr is like stacker.news.
Now working with #[0] lightning addresses as well.
This new space is like an endless hackathon.
Confirmed that it is fairly easy to have the NIP5 verification link and the LNaddress on the same domain even when using BTCPayServer and hosting a website on the root.
Nginx snippets I used:
https://github.com/openoms/bitcoin-tutorials/blob/master/nginx/nostr_lnaddress_snippets.conf
https://void.cat/d/Cx5gGpLL5iP3R8PUdRavxY.webp
Now only email doesn't work there, but I'll just skip that.
Setting up NIP5 is easy and takes 2 minutes. Thanks #[0] for the quick guide: https://nvk.org/n00b-nip5
All I can add that I used the https://nstr.cloud/key.html to transform my npub to hex and yes github does complain, but can also use a subdomain.
To make it even faster you can fork this: https://github.com/openoms/nip5
A little bit more hacking and now my NIP5 identifier is the same as my LNaddress:
openoms@pay.diynodes.com
The nginx snippet used in the redirect to btcpayserver serving the lnaddress:
location /.well-known/nostr.json {
add_header 'Access-Control-Allow-Origin' '*';
alias /var/www/html/.well-known/nostr.json;
}
Next step to move both to the root domain.
FYI #[1]
Setting up NIP5 is easy and takes 2 minutes. Thanks #[0] for the quick guide: https://nvk.org/n00b-nip5
All I can add that I used the https://nstr.cloud/key.html to transform my npub to hex and yes github does complain, but can also use a subdomain.
To make it even faster you can fork this: https://github.com/openoms/nip5
Using the #Raspiblitz dev branch (can sync to it from menu - UPDATE - PATCH) the #lnproxy api and gui is available as a server.
Exposed via SSL and Tor.
Can also subscribe to a custom #IP2Tor to get a clearnet endpoint.
Testers are very welcome before the next major release.
Try to set in the lnd.conf:
debuglevel=debug
db.bolt.auto-compact=true
restart and monitor the logs for the compaction or any error until comes back up. Lower it the debuglevel to info afterwards.
If you use watchtowers check if they are connectable, the Info forbthe offline ones queeing up can also cause high memory usage.
Start on http://raspibolt.org and you can end up here: https://gildedpleb.github.io/hab-guide/poc
h/t: https://twitter.com/gildedpleb
Started to experiment with lnproxy on the #Raspiblitz: https://github.com/rootzoll/raspiblitz/pull/3637
Using it already as a gateway node:
can hide the pubkey of any nodes behind one that is already known.
For a public service follow the privacy best practices:
Tor-only, channels from peers, coinjoin.
Lnproxy's pubkey here: npub1ufdgkgz3qg4q37taye75hxwal3gq5zl7zjd97ec7gmmja84rdmyspmzcue
yes, can only run on LND currently, but can warp any BOLT11 invoice.
gas moving on Amethyst 👍
A better workflow probably would be a BtcpayServer plugin to be able to set some preferred proxy nodes to wrap invoices automatically on request.
Could rotate and randomize through the given list of nodes too.
The setting should be server side, not for the payer to choose from.