[xud-backup] Backup & Restore TOR data + xud.conf

[kilrau]

• [ ] backup daemon should backup

  drwx------ 3 root   root    4096 Feb 26 20:24 tor
  drwx------ 3 root   root    4096 Feb 26 20:27 tor-data
  -rw-r--r-- 1 root   root    2183 Feb 26 19:51 xud.conf

• [ ] restore should be able to restore these. Test: all TOR URI's stay the same, and xud.conf with e.g. infura keys too.

[kilrau]

@michael1011

[sangaman]

I can somewhat understand backing up the xud.conf file, backing up configuration is uncommon afaik but it wouldn't hurt and it would be simple to add.

I don't understand backing up the tor/tor-data folders, what's the purpose here? I also don't know where those directories will exist, would there be permissions concerns?

[erkarl]

I don't understand backing up the tor/tor-data folders, what's the purpose here?

This is to ensure that the restored node gets the same hash.onion URL.

I also don't know where those directories will exist, would there be permissions concerns?

I think this issue belongs to xud-docker repository as the paths there are known and there will not be permission issues.

[sangaman]

This is to ensure that the restored node gets the same hash.onion URL.

Is this important? What would be the harm in using a different tor address?

[kilrau]

I see people publishing their xud uris on websites like we currently see happening with lightning. At least always-on market makers and service providers which have their uris as seed node entry in xud would not want their xud onion uri to change.

But agree that this only becomes important after the OpenDEX network reaches a certain size, hence agree that it is not high prio. Ill move this further down the line.

[erkarl]

Is this important? What would be the harm in using a different tor address?

More like nice to have, yes. Good point.