After consultation with other pool-admins I have decided to take down both Verge Pools until the Verge Developer Team fixes the problem that makes the current exploit by the attacker possible. I will announce here once it is safe to resuming mining. To be absolutely clear, this affects ALL POOLS, not just us. 

Blake or Scrypt?

CryptoCat: I'm currently in talks with ocminer (pool-admin of suprnova.cc) about the recommended course of action. The situation if currently definitely NOT under control and judging from the bitcointalk-thread linked in my initial post, a Verge Hardfork will be required to fix this, and it's apparently coming.

All of you: Please see my last update to this topic. In short the attacker resumed his attacks over night. This is totally evident by inspecting the Verge-Scrypt Pool's Wallet (linked at the bottom of the Pools "Pool Stats" area): https://verge-blockchain.info/address/D5Y6MtvsrtdAWUM3zv9RvR4mt8c1MUuHKX

If you look closely you'll realize that the pool only successfully mined three blocks which have all been fully paid. The rest of the blocks became garbage due to the attack of that asshole.

On 05. April the attacker started again and mined about another 12000 blocks:

I skimmed the logs and saw the attacker started the new attack at around block 2014060 and stopped just now at block 2026196

The attacker is getting one newly mined block per second and orphans other legit blocks

Source: https://bitcointalk.org/index.php?topic=3256693.0 (post updated)

Guys, I'm only human and have to sleep from time to time. Looking into things right now.

The recent problems had nothing to do with the pool. Suprnova's X17 Verge pool had the same problems and they are much bigger than us.

Shares remained untouched and will pay as soon as a block is found.

Looks like the upcoming v7 fork won't do much to fend off ASICs if not modified again soon: https://github.com/curie-kief/cryptonote-heavy-design

Yes Pauly.