In case you missed it: I published a guide on setting up non-custodial zaps using Raspiblitz and LND:
Would be cool if it updated the channeldb backup file anytime it was necessary to update it.
It’s a custodial wallet. They own the private keys to the wallets you are using. Meaning they have the ability to spend those funds.
You would need to use a non-custodial wallet that keeps your private keys on device. There are several good ones, but none of them support Lightning addresses for receiving “zaps”. I recommend Phoenix wallet to those unfamiliar with non-custodial Lightning wallets.
If you want to receive zaps non-custodially, you’ll need to run your own LN node and setup LNURL (not very straightforward at the moment, but I did write up a guide for how to set this up on a Raspiblitz if you already have an LND node running on it):
Would like to see an option for simply saving a local backup on device and keeping that backup file synced.
The fact that it’s even possible for them to rug you should give you concern.
Why even risk it?
Heard good things about Blixt. Currently running my own node via Zeus and Phoenix wallet as a secondary wallet.
Are there any downsides to Blixt when compared to Phoenix?
Dunno if it’s possible with them
Get your sats out of BlueWallet’s custodial Lightning wallet before you get rugged:
Which nostr client & ln wallet are you using?
The $100 cash is still in your possession
Sats in WoS are literally cucked sats that another man owns
Never accept tradeoffs that include the possibility of a rug pull
Does your wife’s boyfriend know you’re using Wallet of Satoshi?
Self-sovereign Lightning Address guide just dropped: https://sovrnbitcoiner.com/receiving-self-sovereign-zaps/
Among the worst shitcoins I’ve ever seen tbh
Thanks Seth! Nice write up!
If you haven't yet done NIP-05 identity verification, no need to jump on solutions that do it for you.
I've put together the simplest possible self-hosted NIP-05 verification setup I can think of. Just get the cheapest VPS you can, clone the repo, edit 2 files slightly, and run one command and you'll have an always-on, always up-to-date, properly certified NIP-05 identity endpoint:
https://github.com/sethforprivacy/easy-nip5
Detailed steps are all in the readme at the above repo.
Feedback welcome!
Can you update the guide so that instead of the NIP-05 verification being in the format of name@domain.com, it's just domain.com?
Orange Surf did it in his guide here: https://orange.surf/nip05-with-ghost/