Decred DCR Wyoming

Peercoin PPC Mining Calculator Usd. Okay, now coinmine found a block with 1 share. Finder 'estebun961'. Obviously estebun961 should have received the entire block reward (minus 1% fee).

No other miner in the pool should have received any reward for this block. However when you navigate to, you will see that a total of 305 miners have received rewards for this particular block (pretty much all in the pool I guess), with miner 'estebun961' getting just 0.01461608 DCR. Don't get fooled by the 'round shares' and 'round%' in that statistics because it is bogus and always has been on coinmine (I reported this to back in February).

But the received reward in the column 'amount' is correct because it fits to the data shown under 'transactions'. I noticed this obvious misconfiguration which affects the mining rewards of all miners two days ago.

Coinranking Decred (DCR) price information, coin market cap and trade volume. View the coin chart with a detailed price history. Decred Stake Pool Overview This pool is a 'pay what you want' pool. You may decide what pool fee to set when purchasing tickets with a minimum setting of: 1%.

And a total of 296 miners received payments for it. Obviously that's not how it should be, since it was likely only one or two miners that have contributed shares to that block. Okay, here is another issue with coinmine that didn't exist until appr. Six hours ago. If I connect only one worker, it will hash nicely with almost zero rejects.

As soon as I connect more workers they will produce 50% or more rejects. Not those rejects with additional messages but just 'rejected' instead of 'accepted' in each cgminer line ('Rejected blabla Diff blabla GPUx'). I can only suspect that this is maybe some anti-DDOS measure.

Like one incoming connection per IP is okay but more than that is treated as DDOS and somehow blocked? But it isn't actually blocked, the second and next workers can connect. They just produce appr. It doesn't mention which worker connects first. The first one is hashing nicely with zero rejects. All others get 50%+ rejects. In the past I could connect all workers and they all worked nicely.

No change in config on my side whatsoever. Hi - you are very fast in writing. Lets go one by one - payout system - it is very difficult to find what happened with 'lucky finder' but for sure it should not be only one person, because there was much more shares in DB at that time. There may be several reasons why system detected only one miner but most probably it was when block was already in wallet and it was detected by pool however getwork/stratum server still did not write shares into DB (not necesarily for that block). In this case pool has a 'failover mode' when it takes share which more or less matches to the time when block as found.

It may be that it took all shares for previous block and then for net block only one share remained in DB. Not sure if this is clear enough It may happen when you have thousands of miners and there is some interruption in network connection or just longer DB query. Next one - rejection rate - is it still happening? I am receiving alerts about DDoS attacks from my provider but they may be fake and they are probably related to shitty cgminer longpoll implementation when it creates several connections to server and never close anything, which ends up in situation when there is 100 workers on one server and 6000 connections.

Thats why stratum is better and may handle workers better even with Decred getwork-over-stratum implementation. I will try to add additional servers for getwork/longpoll but I must calculate if I will not be loosing money. Yes, still 50%+ rejects whenever I connect more than one rig.