Running the daemon without any modifications can take a long time to synchronize. Are there any faster options for synchronizing the daemon with the network?
The fastest way to achieve this, is to download the current blockchain and import it into the daemon:
Step 1: Move into the folder where you downloaded the Monero Gui Wallet, e.g:
Step 2: Download the raw block chain from a trusted source, e.g:
wget -c --progress=bar https://downloads.getmonero.org/blockchain.raw
If it fails half-way, just re-run it. The above command will continue where it left off.
Step 3: Import the downloaded blockchain into the daemon:
./monero-blockchain-import --dangerous-unverified-import 0 --input-file ./blockchain.raw
Do remember though, run with
--dangerous-unverified-import 0 only from a trusted source like the above. The option was previously called either
Step 4: You can now remove the raw blockchain to free up disk space:
rm -rf ./blockchain.raw
Step 5: You can now start the Monero daemon, either from Settings in Monero Gui Wallet, or directly from the terminal in detached/background mode with:
Changing the sync size parameter can have a positive impact in some cases.
Start the daemon with:
./monerod --block-sync-size 10
I've run some tests: Syncing with block-sync-size 10 was faster than with the default of 200. I've run the daemon 9 times in sequence, every time starting at block 1275000 and ending at 1276200 (1200 blocks). I have a slow connection, but SSD. For people with similar hardware and connection I feel it might be fastest to start syncing with 200 and then switch to 10 at around block height 1200000 (when you think you're allmost done, but actually blocks are starting to get huge at around this block height and therefore longer sync time).
10 / 9:52
50 / 11:29
200 / 17:49
10 / 8:09
50 / 20:30
200 / 14:08
10 / 7:37
50 / 13:56
200 / 24:49
ThinkPad W530, SSD, 2 Mbit/s internet, Debian 9 qube in Qubes-OS.
For non-RCT blocks syncing, it seems beneficial as well although not as much:
I would've guessed with old blocks 200 is faster, but because you asked I ran the tests again, this time from block height 40000 to 60000 and it turns out 10 is again faster (on average). block-sync-size / minutes
10 / 8:40
200 / 11:48
10 / 9:21
200 / 12:25
10 / 11:33
200 / 11:25
I didn't test that in windows command prompt but in my sync tool i'd gain best results with
--block-sync-size 4 --db-sync-mode fastest:sync:8750
connection :10mbps . Although developers on github mention that the last argument lowerin the fault-proof i bet it still can be used if you wanna speed. Tool : https://github.com/alexeyneu/tool3
Not to necro this thread... but if anyone is looking for this answer and using windows, once you download the blockchain, move/copy it to the same folder your monero .exe's are in. Then open a cmd prompt, cd into that directory and run the following: monero-blockchain-import.exe --verify 0 --input-file blockchain.raw.
Again, follow security advice about trusted file sources. This is only different in that windows doesn't require the ./ in front of the directory/file names.
protected by sgp♦ Aug 19 '18 at 22:47
Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?