Author

Topic: [0Th]Ozcoin Pooled Mining |DGM 1%|Stratum+VarDiff port 80|NEW CN mining| - page 102. (Read 398185 times)

donator
Activity: 919
Merit: 1000
Sounds like mined shares aren't submitted to the database correctly. Afaik there is a feature that caches all those shares, so their value won't be lost and credited as soon as the issue is fixed.

Could you name the server you mine on (us / us2 / eu / eu2)?

I'm on us2.

M

I'm on eu.
full member
Activity: 199
Merit: 100
Sounds like mined shares aren't submitted to the database correctly. Afaik there is a feature that caches all those shares, so their value won't be lost and credited as soon as the issue is fixed.

Could you name the server you mine on (us / us2 / eu / eu2)?

I'm on us2.

M

I guess us2 server has/had problems submitting shares on time from ecoinpool into the database.

If your reported hashrate appears higher than normal - this is the effect of shares from the past minutes/hours are catching up and get credited.

Just left a message for us2 admin on irc, he'll take a look into it - thanks for your feedback.
legendary
Activity: 1540
Merit: 1001
Sounds like mined shares aren't submitted to the database correctly. Afaik there is a feature that caches all those shares, so their value won't be lost and credited as soon as the issue is fixed.

Could you name the server you mine on (us / us2 / eu / eu2)?

I'm on us2.

M
full member
Activity: 199
Merit: 100
Sounds like mined shares aren't submitted to the database correctly. Afaik there is a feature that caches all those shares, so their value won't be lost and credited as soon as the issue is fixed.

Could you name the server you mine on (us / us2 / eu / eu2)?
legendary
Activity: 1540
Merit: 1001
This is the best pool I've tried so far, but it is also the pool that does weird stuff (admittedly little insignificant stuff). Just now I logged into my account and my workers were all reported as being offline even though my hashrate was reported as normal and my home worker was submitting shares no problem. I logged the home worker off and back on and then all my workers reported as being online. As far as I can tell, my workers were never offline, except when I logged off-on with the home worker. To this I say,  Huh, but also, meh- Cool .  

I observed the same: the hashrate of my workers was reported as 0, while the total of all workers combined seemed correct (25-35 GH). My 24h-income dropped from 15 to 5 BTC. It might be just bad luck, but to me it looks like shares were not accounted correctly.

Same problem here.  Usually takes 8-9 hours for me to get a payout, yesterday it took 17 hours, and it wasn't double the normal payout.  I don't think the difficulty increased that much, it was the wrong day anyhow.

Ozcoin admins?  What's going on?

EDIT: the pool might be catching up.  My reported hash rate has increased significantly over the last 1/2 hour or so.

M
hero member
Activity: 628
Merit: 504
This is the best pool I've tried so far, but it is also the pool that does weird stuff (admittedly little insignificant stuff). Just now I logged into my account and my workers were all reported as being offline even though my hashrate was reported as normal and my home worker was submitting shares no problem. I logged the home worker off and back on and then all my workers reported as being online. As far as I can tell, my workers were never offline, except when I logged off-on with the home worker. To this I say,  Huh, but also, meh- Cool

I observed the same: the hashrate of my workers was reported as 0, while the total of all workers combined seemed correct (25-35 GH). My 24h-income dropped from 15 to 5 BTC. It might be just bad luck, but to me it looks like shares were not accounted correctly.
Same here, I'll wait for a few more hours and if estimated income wont start to clime back I'll have to switch  Sad
donator
Activity: 919
Merit: 1000
This is the best pool I've tried so far, but it is also the pool that does weird stuff (admittedly little insignificant stuff). Just now I logged into my account and my workers were all reported as being offline even though my hashrate was reported as normal and my home worker was submitting shares no problem. I logged the home worker off and back on and then all my workers reported as being online. As far as I can tell, my workers were never offline, except when I logged off-on with the home worker. To this I say,  Huh, but also, meh- Cool

I observed the same: the hashrate of my workers was reported as 0, while the total of all workers combined seemed correct (25-35 GH). My 24h-income dropped from 15 to 5 BTC. It might be just bad luck, but to me it looks like shares were not accounted correctly.
donator
Activity: 305
Merit: 250
Just noticed on the bitcoin balance page:
Code:
Block	Date	                     Conf.
189119 2012-07-14 19:09:44 0
189088 2012-07-14 17:49:36 23
189063 2012-07-14 15:48:39 48

Even though the blockchain is at 189131
legendary
Activity: 1540
Merit: 1001
This is the best pool I've tried so far, but it is also the pool that does weird stuff (admittedly little insignificant stuff). Just now I logged into my account and my workers were all reported as being offline even though my hashrate was reported as normal and my home worker was submitting shares no problem. I logged the home worker off and back on and then all my workers reported as being online. As far as I can tell, my workers were never offline, except when I logged off-on with the home worker. To this I say,  Huh, but also, meh- Cool

I've observed that as well.  The widget goes bonkers reporting workers offline, when in fact, the website sometimes reports them offline.  A moment later, as you saw, they are back.



M
legendary
Activity: 1820
Merit: 1000
This is the best pool I've tried so far, but it is also the pool that does weird stuff (admittedly little insignificant stuff). Just now I logged into my account and my workers were all reported as being offline even though my hashrate was reported as normal and my home worker was submitting shares no problem. I logged the home worker off and back on and then all my workers reported as being online. As far as I can tell, my workers were never offline, except when I logged off-on with the home worker. To this I say,  Huh, but also, meh- Cool
legendary
Activity: 889
Merit: 1000
Bitcoin calls me an Orphan
us2.ozco.in is back up and running. We will update the DNS in a couple days. Very sorry for the downtime on this mining node. Hard drives going out is never a good thing.

