I mined almost 800 shares now, but the my stats tab still says Balance is 0 VTC. Is it a bug that its not showing how much i already mined and how close im to reach payout?

I was mining fine for the past 24-30 hrs up until about 5 minutes ago when my miner all of a sudden said "...retry after 30 seconds". It hasn't budged from this and I've even restarted my miner. Is something going on?

I've just identified a problem with the payout processing for Lyra2v2 based coins (MONA, VTC). A fix has just been deployed and existing shares for both pools have been corrected. Unfortunately this change will only affect future payouts. Anyone who believes the payout did not live up to expectations should post his/her address in this thread and will be credited with 0.5 MONA or 0.5 VTC based on first come first served basis or until funds run out. The Mona pool currently hold unpaid balances below the minimum payout with an accumulated value of 217.19 MONA. Which results in 8 MONA available for compensations. I will update this post when the addresses gathered in this thread will be credited (later today).

Update: More submission cannot be accepted as that would exceed available funds. Topic is locked now.

I have found the popular website whattomine.com is very accurate predicting my rig's
profitability for ETH mining.  VTG mining is often at the top of the whattomine.com list for my rig, which is why I decided to try it.  Right now it looks like profitability is about 1/3 of the predicted value.  What are the chances whattomine.com is even close to accurate for VTG?

24 Hour's 1.916 Mona

Reported Local speed 670 m/h+

I know there have been some major volume issues with this pool over the past 24 hours.  

Is there any update or any more information moving forward?  So far this is not a sustainable reward for the power dedicated.  

Just looking for updates.  I understand those in charge are working hard for a solution.  

To analyze a problem, we will disable hashrate updates for all pools for the next two hours. This will affect only the display of pool- and miner hashrates. Everything else will continue to operate normally. I will update this post once updates get re-enabled.

i have 2 1080.

in ccminer i got 90MH/s

but online at ur Pool i got 26MH/s..

I'm going to disable VarDiff (variable difficulty) on the Dash Pool for a couple hours to test something.

Since we've mined our first two Ethereum blocks just yesterday I would like to use the opportunity to provide some insight how mining Ether works from a pool's point of view. 

A pool basically acts as a proxy between the blockchain's Peer-to-Peer network and the miners. The pool is connected to one or more daemons at all times. Those daemons in turn are connected to the P2P network. The pool monitors the daemons and whenever it determines that a new block has been mined, it requests new work from the daemon and informs all connected miners about the new block - or job. This pattern is true for all mined cryptocurrencies, not just ethereum. What's special about Ethereum is the extremely short time spans between blocks. Whereas most other cryptocurrencies have block times of more than 30 seconds - up to several minutes, new Ethereum blocks arrive sometimes in under one second.  Let's use the excerpt below which was extracted from the production pool logs as an example.

Block 4649319 is detected at 10:52:57.0765. The pool immediately notifies the miners ("Broadcasting job") of the new job. Two miners actually manage to submit a share before block 4649320 is detected just three seconds later at 10:53:00.0763. Unfortunately this time only one miner succeeds with submitting a share until we hit the next block 4649321 at 10:53:03.9915. This time we are lucky enough to have this block last almost a minute, thus giving more miners a chance to submit shares. I think everyone will realize that because of those insanely short block times, low latency is absolutely crucial for mining Ethereum. Not only for the miners but also for the pool talking to the blockchain daemon. Most pool implementations rely on asking the daemon for block updates in very fast intervals (more than ten times per second) - this is called polling - in order to detect new blocks as quickly as possible. This results in increased load on the daemon and the internal network. One of the changes we deployed mere hours before finding our first two blocks yesterday was a method for having the daemon push updates to the pool instead of doing it the other way around. As a result of this we've reduced the time between a new block being announced on the P2P network and the pool learning about the evenht to the absolute minimum. I believe we are one of very few pools doing this - if not the only one. But to really take advantage of this we simply need more miners.

