17

With the most recent version, this particular issue is, fortunately, trivially fixed as follows: GUI Exit the GUI by clicking on the x (right top) and subsequently making sure to stop the daemon as well. Upgrade to GUI v0.14.0.0 -> https://www.reddit.com/r/Monero/comments/ayshug/gui_v01400_boron_butterfly_released/ Start the "new" GUI (v0.14.0.0) and let ...


11

Mainly it's a question of available RAM and I/O bandwidth. When you're importing a raw file, reading the raw file takes up disk bandwidth as well as RAM in the filesystem cache. This competes with the disk bandwidth (and RAM) needed to write out the database file. When you're syncing over the network, this extra disk and RAM overhead isn't present. Note ...


10

Basically, by not verifying, you're assuming the download is trusted. But there could be all sorts of bogus data in the blockchain.raw, if you have a man-in-the-middle attack during the download. Personally, I only ever use blockchain.raw imports when I'm experimenting on very low power ARM devices, syncing up from scratch in nearly every case is ...


9

People were abusing --verify 0, using it for files they downloaded from the internet, which is a dangerous thing to do. So it got renamed to --dangerous-unverified-import (prior to this it was named --guard-against-pwnage), to make it clear it's a dangerous thing to do. Similar to disabling a malware scanner when downloading some binary off the internet. Or,...


7

As far as I know, the current blockchain is compatible across different operating system as long as they have the same "amount of bits", i.e., 64 bit to 64 bit systems or 32 bit to 32 bit systems would work, but 32 bit to 64 bit systems wouldn't work. If this doesn't work there is a second option. That is, you can export on your Linux system using the ...


5

An oversimplified explanation is as follows: Bitmain, an ASIC manufacturer, created a Cryptonight ASIC. This enabled the company to "control" a large portion of the Monero hash rate and consequently mine many coins. When The Monero Project learned about this, it modified the Cryptonight proof-of-work (PoW) so that any previously-created ASIC's would be ...


4

It seems likely that this would be a good idea to import the raw file. Not only will this possibly be faster, but also avoid spamming the Tor nodes on your way with gigabytes of blocks. One very large difference in running time when importing a raw file is whether verification is enabled or not. If you already have a raw file you know is good, you can ...


4

Yes. The daemon doesn't check transaction signatures when under a checkpoint. There are other possible optimizations, but I think that's the only one active right now.


4

This question basically pertains to where monero-blockchain-import stores the imported blockchain by default. monero-blockchain-import uses the following default directories to store the imported blockchain: Windows: C:\ProgramData\bitmonero\lmdb Linux and Mac OS X: ~/.bitmonero/lmdb Note that, by default, both C:\ProgramData\bitmonero\lmdb and ~/....


3

You can put this file anywhere, you just need to add --input-file XX and put the file and its path instead of XX, eg: monero-blockchain-import --input-file $HOME/blockchain.raw As for "monero-blockchain-import doesn't exist" errors, this is unrelated, and just means monero-blockchain-import is not in your PATH environment variable. Either add its ...


2

The answer to the subject is already here Is the raw Monero blockchain file different for Linux, Windows, or Mac? There is nothing to import if you just copy the monero data directly.


2

The current LMDB blockchain is compatible across operating systems. Just copy the files and use them directly. The new one in 0.10 is also compatible across 32/64 bit architectures. That is, the format is identical across ARM32/ARM64/x86/x86_64/Windows/Linux/Android/iOS/etc. There is nothing to convert.


1

I was not able to find the .bitmonero directory in the /home folder and was not aware that "." folders are hidden. So I searched for help in the Ubuntu community and found this answer How to show a hidden file. It was easy, stand in the home directory and put this command: cmd/ctrl + H Then, the .bitmonero directory showed up. This answer might help ...


1

During sync, Monero will add chunks of 200 blocks at a time. The speedup gained from this quickly goes into diminishing returns as the chunk size grows, but the memory usage grows linearly, so it's possible to decrease that chunk size with the --block-sync-size N parameter. A plausible value for N is 20 instead of 200, and the speed will be similar (if you'...


Only top voted, non community-wiki answers of a minimum length are eligible