Both Verge Pools are up again, running on daemons containing the attack fix.

I'm currently re-building the Verge daemons from source with the proposed fix applied. Once this completes the pool unfortunately require another restart.

Please read this: https://feedback.coinfoundry.org/communities/1/topics/909-todays-attack-on-the-verge-blockchain-not-on-the-pool

Sometimes I hate it to be right. Just like I've assumed, todays Verge outage was triggered by outside forces: https://bitcointalk.org/index.php?topic=3256693.0

Verge-Blake apparently working again. Still resolving a crash issue with the Verge-Scrypt daemon.

I'm going to restart both XVG pools now running on daemon with a freshly synced blockchain.

I'm actively working on the problem. Which is tricky as absolutely nothing on our end changed over the past months. Therefore it must be something happening on the blockchain which would explain why the daemons suddenly locked up after running stable for weeks.

Both verge daemons and the associated stratum servers have been restarted and appear to be operating normally again.

The verge-daemon was still running but entered some kind of zombie state. Investigating.

We are talking about Verge-Scrypt, not Verge-Blake right?