Fuck it, I'll volunteer. If the devs can write a simple how-to connect to the testnet, I'll throw 8MH/s on there for 0.01111111 BTC/hr. If it allows them to test code better, the small reimbursement for my time should pay itself back in droves, because I have a feeling they're "testing" code with a bullshit hashrate.
Put a down payment of an hour in BTC to 1C6H5m7DPUgrV5NAzRnjo3nRVCp5EvWwL6 if this is interesting, and I'll come back and check and flip over to testnet. Otherwise mining CAT for 23.5 hours with highest hashrate of any available pools for only ~100 CAT a day is atrocious until this code gets fixed.
Again. 0.01111111 BTC/hr. Could quintuple the price value if the data gleaned from it is used correctly. Or knock out five blocks a day as usual. Oprah show bro!!
I'm the one in charge of the testnet, as it is mine to begin with anyway. I am keeping it a controlled environment, and will actually be looking for someone to act as a whale to slam the network, at least once per solution that is put on the testnet to be run through the series of tests. Unless I get any kind of donations, then that means that your fee that you are asking, would have to come directly out of my own pocket. I'm already using one of my good servers, that I should be leasing out to others so the server could pay for itself. So, I am already losing around $50 / month just to run these tests and help out the community, so code can be tested for bugs and verify that the code in the solutions selected does what it is supposed to do.
Your 0.011111111 BTC/Hr, at current rates, is not unreasonable, as it is round $6 USD / hour. I will just have to come up with the fundings per run. You will have to be willing to jump on and off exactaly when I specify, so the tests being performed can be considered valid. I do not have any one else's solution to the difficulty re-target yet, but I'm sure they will be getting coded and ready for testing soon. I also do not have the full list of what kind of solutions that will be put on testnet. The current solution on testnet is a PID (
http://www.csimn.com/CSI_pages/PIDforDummies.html ), with 16 block averaging for time. It is looking like 16 block averaging is too slow, and I am planning on dropping it down to 8 block averaging for the next round of "steady state" testing.