Dan, could you elaborate it more what the problem is? Regarding xmr-stak, yes it's the new 2.5 version that's required to mine Monero after the hardfork on October 18th.

I feel your pain. Since our hashrate is quite low it may take a couple days for a block. Two days ago we hit a block but it was an orphan. That's why your balance hasn't moved yet.

The ETH and ETC pools will return for sure. But since I realize that the current situation is far from ideal for the miners I will try to come up with a fair solution for an interim compensation. Could you please contact me via contact@coinfoundry.org?

Below is the current state of that wallet - directly from the pool database. As you can see the last payment was sent on 06-21 after which the balance was reset. That someone is sitting on an unpaid balance of 0.2 ETH when the pool has a payment limit of 0.1 ETH shouldn't ever happen and hasn't ever happen throughout the lifetime of the pool. Could it be possible that your memory in this regard is wrong or applies to a different pool?

miningcore=# select * from balances where poolid = 'eth1' and lower(address) = lower('0xbF9c6349111298f42b767bD603826E6c2acBD9CB');
poolid | coin | address | amount | created | updated
--------+------+--------------------------------------------+----------------+---------------------------+----------------------------
eth1 | ETH | 0xbf9c6349111298f42b767bd603826e6c2acbd9cb | 0.000000000000 | 2018-02-19 17:14:19.58346 | 2018-06-21 08:47:34.013312
(1 row)

miningcore=# select * from balance_changes where poolid = 'eth1' and lower(address) = lower('0xbF9c6349111298f42b767bD603826E6c2acBD9CB') order by created desc;
id | poolid | coin | address | amount | usage | created
--------+--------+------+--------------------------------------------+-----------------+----------------------------------------------+----------------------------
656293 | eth1 | ETH | 0xbf9c6349111298f42b767bd603826e6c2acbd9cb | -0.044945619786 | Balance reset after payment | 2018-06-21 08:47:34.013625
656228 | eth1 | ETH | 0xbf9c6349111298f42b767bd603826e6c2acbd9cb | 0.044945619786 | Reward for 58.03 T shares for block 5827456 | 2018-06-21 08:44:37.236995
619598 | eth1 | ETH | 0xbf9c6349111298f42b767bd603826e6c2acbd9cb | -0.052982801172 | Balance reset after payment | 2018-06-06 12:46:49.811581
619469 | eth1 | ETH | 0xbf9c6349111298f42b767bd603826e6c2acbd9cb | 0.052982801172 | Reward for 53.88 T shares for block 5742109 | 2018-06-06 12:44:31.039671
593577 | eth1 | ETH | 0xbf9c6349111298f42b767bd603826e6c2acbd9cb | -0.044029356220 | Balance reset after payment | 2018-05-29 07:17:38.973934
593431 | eth1 | ETH | 0xbf9c6349111298f42b767bd603826e6c2acbd9cb | 0.044029356220 | Reward for 48.04 T shares for block 5695762 | 2018-05-29 07:14:47.521634
536280 | eth1 | ETH | 0xbf9c6349111298f42b767bd603826e6c2acbd9cb | -0.019501897309 | Balance reset after payment | 2018-05-17 18:05:09.098905
536201 | eth1 | ETH | 0xbf9c6349111298f42b767bd603826e6c2acbd9cb | 0.019501897309 | Reward for 20.9 T shares for block 5630524 | 2018-05-17 18:03:32.663662
530836 | eth1 | ETH | 0xbf9c6349111298f42b767bd603826e6c2acbd9cb | -0.019652967602 | Balance reset after payment | 2018-05-16 20:36:55.584757
530721 | eth1 | ETH | 0xbf9c6349111298f42b767bd603826e6c2acbd9cb | 0.019652967602 | Reward for 21.53 T shares for block 5625430 | 2018-05-16 20:35:36.756962
521848 | eth1 | ETH | 0xbf9c6349111298f42b767bd603826e6c2acbd9cb | -0.022431152074 | Balance reset after payment | 2018-05-15 14:13:25.511712
521728 | eth1 | ETH | 0xbf9c6349111298f42b767bd603826e6c2acbd9cb | 0.022431152074 | Reward for 23.19 T shares for block 5618247 | 2018-05-15 14:11:29.530095
494421 | eth1 | ETH | 0xbf9c6349111298f42b767bd603826e6c2acbd9cb | -0.022706687857 | Balance reset after payment | 2018-05-12 00:08:05.995578
494326 | eth1 | ETH | 0xbf9c6349111298f42b767bd603826e6c2acbd9cb | 0.022706687857 | Reward for 25.24 T shares for block 5597753 | 2018-05-12 00:06:07.843152
466718 | eth1 | ETH | 0xbf9c6349111298f42b767bd603826e6c2acbd9cb | -0.013686632743 | Balance reset after payment | 2018-05-08 19:35:34.60164
466607 | eth1 | ETH | 0xbf9c6349111298f42b767bd603826e6c2acbd9cb | 0.007445107003 | Reward for 8.53 T shares for block 5579525 | 2018-05-08 19:34:04.013295
458880 | eth1 | ETH | 0xbf9c6349111298f42b767bd603826e6c2acbd9cb | 0.000783863254 | Reward for 1.19 T shares for block 5574259 | 2018-05-07 21:47:16.290088
170594 | eth1 | ETH | 0xbf9c6349111298f42b767bd603826e6c2acbd9cb | 0.000517165500 | Reward for 564.05 G shares for block 5293692 | 2018-03-21 06:38:04.180027
65293 | eth1 | ETH | 0xbf9c6349111298f42b767bd603826e6c2acbd9cb | 0.004940496986 | Reward for 5 T shares for block 5215249 | 2018-03-07 23:29:47.634025
10173 | eth1 | ETH | 0xbf9c6349111298f42b767bd603826e6c2acbd9cb | -0.011813293818 | Balance reset after payment | 2018-02-25 16:53:39.453512
10030 | eth1 | ETH | 0xbf9c6349111298f42b767bd603826e6c2acbd9cb | 0.011813293818 | Reward for 23.92 T shares for block 5154577 | 2018-02-25 16:47:24.314076
(21 rows)

You're welcome :)

The pool is fully prepared and tested for the upcoming algorithm change.

Ablixeron: I fully understand your frustration. But would it be responsible to let miners work against a pool that distributes work from node that fails to inform the pool about new blocks? If you and anyone else provides his wallet address in this thread I will verify all claims and distribute the pending balances asap.

Unfortunately it was an orphan ;(

Two reasons.

1. The pool was pretty much dead but that wouldn't have forced me to take it down for now ...
2. As CLO is Ethereum based it was also affected by this problem.

That's very strange. I cannot find any problems with received shares during that timespan.