-
Hoping someone can confirm: btc_mainnet/wallet/backup/backups_bisq_BTC_wallet/ is still the only file needed to fully restore bisq data of wallet, txs, payment accts, disputes, ect. to new bisq instance
-
can a full bisq data restore be achieved by restoring from seed into new bisq instance ?
-
Correct that m/44’/0’/1’ and legacy addresses m/44’/0’/0’ derivation paths are only derivations used by bisq & raw wallet details and private keys ?
-
Is this also the most complete way to backup bisq instance to import into new instance
( Create a new wallet for your data directory - Bisq Wiki ) -
Guessing these btc tor nodes are special bisq tor nodes. All search results for --seedNodes=ef5qnzx6znifo3df. onion :8000,s67qglwhkgkyvr74. onion:8000 were bisq related webpages, except for a p2p integration with xmr’s Haveno. (question: is this a centralization risk having the bisq protocol reliant on 2 specific computers? )
1 & 2 are wrong.
You want to use the proper wallet folder, not the backup folder within in, and seed only restores the wallet, no the full bisq data. Just make a backup of the whole data directory to be safe.
Derivation paths are indeed those you see in the account > wallet info tab.
Network provided nodes are federated nodes ran by bisq contributors that respect minimum requirements to offer a stable connection to bisq clients.