pull down to refresh
142 sats \ 0 replies \ @k00b OP 9h \ parent \ on: “Localhost tracking” explained. It could cost Meta 32 billion. security
use signal?
Elvis wrote a post that got quite a bit of discussion a time ago: The dead internet vs the Lightning network
If you have disabled sending wallets, you should be good to go zapping CCs/reward sats.
Any problem you encounter while doing that is a bug, and there's nothing you need to do to fix it. Sometimes zaps in the UI glitch like you describe. Refreshing usually fixes it.
I think that's what this post is trying to get at, right? You're good to go.
If you have a non-working sending wallet attached, disable it (check disable box and hit save) and you can zap CCs with your reward sats.
We can't know in advance that your sending wallet will misbehave. If it's attached and enabled, we try to use it to pay for zaps still.
I saw this a awhile ago but couldn't figure out any details about how it works. The website tells me what it does (roughly), but they seem to expect us to trust them.
I suspect this one of those vaults with a bunch of presigned txs, else a multisig covenant.
Hardly anyone really uses the existing rail that goes north, but if had more routes like this maybe it will change.
Also Yud's stylist is reading this: either get him better hats or have him stop wearing them. Be brave and bald I say.