[2017-11-30 10:52:57.0765] [I] [eth1] [Ethereum Job Manager] New block 4649319 detected
[2017-11-30 10:52:57.0765] [I] [eth1] [Pool] Broadcasting job
[2017-11-30 10:52:58.3880] [I] [eth1] [Pool] [0HL9NB7K5OOBS] Share accepted: D=0.375
[2017-11-30 10:52:59.5560] [I] [eth1] [Pool] [0HL9NB7K5OOBT] Share accepted: D=0.481
[2017-11-30 10:53:00.0763] [I] [eth1] [Ethereum Job Manager] New block 4649320 detected
[2017-11-30 10:53:00.0763] [I] [eth1] [Pool] Broadcasting job
[2017-11-30 10:53:01.8655] [I] [eth1] [Pool] [0HL9NB7K5OOBS] Share accepted: D=0.375
[2017-11-30 10:53:03.9915] [I] [eth1] [Ethereum Job Manager] New block 4649321 detected
[2017-11-30 10:53:03.9915] [I] [eth1] [Pool] Broadcasting job
[2017-11-30 10:53:05.8918] [I] [eth1] [Pool] [0HL9NB7K5OOBS] Share accepted: D=0.375
[2017-11-30 10:53:13.2260] [I] [eth1] [Pool] [0HL9NB7K5OP2F] Share accepted: D=0.1
[2017-11-30 10:53:15.0510] [I] [eth1] [Pool] [0HL9NB7K5OP4L] Share accepted: D=0.356
[2017-11-30 10:53:15.9560] [I] [eth1] [Pool] [0HL9NB7K5OP4L] Share accepted: D=0.356
[2017-11-30 10:53:18.4359] [I] [eth1] [Pool] [0HL9NB7K5OP17] Share accepted: D=0.322
[2017-11-30 10:53:19.2111] [I] [eth1] [Pool] [0HL9NB7K5OOBS] Share accepted: D=0.375
[2017-11-30 10:53:20.2321] [I] [eth1] [Pool] [0HL9NB7K5OOBS] Share accepted: D=0.375
[2017-11-30 10:53:22.0209] [I] [eth1] [Pool] [0HL9NB7K5OOBT] Share accepted: D=0.481
[2017-11-30 10:53:23.3830] [I] [eth1] [Pool] [0HL9NB7K5OP17] VarDiff update to 0.54
[2017-11-30 10:53:24.2158] [I] [eth1] [Pool] [0HL9NB7K5OP2F] Share accepted: D=0.1
[2017-11-30 10:53:24.3368] [I] [eth1] [Pool] [0HL9NB7K5OP17] Share accepted: D=0.545
[2017-11-30 10:53:25.0484] [I] [eth1] [Pool] [0HL9NB7K5OOBT] Share accepted: D=0.481
[2017-11-30 10:53:31.3341] [I] [eth1] [Pool] [0HL9NB7K5OP4L] Share accepted: D=0.356
[2017-11-30 10:53:33.1879] [I] [eth1] [Pool] [0HL9NB7K5OOBT] Share accepted: D=0.481
[2017-11-30 10:53:37.3864] [I] [eth1] [Pool] [0HL9NB7K5OP2F] Share accepted: D=0.1
[2017-11-30 10:53:40.0190] [I] [eth1] [Pool] [0HL9NB7K5OOBS] Share accepted: D=0.375
[2017-11-30 10:53:43.6154] [I] [eth1] [Pool] [0HL9NB7K5OOBT] Share accepted: D=0.481
[2017-11-30 10:53:46.5382] [I] [eth1] [Pool] [0HL9NB7K5OOPC] Share accepted: D=0.552
[2017-11-30 10:53:52.2728] [I] [eth1] [Pool] [0HL9NB7K5OOPC] Share accepted: D=0.552
[2017-11-30 10:53:57.2219] [I] [eth1] [Pool] [0HL9NB7K5OP17] Share accepted: D=0.545
[2017-11-30 10:53:57.7361] [I] [eth1] [Pool] [0HL9NB7K5OP17] Share accepted: D=0.545
[2017-11-30 10:53:58.6192] [I] [eth1] [Pool] [0HL9NB7K5OP4L] Share accepted: D=0.356
[2017-11-30 10:54:00.9873] [I] [eth1] [Pool] [0HL9NB7K5OP2F] Share accepted: D=0.1
[2017-11-30 10:54:01.1095] [I] [eth1] [Pool] [0HL9NB7K5OP2F] Share accepted: D=0.1
[2017-11-30 10:54:01.1473] [I] [eth1] [Ethereum Job Manager] New block 4649322 detected