donator
Activity: 2058
Merit: 1007
Poor impulse control.
I tried to compute the probability of these two things happening back-to-back, but it appears to be beyond my statistical knowledge. I believe it is some kind of infinite series like the following:

sum N = 0 -> infinity (P(3) * (1-P(1))^n * P(4))

Where P(x) = Probability of finding x blocks in a row = (1.5/14.87)^x

If this is correct, it appears to converge on .000001053614510631% Smiley

Almost but not quite. Getting three in a row means the fourth one isn't an Ozcoin block. So your probabilities are (using the Ozcoin network proportion as 1/10):

1/10 * 1/10 * 1/10 * 9/10 = 0.0009

You can model the number of ozcoin blocks as a shifted geometrically distributed variable, with a non-Ozcoin block as a "success". The probability density of the shifted geometric distribution is
Code:
p*(1-p)^(k-1), where k is the number of trials for one success, and p is the probability of success
In this case the number trials is the number of Ozcoin blocks before one non-Ozcoin block, and p is the probability of a non-Ozcoin block (~ 9/10).

Knowing this you can use the cumulative distribution function (CDF)  for a shifted geometric distribution to find the probability of a number of blocks in a row greater or lesser than a given number. The CDF for the probability of the number of Ozcoin blocks in a row being greater than a given number (the "upper tail") is:
Code:
(1 - p)^k for the upper tail

Armed with these two tools it's easy to work out the probability density (the probability of an exact number of Ozcoin blocks in a row occurring) and the upper tails of the cumulative probability (the probability of a number of Ozcoin blocks in a row being grater than some number).

So, getting back to your answer, the probability density for 'x' blocks in a row is 1/10*(9/10)^(x-1), but the sum of all probabilities converges at exactly 1.



Edit:

While I'm on the subject of geometrically distributed variables, my 2% fee Pay-Per-Share is now available for Ozcoin.

Details at: https://bitcointalksearch.org/topic/glbse-ozcoin-miner-variance-protection-available-now-92534
GLBSE link: https://glbse.com/asset/view/MEI.OZCOIN.B
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
See if my bad stats is any better Smiley

Since the chance of finding 1 block = 1 (since there is no restriction on when it is found)

The chance of finding a 2nd block after it is simply just (pool hash rate/network hash rate)
So for 2 in a row it's about 10%?
So 3 in a row would be about? 1%?
So 4 in a row would be about? 0.1%?
newbie
Activity: 32
Merit: 0
First ever OzCoin hat trick?

Blocks 188893, 188894, and 188895 were all found by OzCoin.

Oh, and then didn't stop there. Needed to set another pool record, so blocks 188905, 188906, 188907, and 188908 were also all found by OzCoin.


Probability at any time of getting the next 3 blocks in a row with pool rate of 1500GH/s and network rate of 14.87 TH/s?  0.1026%
Probability of getting the next 4 blocks in a row with those rates in that time? 0.01035%

I tried to compute the probability of these two things happening back-to-back, but it appears to be beyond my statistical knowledge. I believe it is some kind of infinite series like the following:

sum N = 0 -> infinity (P(3) * (1-P(1))^n * P(4))

Where P(x) = Probability of finding x blocks in a row = (1.5/14.87)^x

If this is correct, it appears to converge on .000001053614510631% Smiley
legendary
Activity: 1540
Merit: 1001
Had a little burp on the us.ozco.in server. It might be related to when gpumax went down. At least it was the same time. All is back to normal and shares are starting to catch up.

Something funny is going on.  My confirmed balance is 1.6x my payout balance.  I'm on PPS.  My PPS balance keeps jumping to 0, and my confirmed balance keeps increasing.

I'm also getting NMC credit, which I didn't think was possible when on PPS.

M
legendary
Activity: 889
Merit: 1000
Bitcoin calls me an Orphan
Had a little burp on the us.ozco.in server. It might be related to when gpumax went down. At least it was the same time. All is back to normal and shares are starting to catch up.

legendary
Activity: 952
Merit: 1000
us.ozco.in and us1.ozco.in are different servers in the same DC
us2.ozco.in was in chicago but had a hdd failure so the url is now pointed to us1's IP
hope that clears up any confusion
us.ozco.in runs between 800Ghash and 1Thash most of the time us1 at about 300Ghash
the 2 eu servers even lighter load. I mine them all from Australia without issues Smiley

Thanks for the clarification Graet.

Aye!
legendary
Activity: 1820
Merit: 1000
us.ozco.in and us1.ozco.in are different servers in the same DC
us2.ozco.in was in chicago but had a hdd failure so the url is now pointed to us1's IP
hope that clears up any confusion
us.ozco.in runs between 800Ghash and 1Thash most of the time us1 at about 300Ghash
the 2 eu servers even lighter load. I mine them all from Australia without issues Smiley

Thanks for the clarification Graet.
vip
Activity: 980
Merit: 1001
us.ozco.in and us1.ozco.in are different servers in the same DC
us2.ozco.in was in chicago but had a hdd failure so the url is now pointed to us1's IP
hope that clears up any confusion
us.ozco.in runs between 800Ghash and 1Thash most of the time us1 at about 300Ghash
the 2 eu servers even lighter load. I mine them all from Australia without issues Smiley
legendary
Activity: 952
Merit: 1000
Please consider using us1.ozco.in
us.ozco.in is under the heaviest load all the time Smiley
cheers
Graet

wait, are us1.ozco.in and us2.ozco.in the same?

No, ones in Texas and the other's in Chicago

How come when I ping them, I'm getting the same ip address? 67.210.248.58?
Jump to: