I got your 30 sats but zapping and receiving zaps are unrelated.
Just a minute ago I was able to zap your lightning address and zap your most recent post (15 and 21 sats respectively).
My guess is that during the time when you were having trouble receiving zaps there was a lightning node in the path between your node and my node that was down.
What is the website where pump and dumpers make short term memecoins and do stunts to promote them on a live stream?
Glad to have you here!
Yeah, a #Bitcoin node and Electrs are plenty on a Pi. I used a Pi years ago and thought it wasn't adequate then.
Okay but one devil might not keep his promises and will otherwise ignore us while the other devil would have actively persecuted us.
Any reason for the wild price action over the last 24 hours or so? I assume it's just related to the inauguration and #Bitcoin Strategic Reserve speculators.
We don't typically see these quick 5% swings anymore.
I'll be joining you soon, just started up the pot.
#coffeechain ☕
I've used Electrumx for years. I used to run it as a public server but now I just run it for myself. It works great. I wouldn't call it light weight however. I think typical people run Electrs for personal Electrum servers.
Fulcrum is supposed to have the best performance but it also uses the most from a resource perspective.
Welcome! Glad you're here my friend.
The part where exchanges have to report your cost basis has been delayed for a year. The per-wallet tracking for individuals is still required for tax year 2025. Ironically as I'm talking about the fact that I knew about the tax changes because of X, X also caused a ton of confusion thanks to clout chasing influencers who confused people by reporting that ALL changes were delayed. Here is a helpful writeup on the changes and what hasn't changed:
https://coinledger.io/blog/is-the-irs-delaying-crypto-tax-reporting-requirements-until-2026
You are correct that these changes are intended as a back door way to ban self custody by making tax reporting more difficult.
The part where exchanges have to report your cost basis has been delayed for a year. The per-wallet tracking for individuals is still required for tax year 2025. Ironically as I'm talking about the fact that I knew about the tax changes because of X, X also caused a ton of confusion thanks to clout chasing influencers who confused people by reporting that ALL changes were delayed. Here is a helpful writeup on the changes and what hasn't changed:
https://coinledger.io/blog/is-the-irs-delaying-crypto-tax-reporting-requirements-until-2026
Extremely proud of this installation. Two S19K Pros replaced a furnace today. Go to http://256heat.com if you are interested in getting paid to heat your home. 
Great setup.
I tried to zap but it didn't work.
I get that I should just delete it entirely, and I've been close for a long time, but I'm not sure I can get all the into I need from just Nostr and nostr:nprofile1qqstnffh2gam5t7d46zhmyxc5asdunep88yljrvcda68ee7sasx3w0gpz9mhxue69uhkummnw3ezuamfdejj7qg4waehxw309aex2mrp0yhxgctdw4eju6t09uq3wamnwvaz7tmjv4kxz7fwdehhxarj9e3xzmny9upwsw84.
I would have biffed the safe harbor tax nonsense for example.
In solidarity with those that are waking up to find that TikTok is no more, I have logged out of X.
It is pretty cool to look at a #payjoin transaction with a block explorer and see that it completely breaks the "common input ownership heuristic". When I setup my #btcpay server I tested it with Wasabi which was one of the wallets that supported payjoin sending at the time (there are quite a few wallets that support payjoin send now). It works but of course with payjoin v1 you need to have a publicly accessible btcpay server to receive. The new payjoin v2 sounds like it's much more accessible for non-server runners to be receivers.
The end of another era:
Due to nostr:nprofile1qyt8wumn8ghj7etyv4hzumn0wd68ytnvv9hxgtcppemhxue69uhkummn9ekx7mp0qydhwumn8ghj7mn0wd68ytf39ehxymewv9hxwctwdyhxxmcpr4mhxue69uhkummnw3ez6ur4vgh8wetvd3hhyer9wghxuet5qy08wumn8ghj7mn0wd68yttsw43zuam9d3kx7unyv4ezumn9wshszynhwden5te0wp6hyurvv4cxzeewv4esz9rhwden5te0wfjkccte9ejxzmt4wvhxjmcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsz9nhwden5te0wfjkccte9ehx7um5wghxyctwvsq3wamnwvaz7tmjv4kxz7fwdehhxarj9e3xzmny9uq3vamnwvaz7tmjv4kxz7fwwpexjmtpdshxuet5qyvhwumn8ghj7un9d3shjtnndehhyapwwdhkx6tpdshsqgzx2l0739jmazvq4yc8908mtev6v5fygpkmp7qey90w0zay0y6t8ccesg0j winding down its custodial wallet today, we are looking to empty out our Zap Wallet before switching.
The first 21 reposts or likes get 210 sats. Go!
Nostr-only 🧡
Thank you (if I get one of the zaps)!
For anyone that stumbles on this while trying to resolve an issue I ran this command:
dnf list --installed
dnf tells you the method by which a package on your system was installed. In the case of the problimatic containerd package it was installed via command line (I assume I manually installed an RPM package).