Will release version 1.9.0.4 that has CPU support and API caching for zpool either tonight or tomorrow. Just ironing out a few bugs related to the re adding of CPU mining.

Yea my target is $100 per day per pool version.
Once each $100 gets achieved for a steady 7 days we reduce the dev fee in the next release.

Example zpoolminer just had a $211 24hr dev fee payout but it looks like it was a spike we will see over the next few days.
If this is paying more than $100 per day the fee will reduce to 5Min for me after 6 hours for you
Then when it hits $200 per day dev fee will reduce again to 8Min for me after 12 hours for you
and so on. I am not here to be greedy just here to make a living.



Announcement: Version 1.9.1.0 for zpool has been delayed slightly while I do more code cleanup to improve performance and work on getting hardware info on the main mining page.

Well yea you need a stable internet connection to mine.
I do have a version being worked on that will have API caching that should stop the internet loss issues.

Honestly zpool pays better if your US or EU and ahash pays better if your further away as zpools servers are in Canada.

Attention:
Someone mining BTC on zpool with a rig name of SPrig2 your rig is stuck mining the dev fee please close zpoolminer and relaunch for some reason the rig must have stopped mining while mining the devfee and it got stuck there.
Resolved

Not yet but it is in my road map to do, I have 10 different versions each has a different feature. Just have to finish each one then I can release them.

Well you guys asked for it so here is the preview:

CPU Mining Returns

Image: Take s a Min to load some times.



Yes I will be removing some algo's and the skunk is estimated high zpool API is still normalizing back to how it should be.

I have seen that happen with failing risers or dirty PCIE sockets.

The skunk spike was cause by the zpool api, looks like they were using a exchange that had a HUGE spike in the price of MUN and that shot the estimated earning way up then the exchange went offline and all coins went to a 0 value so now we have to disable skunk until the API settles back to were it should be.

I don't control the source of our API data but i can start on V4 of my caching api to check for these spikes later today.

Those using AhashMiner
This notice was just released on their site doublecheck your worker settings.

Benchmark 1 card then right click all the others and copy from the first GPU

This is because we use normalization so that we do not lose money switching to a coin that has a short spike then by the time it's exchanged it's less that what you would have made on another algo.

Download the release and not the source

I recommend those drivers as they are what I use for testing on RX 470 4GB cards however for more than a 8 Card rig they do not work correctly.

What version of drivers did you upgrade to as i would be willing to give them a test.

Ahash only supports BTC payouts

Announcements:

Just cleared the first $40 day with zPoolMiner, Thank you all so much for your support. We are 40% of the way to the first of hopefully many DevFee reductions in only a months time.

AhashMiner 1.9.0.3 has been released.
zPoolMiner 1.9.0.3 Has been released.
A more robust API has gone Live.

AhashMiner 1.9.0.3 is available at : https://github.com/Cryptominer937/zPoolMiner/releases/tag/Ahash-1.9.0.3
to copy benchmarks from zpoolminer
1. Make sure the zPoolMiner is in the folder called zPoolMiner on your desktop
2. Install AhashMiner
3. Open AhashMiner & after bin downloads close it
4. run AhashGUIMiner Benchmark Copier
5. Re-launch AhashMiner and there should be minimal benchmarking required.


zPoolMiner 1.9.0.3 is available at : https://github.com/Cryptominer937/zPoolMiner/releases/tag/1.9.0.3

to Upgrade
1. Copy your benchmark_GPU files from the configs folder
2. Install the new zPoolMiner
3. Run zPoolMiner and download all Bins.
4. Close zPoolMiner
5. Copy your saved benchmark_GPU files into the new configs folder overwriting the ones created by default

This will minimize Required Benchmarking and Yes I will automate it in a future release.

Changes: Addition of Palgin_HSR for HSR

Fixes: 20-30 tiny bugs.


Unfortunately I have had to make the decision to not keep the Github fully up-to date as we have had people starting to release a versions with the devfee ripped out when there is already a command line argument that can be used to disable it. (Don't ask me for it as you will have to find it inside the code that is available on GitHub.) Github will still be updated but it will remain one full major revision behind. I am doing this so that people are not inserting malicious code into what I have done so far. Will provide source to well respected members of the community if anyone wants my code inspected. 

The blake2S, phi pools randomly gets stuck in a low vardiff state so many have chosen to disable them as a low vardiff means less submitted shares.

Goal for Today.
Version for AHashpool.com
Setup VPS for API caching
Build V3 of my API Cache.

@CjMapope
So your the one that has all those rigs I randomly see mining the devfee with similar names.

Yea the zpool frontend and api went down for a while. I did a quick fix on my API but will also start on V3 of my api to prevent this in the future if it was to happen again.

Well My webhost just warned me about connections per second so guess I have to upgrade to a VPS now.   Cpanel or Sentora for the control panel?

Seeing as i get 12 Min every 12 Hours

Check your math..
12*60 = 720 Min for you
SO
Add 12 Min to that
720 + 12 = 732
Now divide 12 by 732 = 0.0163924426229508

So what is my percentage?

1.63924426229508% which will be reduced as more people use the miner.