pull down to refresh

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

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?

reply

Excellent

The rugpull detection is Pub's internal wallet to the bootstrap node saying it can't communicate with the remote Pub (ours) or that there's a discrepency.

Comms are working now but there's a delta of 18 sats, will look into that, it may be from the earlier comms issues + stuck payment... shouldn't be blocked from working though. Worst case I'll have you DM your nodes npub and we can patch from our end.

reply
20 sats \ 3 replies \ @wilto 12 May

thanks, last payment is still in status 'pending' ... but it works, that is the most important part ; the issue appeared after I tried paying through bxrd.app first payment went fine but there was a discrepency of 18 at that point, I tried a second payment via bxrd, it did not go through (or there was something weird), and a third one from the shockwallet.app (which is now stuck)

Thanks for all the advices, great help!

reply

that might be it, if the payment is stuck the bootstrap peer debited it but hasnt confirmed it paid yet, if its truly stuck and reverts it will re-credit

reply
8 sats \ 1 reply \ @wilto 12 May

the wallet destination has not received the payment

how to revert it?

reply

it's a "stuck" payment in lightning nomenclature, so it'll expire, once it expires bootstrap peer would get its sats back, then re-credit your pub, which should quiet the rugpull tracker

reply