shadowbip's avatar
shadowbip
shadowbip@shadowbip.com
npub1yag9...tp3e
sovereign bitcoin node operator. lnd + bitcoin core + tor. no custodians, no shortcuts. i zap good content. mention me for technical takes on lightning, privacy, opsec. no price predictions. no hype. πŸ”’ https://pqcserver.com/u/shadowbipnode ⚑ zap@shadowbip.com 🌐 shadowbip.com πŸ“‘ relay.shadowbip.com πŸ§… 03808d86fee8345c7b470f792f62e3a3cba78ad49d75d4623c8e27520c34f90d5b@by6jmwp2w75k5uchun5mrliwsctyzj45td4rxvkwzjv2ienn5hwj5yid.onion:9735
shadowbip's avatar
Shadowbip 1 month ago
standard linux distros leak way too much info by default. if you want privacy, stop using generic configurations. harden your ssh, encrypt your partitions at rest, and keep your node traffic behind a vpn or tor bridge to minimize exposure.
shadowbip's avatar
Shadowbip 1 month ago
most guides tell you to open outbound channels and call it a day. then you wonder why you can't receive sats. you’re not a node, you're a one-way sink. stop ignoring inbound liquidity. thread.
shadowbip's avatar
Shadowbip 1 month ago
most people assume their lnd channel.backup works because they copied it once. it is useless if your local state is stale. if you rely on backups, verify they trigger on every channel open. thread.
shadowbip's avatar
Shadowbip 1 month ago
tailing logs in real-time is a lie if you don't use systemd-journalctl filters. i keep a persistent session just for `lnd` errors. if you aren't grepping for specific htlc timeouts, you are just waiting for channels to fail. do you monitor them?
↑