Topic: [DOWN] Bitlc.net - P2SH, No invalid blocks, Custom payouts, EU, 0% fee, LP - page 27. (Read 180987 times)

The pool had a stats glitch, the pool had solved three blocks, but for 10 hours the stats page thought we were still working on the first round. That gave the appearance of a 16 hour round. It was fixed and the payments went out without a hitch.


I get a different answer. The chance of solving a block depends on difficulty.

Here is the probability of an individual hash solving a block: http://blockexplorer.com/q/probability

The current probability of solving a block with an individual hash is: 0.0000000000000001489590023459044440534704278888966655358

The current probability of not solving a block with one hash is therefore :
( 1 - 0.00000000000000014895900234590444 ) = 0.99999999999999985104099765409556

Let's call that chance of not solving with an individual hash (a number very close to 1, or 100%) "Z".

The probability of not solving a block with two hashes is Z * Z, better written as Z^2. Still nearly 100%. We need more hashes.

The pool averaged about 600Ghash per second. That is 600,000,000,000 hashes per second x 60 seconds per minute x 60 minutes per hour x 16 hours in the "imaginary" round. Probably around 34,560,000,000,000,000 hashes. That's another preposterous number, so I'll call that "hashTotal"

A pool trys hashTotal hashes in 16 hours, so the chance of not finding a block in that time is Z ^ hashTotal.

.99999... ^ 3.456E+16 = .02156 = 2.16% chance of not solving a block in 16 hours. Not improbable. Bruteforcing the nonce statistics don't enter into it, since everybody is doing random work on multiple blocks. Actual calculation done in Excel, not Matlab, so feel free to verify the percentage for me.

The reason, why 5.2 has 100% is rounding error. It could truly be possible that no block is found the next 7 days, but it is extreme unlikely.

Seems they fixed it though, there were 3 blocks found within that 18 hour timeframe & the software bugged.

They just credited the missing blocks a few mins ago.

At this point it does seem a bit weird

The current round should be mathematically impossible.


The statistical probability of finding a block at 5.2*1566776 shares becomes 1 [100.00%].

However the site claims no block has been found after 5.6*1556676 [8717385 shares]

Jine, any comments on what's happening with the pool, hours and hours of poor connectivity with stats reflecting some troubles (hash rate bouncing). Are you getting hammered still or is something else up?

I seem to have had a large amount of connectivity issues today... i am down by like 1/3 of my normal hash rate that I am getting credit for... More issues?

The CDF is already at 99.999% probability of finding a block per Poisson distribution table since 4 hours ago.
It's now at 8 million shares and 16 hours @ 600ghash/s.

Mathematically very, very improbable, if not practically impossible
http://portal.acm.org/citation.cfm?doid=355993.355997
http://www.itl.nist.gov/div898/handbook/pmc/section3/pmc331.htm

(The probability of not solving a block within 960 minutes at current difficulty with 600ghash/s is <0.0000000000000001% and decreases exponentially after each passing minute)

It's seems to be under DDoS.

Is there a reason, why this pools sometimes has problems with sending works?

Every now and then the hashrate goes down about 50% and recovers.

I'm writing a script to monitor all my btc related stats
I didn't know about the API, it will be ok then, thanks

CSRF-protection.

Why are you trying to login using script?
I'd suggest you to wait a few days and then use our API instead.

The method of signing in, url's etc will change in the next release.

While trying to login with a PHP script using a proper token and cookies, I just get this error:

What's wrong?

It seems like it was the same botnet of nodes as before - this time they we're connecting via a mining proxy or similar (due to they're own IP's got blocked).
Was rather easy to find out what account and from which IP - and ban those.

Seems stable again now.

We're expanding our environment due to this, a real load balancer (with sticky connections) is set up and we're creating multiple nodes with pushpoold to be able to handle even that amount of connections (~6-10k established connections from the same IP - this time)

I'll keep you guys updated.

Think your pool got attacked again, latency through the roof

Edit: my hashrate returned to normal after the long block.

same thing with mine

Jen

Same.

Pool having issues? my miners are having trouble getting work..

i slowed down as well ,  hopeing this goes back up again


Jen

The server is suddenly pinging at about 430ms
I think there is a very high chance of your site being under a DDoS attack.

Just a heads up to know it's prob. not caused by your software.