DASH Situation

Are you able to do an early payout? I'm really close to the threshold (Dash) and I kinda need the money asap. Wallet: XkxEvpagNormToUmMTSF9gQV2BkpsDMAgc 

I've already resolved your ticket in transaction 34cc55106079a90ab9a53fb103571b177a85f57e0ce5772f7949155bb42b064b

Oh, ok thanks. I though you just deleted the request.

No, I've only converted it to a ticket.

Praying that this block verifies.  I really like this pool.

Almost every orphan happened below 10% confirmations. My gut tells me this block is going to make it.

This block is our - safe!

Why?

Because there are newer blocks from antpool on the top... and it never happend that we lost a block if antpool has a confirmed newer one...

Spot on as usual.

Hi,

Very high orphan rates may indicate network connectivity problems. You are with cloudflare.com

I know that all exchanges who use cloudflare are having problems 100% of the time (Kraken, Bitstamps etc.) when the load is a bit over some threshold.
To me cloudflare means BAD BAD BAD reliability. Antpool is NOT on cloudflare according to a simple one level dig.

Verify that, it's been 2 days now almost 3 days. Also make sure your network config is tweaked and set for industrial usage, not default install of Ubuntu or else.

I will wait another 24 hours before relocating our D3 or maybe even start our own pool.

Regards,

DNS lookups have nothing to do with this at all.

That is a wild statement.  Most of the pools I use for mining other coins all use Cloudflare, including NiceHash (which is back up).

To be fair, Cloudflare is one of the best hosting services out there... If you think there's an issue, it's not with them.

Did I mentioned DNS ? I've said connectivity, not the same thing as it includes ALL networking protocols, not just DNS.
Anyway your answer helps anyway in my decision making process.

Regards,

That's good to hear. Good luck with your own pool. You are going to need it.

Hint: We are only using Cloudflare for DNS and nothing else. DDos protection is provided by multiple Arbor Networks appliances at our hosting provider.

We miners getting poolmining and poolminigs IPs via cloudflare - it´s OK - maybe we connect a little bit slower with the pool than theoretically possible... but if there is a speed problem than it´s the pool connection time with the deamons not that the pool is running behind cloudflare... I don´t believe in speed/cloudflare problems...

Poolmining is using cloudflare for DNS only.  The server (or plural) is hosted at Hetzner in Germany.  Once you've resolved the domain name to an IP address cloudflare is no longer used (unless another lookup needs to take place, which shouldn't be very frequent).

If you want to eliminate using cloudflare entirely you could add the IP to your hosts file, but if they change the DNS around here you will be pointing at the old IP - so isn't recommended.

Thank you all.
I hope the block makes it.

Regards,

I've reduced the pool fee to zero for the time being to somewhat ease the pain during these dark times.

Der aktuelle ( 795514 ) bleibt trotz das er erst 2% hat auch bei uns... behaupte ich mal.

Die Gebühr wurde bereits 7x bestätigt und es sitzen auch schon mehrere Blöcke aus China obendrauf.

Wenn noch was schief geht... ich habe diesmal Screenshots...

Auf das wir eine glückliche Nacht haben... und ich nicht von der Scheiße träumen muß... ;-)

Dein Wort in Gottes Ohr. Gute Nacht.

That last 1% is taking after any Microsoft update ever.

Result: Yay!!

Good! Thank you.

Guten nacht!

Guten nacht, steven.

Great, all my shares just vanish again and my Dash balance doesn't budge. It's been stuck on 0.075 for days despite my 2 D3's running.

My DASH address is: XtGTHomH4zsYMCj4mGXmiMuj2fY1CcqJ6v

I expect my 0.1 DASH payout otherwise I'm gonna have to take action.

lol, Support. You're gonna have to change the stats to reflect more decimal places so people can't get pissed one block didn't move their stats. 

Anyone mining in this pool is just burning their money on electricity for nothing. Just annoyed it took me 2 days to realise mining here was a total write off. Back on Nicehash now and looks like it's running better than before the hack.

You do realize that for the last two days there's been a legit problem with dash mining across the board, right? Not just with this pool. I only ask because what you're saying says you don't realize that. 

just for shits and giggles go to nicehash and see where they have the when and how to get paid link. you should notice the two ** scroll down and see what they mean

looks like everyone might be over the hump. Was going to suggest that we should vote a order for the orphans to made whole out of the 50% share that goes to node holders. Especially given that it was likely one of their own being an antpool node being the not so innocent party

@POOLMINING - Thank you.

Unser aktueller (795676) wird auch gut... :-)

