pull down to refresh
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!
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: 36443what does that line "rugPull >> ongoing rugpull from" mean?
Thanks Justin, will wait
Was wondering which relays are setup in bxrd.app ; could not find the relay list in the bxrd settings
should I
systemctl stop lnd and lightning\_pub?and then run
wget -qO- https://deploy.lightning.pub | bashdid some test yesterday, I think I broke it
May 12 11:09:39 debian12amd64 bash[8411]: Node.js v24.15.0
May 12 11:09:39 debian12amd64 systemd[539]: lightning_pub.service: Main process exited, code=exited, status=1/FAILURE
May 12 11:09:39 debian12amd64 systemd[539]: lightning_pub.service: Failed with result 'exit-code'.
May 12 11:09:39 debian12amd64 systemd[539]: lightning_pub.service: Consumed 22.751s CPU time.
May 12 11:09:39 debian12amd64 systemd[539]: lightning_pub.service: Scheduled restart job, restart counter is at 14.
May 12 11:09:39 debian12amd64 systemd[539]: Stopped lightning_pub.service - Lightning.Pub Service.
May 12 11:09:39 debian12amd64 systemd[539]: lightning_pub.service: Consumed 22.751s CPU time.
May 12 11:09:39 debian12amd64 systemd[539]: Started lightning_pub.service - Lightning.Pub Service.
May 12 11:09:40 debian12amd64 bash[8456]: > lnpub@1.0.0 start
May 12 11:09:40 debian12amd64 bash[8456]: > npm run clean && tsc && node build/src/index.js
May 12 11:09:40 debian12amd64 bash[8743]: > lnpub@1.0.0 clean
May 12 11:09:40 debian12amd64 bash[8743]: > rimraf build
the field "ndebit string" in wallet setting https://bxrd.app/settings
cannot be edited, when login using the nostr extension (as recommended best practice)
"Browser-extension login cannot save or use ndebit: import your nsec in BXRD
so your key can sign CLINK debit requests and encrypt the wallet link."
Hopefully there will be a workaround, or is this technically impossible?
bxrd.app
thanks for these explanation
found the wallet setting in https://bxrd.app/settings
looking forward seeing the whole project reaching momentum
First I need to clarify that I really enjoy shockwallet,
and I've tried to understand it as much as I could on my own.
There is no equivalent out there, except Zeus, or Alby
but then they charge for inbound liquidity ...
With Shockwallet, I never managed to properly use the lnd command line, every time I tried to run lnd, I noticed it is not connected to the node because the balance is always zero. And the second thing lacking is NWC support, which would allow to use it with nostr client app.
Lastly I have to say as well that I was a bit afraid the project would be abandoned, because there are a few typos, and annoying messages (when I click to return on the homepage), which were giving me the feeling the product was not fully finalized and like many Nostr projects would stay like this ...
After many months using custodial wallets (coinos) - but I kept seeing 'not your key, not your cheese!' and saw on many occasions the wallet being offline.
Finally I decided to get into self-custodial for the benefit of being able to control the wallet, now I am running shockwallet with lightning node, and to me the critical problem is the trust I can have on the setup, how it can be recovered in case of trouble, how to restore a node, that sort of thing ...
Not a disguised ad, I wanted to learn by myself and usually AI is helping because it acts as a rubber chicken.
It is all for learning, and I am humbled that Justin took the time to answer.
I might get the funds back, that would also restore my self esteem.
Thanks for the instructions, that means I do not have to restore anything, just delete the csv and edit the user account table to reconcile the balance manually (from the old account, and to set the correct amount of sats as well)
Messing around with a lightning_pub node for shockwallet, I've lost my fund
because I wanted to reset my account (that option does not exist), and instead thought that to delete the attached source node would allow to resync the balance.
The result was that once reattaching the node, the funds were gone.
The node still exist of course, the funds are still in the node (as far as I can see from the journalctl --user-unit lightning_pub -f) but the shockwallet.app address assigned to the account is now different, so I guess that was the price of this lesson for me. It was not much but still 11K.
I asked ppq.ai for help on this and it produced this report
naddr1qvzqqqr4gupzqd3whlagjkktp2jwctc3jkd3cge6as38tasm80hwrxcmdeyjufceqy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qgwwaehxw309ahx7uewd3hkctcqz44x7e35xfpygjtt0fgnsujxxdkh5vj0de6sgqwk9d
still working on it