Although the concept of the coin and the measures the dev has taken in order to keep things as fair as possible deserve a big kudos, there are a few issues that need to be addressed asap:
1. There is no open source standalone miner.
2. There seems to be no official plan for a public pool.
3. It is not possible to manage the wallet from the command line under GNU/Linux, unless you have enough free RAM to run the internal miner thread.
4. On Windows and Linux the wallet does not seem to sync if 'ramhogthreads=0'.
5. The provided config file should have more sane default values, at least ramhogthreads should be zero.
1. There is no open source standalone miner.
2. There seems to be no official plan for a public pool.
3. It is not possible to manage the wallet from the command line under GNU/Linux, unless you have enough free RAM to run the internal miner thread.
4. On Windows and Linux the wallet does not seem to sync if 'ramhogthreads=0'.
5. The provided config file should have more sane default values, at least ramhogthreads should be zero.
1+2 There have been several requests for a standalone miner and public pool. For miner and pool source must be released for people to trust nothing nefarious is in the binaries. I also request the source for both standalone miner and pool be released here, and I also will point my hashing power to the mining pool.
4 I am currently working on a way to verify hashes without running ramhog to validate the blocks and requiring 15 GB RAM. The way it would work would be the checkpoint node would verify sign the list of hashes so that the client itself would have the option of verifying itself or using the validated hash list signed by the checkpoint node. As the block height increases it will take longer and longer to download and validate the full chain, one of the drawbacks of ramhog. I hope to include this optional feature to the client within a week.
Read my post if you want to be informed, ramhogthreads != cpu threads.