Aber der Block danach (https://chainz.cryptoid.info/dash/block.dws?795677.htm) ist gemein... geht an antpool und enthält ausser der Fee und den Transaktionsgebühren keinerlei Transaktionen...

Und der hier ist noch kritisch (795713)...

Aber jetzt ist er auch uns - :-)

Sorry people for German...

I´m actually analysing every new block from us and others... I´m nearly sure to know now when the critical time ends for our new blocks... Everytime if one of the chinese pools founds a newer one which has minimum one confirmation for the fee transaction...

Generally: Last 8 hours no orphanes nowhere! Maybe its over...

From Dash Core Dev:

Turned out that some pools were actually rejecting some blocks. They restarted their nodes, so should be ok for now. We are still investigating what caused the issue exactly.

Source: https://github.com/dashpay/dash/issues/1822#issuecomment-354526039

I would bet an arm that those pools were AntPool and ViaBTC. Chinese Scumbags.

Ok, in English for all... ;-)

I watched all our blocks today from the first second the appeared on the blockchain...

Biggest difference to the last two days is that all first fee transaction confirmations comming within seconds and the following confirations comming much faster.

Now I´m absolutly sure that the bad period is OVER - YEAH!

Now we need only 3 days with 30% effort and everything is good again... ;-)

Yeah looks much better now. Thanks again for your monitoring efforts! :-)

hey, i had a few miners pointed at your pool and didnt realize it. could you do a payout to XxGPbbt3Fvm9DvEJN38ZcGeM1QMm7ZYjCD ? thanks.

Also OK... 795839 - 5 confirmations in <30 sec.

Now I´m stopping with monitoring...

Thanks for all the hard work guys.

Indeed thanks for the hard work and finding the solution!

Lets buy our Poolmining support a beer!!!  Great job!!!

whats up with eth pool

never mind ok now

question. so any shares we had two days  are now gone?

yes you had your shares nullified by viabtc or antpool (bitmain) refusing to accept blocks to the chain.

there is nothing oliver can do personally apart from put up a proposal for the antpool node to reimburse orphaned blocks, which they effectively stole

As someone brand new to cryptomining and especially DASH mining, I'm trying to understand the frequency for blocks being discovered.  Now that it looks like we are past the Orphaned Block issue, is it typical for the pool to go 12 hours or more between blocks?  I think the block count (https://chainz.cryptoid.info/dash/) is about 250 new blocks since the last one here at poolmining.  (I am not complaining, I'm just trying to better understand how it works.)  Thank you!

BigDave our block found rate is proportional to the pool hash rate at 18TH/s expect average of 3or4/day

another one just orphaned - 797016

Seen it. Let's hope that shit doesn't start all over. If we get a second one in a row I'll immediately contact the dash team.

is there no way of alerting someone in realtime so that they can monitor whats going on with the orphaning ? this is giving Dash a bad name .... I am already thinking of mining some other X11 coin

This was the 4th dash orphan today...

1st and 2nd going to antpool

3rd to ViaBTC

And the 4th (our) is going to a "nobody" who mines less than our pool. His last recievment was on 12/22/17...

I have an idea how to make a good alert and monitoring system... but I have no time to write such a tool the next time... :-(

Did Antpool and ViaBTC mine those orphans or did they hijack them?

If we have one more orphane in the following 12h I try to cancel my work for a day...

Antpool and ViaBTC are both connected to China.... this D3 miners also come from a chinese company which run them before sending them to us .... seems like one big chinese scam to me ..... 

the damn chinese cant just stop f**king people can they... first they rape south american and africa for minerals and oil and now they wanna loot the cryptoworld too .... zero ethics and values I say

Timing would be perfect. January 1st is probably the worst day of the year to get something done and fewer people will notice.

IF (I don´t believe really) these are 4 legal orphanes then it´s simple math that 2 going to antpool, one to viabtc and the last to a "nobody" like us... nearly 3/4 of x11 hashingpower is located at this two companys - or much to much wordwide ASIC miners are connecting their power with these chinese pools.

It´s up to us private and small business miners to look which currencies have democratic concepts (gpu ram harddisk POS) and to ignore the currencies which can be killed easy by cheap electricity and ASICs...

5 years ago nobody believes in the future power of a bitcoin...

Today nobody believes which power other currency concepts will have in 5 years... ?!

OK, one detail is simmilar to the situation 3 days ago and different to most other orphan periods... Every two orphanes on the blockchain we can see as couples - because the second orphan has same time stamp but only +1 block height... A "regular" orphan has two blocks with same height and time but followed by a regular higher block with also higher time stamp. Two regular follwing orphans with same time stamp I can´t find... only with different time stamps...

Fuck... difficult to explain this understandable... ?!?

797068 - it´s our... I´m sure... :-)

