Having fun learning blockchain and stuff . I find self in the same predicament and decided to manually move my blockchain file on a drive instead of copy across network to another new PC . That worked. The goal is to play and send mojo between one wallet and another, and have 2 different full_nodes.
Sorry in advance to ramble, but Im trying to understand the why not the how.
Here at start of July , my sql lite file (mainnet/db/block*.sqlite ) is about 6GB on my main node. I periodically copy my mainnet dir off to another HDD as a backup because the thought of having to re-sync from scratch would take what … a week (?) I find my wallet db file ( mainnet/wallet/db/block.sqlite ) is 3GB (? … wtf … why ? ). So the problem of sync just moved from the blockchain file to the wallet file.
I assume that my / our blockchain db file only holds a portion of all the global transactions, it appears to download all the heights from beginning of March 2021. So I gather that earlier adopters with sync’d blockchain DB files are going to be holding up the network in perpetuity … that sort of makes sense.
But still wondering
- How big that mainnet db file will grow, what happens when the transaction volume takes off ? I cant forsee my home PC being able to keep up when Chia becomes the backbone of the crypto universe ( sarc ).
- are other blockchains this slow to sync on a new node ?
- now what about the wallet DB file …
I assume there’s no shortcut for copying the wallet DB from one source to another, if they are different wallets. So, why would a new, fresh wallet DB need to sync ? … There are no transactions in the new wallet. It is currently at height 72 K and I assume will need to sync up to the height of 530k and 3GB (?) . That part makes no sense. I find I need the full_node daemon and the wallet daemon to run minimally on PC2, its connected back to my mainnode:8444, the mainnet DB file is synced ( I copied it ), but the empty wallet is still way behind. After about 4 hrs its at height 230K so about 1/2 way done …