Ligess is a self-sovereign Lightning Address and Zap (NIP-57) server:

GitHub

GitHub - Dolu89/ligess: Personal Lightning address server

Personal Lightning address server. Contribute to Dolu89/ligess development by creating an account on GitHub.

To use it you need: * an always on lightning node (eg. a Raspiblitz) * a (sub)domain under your control * a VPS with a public IP address to avoid exposing the location of your node A 5 minute guide to set up with your own node:

GitHub

bitcoin-tutorials/nostr/ligess.md at master · openoms/bitcoin-tutorials

Documenting Bitcoin related setups using LND, JoinMarket, RaspiBlitz, Debian and Ubuntu - openoms/bitcoin-tutorials

H/t #[0] for adding the Zap support You can try it by zapping this post ;)

Are we getting ⚡ competition with #FedNow? (Don't think so, it looks like just another quick wire system like UK Faster Payments or SEPA instant in the EUR zone) That name though 🤣

I realized now that jumping between clients something made me loose my follow list. Is there a good way to back the list up once I get it together again? Know about nost.directory to add the twitter contacts, but woul like something I can keep locally.

Find here a guide to host an LNURLpay code over Tor with you own BTCPayServer:

Gist

LNURLpay over Tor

LNURLpay over Tor. GitHub Gist: instantly share code, notes, and snippets.

Help on the lightning wallet front is much needed. Ask all your favorites to add support or help them if possible (FOSS wins).

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.

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.

Setting up NIP5 is easy and takes 2 minutes. Thanks #[0] for the quick guide:

NVK.org | How to setup NIP5 verification using Github Pages

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:

GitHub

GitHub - openoms/nip5

Contribute to openoms/nip5 development by creating an account on GitHub.

Start on

RaspiBolt

Home

Build your own ‘do-everything-yourself’ Bitcoin full node. No need to trust anyone else.

and you can end up here:

HAB Node Proof of Concept | HAB Node

Technical design considerations and specifications for the Proof of Concept

h/t:

X (formerly Twitter)

Gilded Pleb (@gildedpleb) on X

“With the measure you use, it will be measured back to you—and more"

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

There should be many more nodes running

GitHub

lnproxy - Overview

dev of lnproxy. lnproxy has 19 repositories available. Follow their code on GitHub.

and apps have a selection of proxy nodes to receive through.

#[0] Verifying My Public Key: "openoms"

#[0] Verifying My Public Key: "openoms"

#[0] Verifying My Public Key: "openoms"