This was the first block today I watched from the 1st second... Confirmation speed and quantity for the fee transaction of this block is slow... not so slow like three days ago but much slower than yesterday...

I'm getting tired of this already.

My miners has issues, the pool has issues. I've been sleepless dealing with this 100k project.

Everybody with a D3 has bought some BS... Believe me - your not alone...

This pool is OK... if a pool has an issue then the D3s manufacturer own pool... the antpool... ;-)

there's some ppl in this pool who have some serious money laid out in D3s. So my frustration levels must be amplified 50 fold for those guys  to see us get pinged this often.

It's reassuring that bitmain's pools are now getting orphans, but I looked at their pool allocation yesterday, and it was pretty fluid. At one point they had ViaBTC making nearly as many finds as Antpool, so they must have algo's that shift the target pool for their D3s.

Sounds like they're betting on mining on top of a stale block to create a longer chain. This would cause all (proper/fair) to switch to the longer chain. The block on the previous chain becomes orphaned. It explains why blocks show in pairs from a single miner. I'm sure it's a "bug" in that miner's code and no malice and greed are involved. Cough.

Does anyone know why the pool strike rate for finding new ones fell so much ? 

law of averages will out dude... today we've just pulled in  our 5th block inside 20 hours.

Just got word from the Dash Team regarding my inquiry towards improving the pool list on dash.org:

Hi Oliver

Seeing the circumstances it might be a good idea to swap the miming pools from top lower and pools from lower upper.
I`ll ask guys if they might do it causing this way some more hashpower into the pools which has less instead of pumping it into the biggest one.

Cheers

Slawek

Another newbie question. Other than the day of bad luck that we had yesterday, the blocks have been coming pretty consistently.  Is it typical for a block to confirm and not see a balance increase?  I've had my ASIC going all day other than a 30 to 40 minute outage due to my ISP.  After Block 799933 confirmed, my balance did not change.  Any thoughts?

Whats your address dave?

I knew that I should've included that!  XcLYn1EgjCL54n9sn6LDwgAb7panVk7Kge  Thanks for checking!

Looks like that ISP outage you've mentioned caused your shares to slip outside of the PPLNS Window:

core.log:[2018-01-07 07:07:20.3649] [I] [PPLNS] XcLYn1EgjCL54n9sn6LDwgAb7panVk7Kge = 76.63 K (76625.8733406494) discarded shares, block 799933

Round 5 in the Payments FAQ explains this scenario: https://poolmining.org/faq#payments

Darn it!  Appreciate the info! Still so much to learn!

Looks like the next one also did not credit me after confirming.  I wonder if there is an issue with my ASIC?  I just realized that my share count is not increasing.  Rebooting now.

Share count is increasing now. I'm just monitoring it.

UPDATE:  I can see my share count increasing again.  Looks like rebooting my miner after an Inet
outage will be best practice going forward.  That cost me about 9 hours
of mining...

Damn that sucks. My sympathies.

Support I had the same question as BigDave. My D3 has been going on for 26 hours but I didnt see any change in my balance from block 800418 or 800428 for example 

Coudl you please help me check too .... my address is XhV7QdqZDTqUaRZGTS61K67DHsrWcVSDPo

Bandar, in my case, I had to look closer and realized that my Share Count was not increasing.  It looks like my miner did not handle losing Internet connectivity very well.  The reboot eventually fixed it, but I think that the existing blocks were likely too far along for me to earn enough credit or shares to gain from them. 

Good lesson learned on checking the equipment and pool more closely after an outage.

@Bandar. I beg to differ:

core.log.1:[2018-01-08 04:15:54.6413] [I] [PPLNS] Adding 0.00183 DASH to balance of XhV7QdqZDTqUaRZGTS61K67DHsrWcVSDPo for 80 K (79999.6134950597) shares for block 800418

core.log.1:[2018-01-08 04:37:40.4292] [I] [PPLNS] Adding 0.00177 DASH to balance of XhV7QdqZDTqUaRZGTS61K67DHsrWcVSDPo for 76.24 K (76240.9811465697) shares for block 800428

core.log.1:[2018-01-08 05:48:16.6849] [I] [PPLNS] Adding 0.00176 DASH to balance of XhV7QdqZDTqUaRZGTS61K67DHsrWcVSDPo for 71.57 K (71566.01147445) shares for block 800458

The confusion is caused by the dashboard not displaying enough decimal digits for the balance. This has been changed for the new dashboard going live today.

I'm locking this thread now as it was never intended to become a free-for-all support thread.