I believe my zapper is now back in service after upgrading to
new hardware multiple times.
1st hardware upgrade attempt MeerKat from system76
  USB would loose power after 24 hours of run-time.
  Only discovered after completing a full migration.
  Return the hardware after retreating to old hardware.
2nd hardware upgrade attempt desktop from Velocity Micro
  Issue with graphic card.
  returned next day after receiving
Current hardware upgrade desktop from system76
  Did a one week burn-in before doing any migrations.
  no issues so far.
Now three months or so later, I've updated the local instance
of albyhub and opened a new LSP channel with Olympus by Zeus.
Here is the ablyhub upgrade process that worked for me.
Download current release and manifest files
  Navigate to 
  Download albyhub-Server-Linux-x86_64.tar.bz2
  manifest.txt
  manifext.txt.asc
-------------------------------------------------------------
Copy the downloaded files to $HOME
  mv $HOME/Downloads/albyhub-Server-Linux-x86_64.tar.bz2 $HOME
  mv $HOME/Downloads/manifest.txt $HOME
  mv $HOME/Downloads/manifest.txt.asc $HOME
---------------------------------------------------------------
Verify manifest signature & Checksum
  Only need to import once
  curl 
  gpg --verify manifest.txt.asc manifest.txt 
  shasum -a 256 albyhub-Server-Linux-x86_64.tar.bz2
  The above checksum should be referenced in the file, manifest.txt.
  cat manifest.txt
----------------------------------------------------------------
Stop AlbyHub & Backup existing data
  systemctl stop albyhub
  cp -r $HOME/.local/share/albyhub /media/veracrypt1/albyhub 
  cp $HOME/bin/albyhub $HOME/bin/albyhub114 
  cp -r $HOME/lib $HOME/lib114
----------------------------------------------------------
Extract new release Binaries & Start AlbyHub
  tar -xvjf albyhub-Server-Linux-x86_64.tar.bz2
  ./
  ./lib/
  ./lib/libldk_node.so
  ./bin/
  ./bin/albyhub
  systemctl start albyhub
----------------------------------------------------------------
Login and open new private channel
  Navigate to