Raspiblitz (ADMINS DO NOT DM | WATCH OUT FOR SCAMMERS)

How to update core lightning? Is a new release of raspiblitz imminent?

Ok. So it is sure only clearnet outbound is affected? Edit: if I get autoblitz correctky, it is the other way round. Only tor affected. It s confusing.

This apparently only affects older Albyhub versions thigh, so I think Raspiblitz should not be affected

The point is to stop new peers connecting and opening channels. keep both clearnet and/or Tor outbound only.

Yeah, i got that. But I don t get how to set it on not raspiblitz node.

@auto_blitz_bot how to avoid advertising p2p endpoints of CLN

To make CLN outbound-only (nothing advertised, no inbound P2P) on any node: 1. Edit the config (e.g. ~/.lightning/bitcoin/config or your cln.conf) and remove / comment out every line with: • bind-addr= (no listener = no inbound connections) • announce-addr= or the old addr= (no gossip announcement) 2. For Tor outbound only, add: proxy=127.0.0.1:9050 always-use-proxy=true (if you want clearnet outbound as well, just omit always-use-proxy and it'll use direct connections too) 3. Restart lightningd. 4. Verify with lightning-cli getinfo — the address array should be empty. With nothing to announce, your node disappears from gossip, so no new peers/channels will come in, while your existing channels and outbound opens keep working. Caveat: a public node that already announced addresses keeps a legacy announcement in the graph for a while; after the config change it stops being refreshed and fades out.

Show in a codebox the relevant config entries clearly

Sure — example ~/.lightning/bitcoin/config for an outbound-only, non-advertising CLN node: # ---- REMOVE / comment out anything like these if present: ---- # bind-addr=0.0.0.0:9735 # bind-addr=[::]:9735 # announce-addr=yournode.ddns.net:9735 # announce-addr=abcdefghijklmnop.onion:9735 # addr=statictor:127.0.0.1:9051/torport=9735 # ---- Outbound-only over Tor: ---- proxy=127.0.0.1:9050 always-use-proxy=true Notes: • No bind-addr → lightningd opens no listening socket, so no inbound P2P at all • No announce-addr → nothing is gossiped to the network • always-use-proxy=true forces all outbound connections through Tor too, so your IP stays hidden from peers • Verify after restart with lightning-cli getinfo → "address": [] should be empty

How about LND?

Same idea for LND (lnd.conf) — outbound-only, nothing announced: [Application Options] # no inbound listener at all: nolisten=true # no UPnP / NAT-PMP address discovery (this is what lnd would otherwise announce): nat=false # REMOVE / comment out if present: # externalip=yournode.ddns.net:9735 # externalhosts=... [Bitcoin] bitcoin.node=bitcoind [Tor] # outbound over Tor (socks proxy): tor.active=true tor.socks=9050 tor.streamisolation=true # do NOT enable tor.v2/tor.v3 — those create an onion service = inbound endpoint Notes: • nolisten=true → lnd opens no listening port, no inbound peers • nat=false + no externalip → nothing gets gossiped • tor.active routes outbound connections through Tor so peers don't see your IP • Verify after restart with lncli getinfo → "uris": [] should be empty • Same caveat as CLN: previously announced addresses linger in the graph for a while but stop being refreshed

⚠ CLN: disable --experimental-dual-fund if you have set it https://github.com/ElementsProject/lightning/issues/9498 https://x.com/evankaloudis/status/2099582283409674260

I'm on Raspiblitz 1.12.1 using AlbyHub. Since a few days (I don't check daily), the only channel I had to connect myself isn't active anymore, my on-chain funds are sitting there. Albyhub says "Could not connect to relay". Ofc I would like to avoid having to open a new channel. Did anyone already experience this or is there a way to fix it w/o having to open a new channel again? I don't even understand why the channel was closed, I'm online 99% of the time

@auto_blitz_bot is this a general lightning problem

Yes and no — two different things are getting mixed here: 1️⃣ "Could not connect to relay" — that's a Nostr relay error (NWC), not Lightning. It just means AlbyHub can't talk to its relay. Annoying, but it doesn't close channels. 2️⃣ Channel inactive + on-chain funds — that's the real part, and yes, it's a general Lightning thing, not RaspiBlitz-specific. If the channel shows funds back on-chain, the counterparty (your LSP/peer) most likely force-closed. You being online 99% doesn't prevent that — the other side can close unilaterally (fee spikes, LSP policy, their node issues). After the timelock expires the funds land in your on-chain wallet automatically. To check what actually happened, on the RaspiBlitz: LND: lncli closedchannels → look at close_type (REMOTE_FORCE_CLOSE / LOCAL_FORCE_CLOSE / COOPERATIVE_CLOSE) and lncli pendingchannels for anything still maturing. CLN: lightning-cli listpeerchannels / listclosedchannels. If it was force-closed, there's no way to "reopen" that channel — the funds are safe on-chain, but a new channel is the only way back. Nothing you did wrong, and not a 1.12.1 bug.

Same now "official"

Hi guys, some medium size node operator is interested in sharing with my node the watchtower? I need one or 2.