Run bitmonerod with the option "--db-sync-mode safe" and it will persist every change immediately. Then if your system crashes or restarts suddenly, there will be no data lost and bitmonerod will pick up wherever it left off the next time it starts.
Saving isn't really needed now. All it does is call mdb_env_sync, which will flush the filesystem, so the OS really writes things on the disk. Exiting bitmonerod normally will also call this, so using save before exit is unneeded.
Originally, save was needed because the blockchain was all held in RAM, so if your node was running long term and crashed, you'd ...
When you’re on Linux or macOS, I usually put the Monero software in the /opt directory. That’s where “optional” software typically goes outside of the OS packaging system. I also try to plan ahead and keep multiple versions.
E.g. on macOS, for the Wolfram Warptangent release, I created a subdirectory like this:
$ cd /opt
$ sudo mkdir monero.mac.x64.v0-10-0-...
For Linux and Mac OS X, browse to the folder you extracted the Monero binaries to. Subsequently, open the terminal and type ./monero-wallet-cli to start the wallet or ./monerod to start the daemon. If you want to see all the flags the wallet and daemon can be launched with and how they should be used, use the following commands (from the same directory). ...
Quoting relevant part of the commit message:
There are three ways to prune a blockchain:
run monerod with --prune-blockchain
run "prune_blockchain" in the monerod console
run the monero-blockchain-prune utility
The first two will prune in place. Due to how LMDB works, this will
not reduce the blockchain size on disk. Instead, it will ...
All of these are measured in kB (1024 bytes). See src/p2p/net_node.inl, in set_rate_up_limit.
The defaults are 2048 kB/s upload, and 8192 kB/s download. If those are near or above your connection's capabilities, you may want to lower them to a bit lower, to keep some QoS. Similarly if you have a fast connection, you might want to increase them.
If you previously ran simplewallet in CLI mode (or 0.10's monero-wallet-cli in RPC mode) then you would simply transition to using monero-wallet-rpc with the same flags. As always, running the binary with --help will give you a list of all possible flags.
monerod currently can only be set to limit outgoing connections with the parameter --out-peers where the default is 8.
So if you setup your node to be reachable for the public, you can't limit incoming connections. However, you could use a firewall like iptables to limit incoming connections on your public port.
Sometimes, the wallet's idea of what outputs are spent and what outputs are not get out of sync with the blockchain. This can happen if you exit the wallet without saving after sending a tx, or if it crashes.
rescan_spent will look for the key images on the blockchain to make sure it's up to date.
Since this involves sending your key images to the daemon, ...
The log file is ~/.bitmonero/bitmonero.log. On Windows, it is somewhere else which someone who knows will edit here soon.
The status command reports your hash rate. If you're running a detached monerod:
You could use watch to run this at whatever interval you want, eg:
watch -n 60 monerod status >> /tmp/monerod.log
Or you could ...
You can type the command status in monerod. This will show something like the following, in green:
Height: 1226605/1226605 (100.0%) on mainnet, not mining, net hash
51.39 MH/s, v4, up to date, 8+6 connections
The first number in the 8+6 connections part refers to the number of outgoing connections. The second number refers to the number of incoming ...
Transaction fees are paid to the particular miner who includes the transaction in a block. The more transaction you fit in a block, the more fees you get. However, once you pass the median of the last 100 blocks in size, the base reward goes down, so there exists a sweet spot in size which maximizes the base reward plus transaction fees you get.
Once you've ...
Mostly because it's a lot slower, which could cause users to abandon Monero out of frustration if they can't sync in a few days.
There are recent improvements to a "sweet spot", however. See https://github.com/monero-project/monero/commit/65e33b1bc51d6540f23c8de0dbf4826a56549373
While getting a bad block on top should not be possible in the first place, it could happen in case of crashes, etc, on some systems.
Popping one or more blocks can be done with blockchain_import, eg: blockchain_import --pop-blocks 1 will pop the last block. However, if the blockchain got corrupted somehow, this might not work.
Last, note that the message ...
Permission denied is typically due to... bad permissions, unsurprisingly. You need at least execute permission (for owner if you own the file, for group if you're on its group, others otherwise).
Here, sudo fixes it, so it's likely you don't have read rights on the directory. Fix that. You probably saved this as root, which is a bad idea in the first place. ...
The error "/usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/5/../../../../lib/libgtest.a(gtest-all.cc.o): relocation R_X86_64_32 against `.rodata' can not be used when making a shared object; recompile with -fPIC" tells you that the libgtest.a file of your system has not been compiled with position independent code, which is necessary to compile monerod.
You must ...
Take a look at a response to issue #2351:
You can send 50 monero 20 times in one tx to yourself (make sure you have set merge-destinations to 0 first). This will break up the 1000 output.
Also set min-outputs-count and min-outputs-value to, say, 20 and 10, see the commit message for 0ad87db for an explantion of how they work. Last, you can pay several ...
A block is not a transaction. Obviously, if you print different things, you will get different results. This should not come as a surprise.
A block may contain more than one transaction (in addition to the coinbase transaction). It appears you are comparing the block's coinbase transaction to the transactiou you had the txid for. These things are also ...
When you've started monerod with the --rpc-bind-ip option (and --confirm-external-bind), you should also reference that when sending commands, such as exit (or status). For example, the following wouldn't work anymore:
$ monerod exit
Creating the logger system
Error: Couldn't connect to daemon
You'd need to do it like this instead:
$ monerod exit --rpc-...
Using monero is teaching me....find a use case for it or some reason to justify spending the fee, and do a little experimenting with it. Having used monero a handful of times, i've learned a bit about payment ID's. Did you know that to use shapeshift for example, you have to use a payment ID? When I learned that, it seems like payment ID's will be necessary ...
With priority set to 0, what does that actually mean in practice?
First note that the priority levels unimportant, normal, elevated, and priority correspond to multipliers of x1, x4, x20, and x166, respectively.
With priority set to 0 it will use the default fee multiplier, which is x4. In addition, the fee priority level is static, i.e., it won't change ...
You can do this on Windows using NTSF symlinks:
Open an elevated CMD window. Then:
mklink /D "C:\ProgramData\bitmonero" "x:\mydir\monerodir"
Then you don't need to specify any other command line options when starting the monero daemon.