pull down to refresh
That's helpful information, thank you.
If LND is at 0 and you're connected to your own Pub via the nprofile then it is in bootstrap mode, it will open an outbound channel automatically once the balance is sufficient. The only cost then is the chain fee for the channel, no lease.
We created CLINK as a superior protocol to NWC, if using with Nostr what you're looking for it's bxrd.app support it.
Definitely rough edges as we're still focused on driving innovation and a comprehensive ecosystem as part of that, wallet is getting pretty mature now though and polish is coming. Wallet is just one part, Pub, Bxrd, LV, CLINK, Sanctum... all primatives to a bigger vision intending to work better than the ad-hoc disjointed projects the ecosystem is stunted by... the trade-off for that being our dev effort bounces around to each component over a long time horizon.
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?
Just pushed a probable fix for this, see if it works now after a hard refresh
did 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
Pub seems to be crashing in a restart loop, likely unrelated to CLINK...
More detailed logs from Pub might explain why, let me know the output of this:
journalctl --user-unit lightning_pub -f
Thanks
Looks like the node restarted while a payment was stuck and triggered a sanity checker that monitors db consistency, just pushed a fix for that edgecase... if you re-run the pub install script it should gracefully update and restart.
should I
systemctl stop lnd and lightning\_pub?and then run
wget -qO- https://deploy.lightning.pub | bashbxrd.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 ...