pull down to refresh
That's a manual process for the moment, I need to work on this docs... Got doc updates staging will try to get that out this week and update the backup section
https://docs.shock.network/pub/faq
Tldr use a cron job or similar to backup the pub directory and the static channel backups from LND along with the seed (seed accessible in public dashboard)
took me a while, but I managed to backup and restore a node
there were some discoveries, for example: the arch linux install for example is quitting because it cannot install node.js ...
finished my testing in linux mint 22, now there is a little issue left: my 2 nodes balance slightly differs, and in journalctl --user-unit lightning_pub -f I see 'rugPullTracker >> detected excees from ...." How can I reconcile both balances?
Thanks for the report, tested Arch not that long ago but maybe the latest binary isn't available... is your system x64, ARM or other?
When you say 2 nodes, you have 2 nodes running from the same Pub state? There's no HA so they aren't going to be aligned, if the same LND basis is running in 2 places thats going to break channels
The rugpull tracker seems to be saying you have a higher balance than is expected, this may be if you received to the other node and the latter node isn't aware of it.
it was 'x64'
yes, I restored a node, tested it by sending a few sats then shut it down.
Then I restarted the original one, and was waiting for the balance to actualize, it never did, and I sent a few sats (thinking maybe a refresh would happen) and that's where I saw the Rugpull tracker message ...
Now both balance are both wrong - I will settle for the highest balance.
And keep the original one shutdown for good.
ok so it sounds like the sats to the restored node aren't recognized by the original node because the Pub database has no record of them since they happened elsewhere, but the bootstrap node that the rugpull tracker is referring to sees both because both used the same key with that peer
You can use those sats still but need to manipulate the database manually with something like DBBrowser for Sqlite and just increase the balance on your desired user account. To do that you'll need to shut down the Pub, delete logs/eventLogV3.csv, then edit the database.... on restart the liabilities side should be increased so you can access the additional funds on the bootstrap peer. That CSV file is a sanity check and will be re-created on the restart.
Going to reply to your wallet account thread next, but the process is basically the same...
I just started using shockwallet, and installed a ligthning pub node.
I want to know though, how to operate a weekly backup of that node (if that's necessary)
The goal, in case of disaster would be to see if I could restore the wallet