The autosave is every 12 hours. I agree that isn't needed for the most part (catching up with some resync if you don't save often is no big deal) and is bad on low mem platforms. I'll take a look at adding a command line option. Should be easy.

EDIT: I committed some code to master that adds a --disable-save option. This turns off the automatic saves every 12 hours. Manual saves and saving on exit still work.

i'm using only 2 arguments --wallet-file= and --password=i see in log file that wallet is opened ok and after this neverending message, for aeond helps --no-console, but for simplewallet no such command

i'm using only 2 arguments --wallet-file= and --password=i see in log file that wallet is opened ok and after this neverending message, for aeond helps --no-console, but for simplewallet no such command

guys please help, any idea?

I'm not sure there is a good way to run the wallet as a true daemon. I think you might need to use screen or tmux. Maybe someone else knows of a way though.

If using the wallet as a daemon take care to ensure that access to the wallet rpc port is limited. It can be used to send your coins.

The autosave is every 12 hours. I agree that isn't needed for the most part (catching up with some resync if you don't save often is no big deal) and is bad on low mem platforms. I'll take a look at adding a command line option. Should be easy.

EDIT: I committed some code to master that adds a --disable-save option. This turns off the automatic saves every 12 hours. Manual saves and saving on exit still work.

If you pull and build you will get it, or wait for the next release.

My public node is updated and running with the --disable-save option. Thanks!

The autosave is every 12 hours. I agree that isn't needed for the most part (catching up with some resync if you don't save often is no big deal) and is bad on low mem platforms. I'll take a look at adding a command line option. Should be easy.

EDIT: I committed some code to master that adds a --disable-save option. This turns off the automatic saves every 12 hours. Manual saves and saving on exit still work.

If you pull and build you will get it, or wait for the next release.

My public node is updated and running with the --disable-save option. Thanks!

The autosave is every 12 hours. I agree that isn't needed for the most part (catching up with some resync if you don't save often is no big deal) and is bad on low mem platforms. I'll take a look at adding a command line option. Should be easy.

EDIT: I committed some code to master that adds a --disable-save option. This turns off the automatic saves every 12 hours. Manual saves and saving on exit still work.

If you pull and build you will get it, or wait for the next release.

My public node is updated and running with the --disable-save option. Thanks!

I could have put that in the option but my assumption was that if you don't want it saving often, you don't want it saving at all because it causes massive swapping and the node to become unresponsive. Better to just have copy of the blockchain up to some recent-enough point (created either on that system or a different one) and then let it resync on restart.

This also reduces the disk space requirement because saving the blockchain requires writing a new one and then replacing the old one (so 2x).

Alrighty, you've downloaded the wolf cpu miner, extracted the files and you already have a wallet address?

Launch the command promt, just search for "cmd" and execute it. Depending on where the mining application is located (as in where you have extracted the files) on your PC, you now need to navigate there with the command promt. Assuming that you have extracted all the files on the desktop, you type "cd desktop" and confirm. Note, if the files are in a folder on the desktop, let's call it "miner", you'd first navigate to the desktop and then to this folder (cd desktop --> cd miner)

Now you need to start the miner with the command, that you can find on the getting started page of the pool you want to use. It looks like the following:minerd -a cryptonight-light -o stratum+tcp://aeon.kryptopool.com:3333 -u YOUR_WALLET_ADDRESS -p xReplace "YOUR_WALLET_ADDRESS" with your wallet address and execute the command.

That's it! Let me know if there is anything unclear

This is exactly what i did, but when i execute the command line it says minerd is not a command and nothing happens.

Make a .txt file in the same directory as minerd.Rename the extension from .txt to .bat.Put in there...

I just started mining on the kryptopool today and am getting a tad over 1100 H/S on average. With that hashrate should I be in the 3333, 5555, or 7777 pool as far as difficulty? I started in the 3333 pool that says "low end hardware", but I wondered if I should switch to a higher difficulty pool? Thanks!

I have tried many many times to mine with the wolf opencl miner and have spoken with Arux alot on trying to get it working but never could get it working. I tried with several different drivers as well. Wolfs miner works with my rx cards mining xmr but when i mine aeon all i get is low difficulty shares. I tried many different setups but could never get it going. If anyone is mining with wolfs and are using the RX series cards please let me know what your doing. When i saw that there was a new miner it made me want to give it a go again.

Well, the reason is that this miner sends invalid shares, and then you get banned by pool. Any pool, any worksize, any intensity, any (with mind, of course) amd driver version. That's on RX series graphics. So, everyone looks for a good amd cryptolight miner, and wants to give a try for any miner seen on the horizon. W0lf is not going to support this miner - he's got a lot of work to do without it (Nexus miner and others from the recent ones).

I found there were a couple of problems with the seed nodes. One of the nodes seems to have unreliable hardware and the other one has an out-of-date IP address in the code. I'll address both issues ASAP but for now at least the unreliable one is rebooted and back in service. So syncing new nodes should now work.

I have tried many many times to mine with the wolf opencl miner and have spoken with Arux alot on trying to get it working but never could get it working. I tried with several different drivers as well. Wolfs miner works with my rx cards mining xmr but when i mine aeon all i get is low difficulty shares. I tried many different setups but could never get it going. If anyone is mining with wolfs and are using the RX series cards please let me know what your doing. When i saw that there was a new miner it made me want to give it a go again.

This also happens with my Hawaii cards (390X)

Oh, I see.Unfortunately enough they (the guys at the git repository) were not descriptive at all as far as compilation under win is concerned