Of course!

If you are able to update from source code (for most Linux users this is fairly easy) then please get the latest update as described above. If not please await a new version of the binaries soon.

If it is 100% pool then you wouldn't even have a node in there at all, so no issue of upgrading.

My preferred way to use AWS is pool on the GPU and solo on the CPU, but I don't know if they are doing that.

I don't even see the install script there any more, but maybe I'm looking in the wrong place.

I see

Here: http://monero.cc/getting-started/index.html#install_source

That is how I do it, except "make -j$(nproc)" goes much faster.


I find this is usually not a major concern. The reason being that you will end up needing to update your images (new version of node, etc.) and at that point I will just update the blockchain in the image as well. (I also grab any new OS updates.) The rest of the time, yes it syncs but it doesn't really take that long. Downloading the bootstrap would probably take longer (unless your image gets really old).

Another pitfall here is to make sure you have enough disk space for two copies of the blockchain. Because when it saves (every 12 hours) it stores the new one before deleting the old one. This can be an issue on some very small instance types.


Excellent! Thank you (and them) for both.

Important update (source code only)

We have a new update with additional precautionary checkpoints added to protect more of the existing blockchain. In addition this update adds the ability to read checkpoints from an external file. We will be distributing updated checkpoint files that will continue to protect the blockchain without the need for a full update of the daemon.

Although there has been no actual attack we consider the threat credible and are acting accordingly. We urge you to do the same.

We are however, continuing development and this update also contains some new features that will be included in the next official build. As such, dependencies have changed. For example Linux dependencies:


https://github.com/monero-project/bitmonero

Plain 'git pull' wont work. Unless you are doing your own modifications to the code it is probably easiest to make a new clone. If you are doing your own modifications you should know how to use git.

If you are operating a pool or other important service, or if you are solo mining, and you compile your own node, please pull master from github and upgrade ASAP. If you are not a git expert it is probably better to just create a new clone. Likewise if you have AWS images, please rebuild them with the new version.

Our recommendation for exchange is to remain frozen for external transactions. If you are still running a node, please update.

The only evidence of anomalous activity is what was reported by fluffypony. Nevertheless malicious activity may occur that is not visible until the moment of the attack.

The update is an important precaution.

Updated binaries will follow shortly.

Further measures will be taken as necessary.

For some portion of the past 12 hours (including a time after my update message) there was a bad commit on github, so if you updated from there you should make sure you have the current version as of now.

What are the has rates on the c3.8xlarge and  g2.2xlarge, what are the costs?

Indeed. It's more cost-efficient to mine with the GPU instances. The price is indeed 1/3 of the 32 core instances.

With the current configuration the hashrate for the g2.2xlarge should be around 60% of the c3.8xlarge.

You sure? its 1.6 linux and 3.008 windows right now for the c3.8xlarge

Also depends on region, right? In the regions I used, when I had a number of instances open, and wanted them to be persistent and stay up without being outbid, ~0.3 was the max I had to put for CPU.

In that case many reliable pool will welcome the spoiled hashrate !