I have difficulty to believe that, judging by the way you do 'business', you really care about someones life, king Pin  ..

( don't get me wrong, its fun to have you around )

From "getting started" page on the Test pool I read this:
Yacminer GPU Miner [example config for 7790. Use static diff port 5555]
yacminer --scrypt -w 128 --lookup-gap 2 -I 17 --thread-concurrency 8000 -g 1 -o stratum+tcp://stratum2.tumblingblock.com:5555 -u Weblogin.WorkerName -p WorkerPassword

Got NF 14 (yacminer) and low hashrate, tried to change the batfile with the above settings and got NF 16 but no connection to the pool, changed back to the original settings and still can't connect with this miner to the test pool. The other miners have 0,1 difficulty and very low hashrate with the original settings...

Strange, now  when I looked at the testpool, all my original rigs with yacminer pointed at stratum+tcp://stratum2.tumblingblock.com:64444 had high variable difficulties (1-5) and normal hashrate. Tried my first rig which got rejected before and pointed it towards port 64444 and got low difficulty (0,1), switched to port 64445 and it seem to be hashing at normal speed and difficulty around 1.
So it seem to be working on both ports with yacminer, the original ones with port 64444 and the first one that got rejected now works on port 64445, if you can make something out of that...

Yes, thanks tons for the hash guys.   You've been awesome.  This has been very helpful.

So far Digishield - 10 block average looks like the best candidate.  It is set up to retarget every block, adjustments will be no more than in increments of 8% up and 16% down.  It averages out over the last 10 blocks, allowing it to be fairly flexible with inconsistent hash rates.  If there's a hit and run on us, we'll recover at a decent rate.   I've also implemented the same retarget on the staking, but with its original 20 second spacing.

I'll be resetting the testchain and test database back again soon, so we can test transition to the new retarget starting from a higher diff block.  If you leave your miners aimed at the pool, I'll have everything restored, including your pool workers, within 5 minutes or so after it goes down.

Looks like the test pool is up and running again. All my miners are connected and mining at normal hashrate. Changed one rig from port 64444 to port 64445, so now two rigs are running on the static port and the rest on variable diff, all yacminer NF 14.

Good to hear. Anyone else have their Yacminers running successfully on the test pool? It really shouldn't be any different than the other pools as I'm using the same plain NOMP setup for the stratum.

Nice new pools are welcome.
I must ask you Thiago where is your support for Testnet UTC pool?

I tried to sign up for the test pool.  I am not receiving the verification email though so unable to login to create workers etc.