pull down to refresh

should I

systemctl stop lnd and lightning\_pub?

and then run

wget -qO- https://deploy.lightning.pub | bash

the script alone should restart services

reply
reply

good news, thats further along and a different issue

bad news is our relay is under DoS, but I just got a mitigation in place, relay is working now... will push a fix for this crash shortly... you'll need to re-run script again to update once I do... will keep you posted

reply

Thanks Justin, will wait

Was wondering which relays are setup in bxrd.app ; could not find the relay list in the bxrd settings

reply

will expose this in the UI soon so you can add others and see connection status

const DEFAULT_PUBLIC_RELAYS = [
    "wss://nos.lol",
    "wss://relay.damus.io",
    "wss://relay.primal.net",
    "wss://nostr.bitcoiner.social",
    "wss://relay.snort.social",
    "wss://relay.nostr.band",
    "wss://purplepag.es",
    "wss://nostr.mom",
    "wss://relay.ditto.pub",
    "wss://relay.mostr.pub",
    "wss://nostr-pub.wellorder.net",
    "wss://relay.bxrd.app",
    "wss://nostr.land",
    "wss://relay.momostr.pink",
    "wss://offchain.pub",
    "wss://nostr.oxtr.dev",
    "wss://relay.current.fyi",
    "wss://relay.nostr.bg",
    "wss://relayable.org",
    "wss://nostr.orangepill.dev",
    "wss://nostr.fmt.wiz.biz",
    "wss://brb.io",
    "wss://nostr.data.haus",
];
reply

oh since the relay is working now, is pub restarting ok? havent pushed fix yet but the crash is related to the bootstrap comms because of the relay issues that were happening

reply

pushed another Pub patch

reply

it works

$ journalctl --user-unit lightning_pub -f -q
May 12 21:10:46 debian12amd64 bash[27537]: 2026-05-12 21:10:46 StorageProcessorQueue >> pushing to queue 0
May 12 21:10:46 debian12amd64 bash[27537]: 2026-05-12 21:10:46 StorageProcessorQueue >> done write
May 12 21:11:14 debian12amd64 bash[27537]: 2026-05-12 21:11:14 StorageProcessorQueue >> pushing to queue 0
May 12 21:11:14 debian12amd64 bash[27537]: 2026-05-12 21:11:14 StorageProcessorQueue >> done write
May 12 21:11:30 debian12amd64 bash[27528]: 2026-05-12 21:11:30 rugPull >> detected rugpull from:  76ed45f00cea7bac59d8d0b7d204848f5319d7b96c140ffb6fcbaaab0a13d44e provider balance changed from 36443 to 36425 losing -18
May 12 21:11:30 debian12amd64 bash[27528]: updating tracked balance: 36443
May 12 21:11:37 debian12amd64 bash[27537]: 2026-05-12 21:11:37 StorageProcessorQueue >> pushing to queue 0
May 12 21:11:37 debian12amd64 bash[27537]: 2026-05-12 21:11:37 StorageProcessorQueue >> done write
May 12 21:12:30 debian12amd64 bash[27528]: 2026-05-12 21:12:30 rugPull >> ongoing rugpull from:  76ed45f00cea7bac59d8d0b7d204848f5319d7b96c140ffb6fcbaaab0a13d44e provider balance changed from 36443 to 36425 losing -18
May 12 21:12:30 debian12amd64 bash[27528]: updating tracked balance: 36443

what does that line "rugPull >> ongoing rugpull from" mean?