[DEAD] DeepBit.net PPS+Prop,instant payouts, we pay for INVALID BLOCKS too

[[Tycho]]

Time/Link   Found in Your   Total   Reward
29.05 12:09:48   1h 35m     10   12601     0.0xxx
29.05 12:05:19   1h 30m     8   7930     0.0xxx
29.05 12:00:23   1h 25m     750   984518     0.0xxx

The amount of my shares compared to the pool seems very odd when looking
at the amount of time to solve a block for the last two blocks.

Did something just recently change? And yes I read back a few pages of this
thread but did not find anything related.

No, nothing was changed. Shares should be accounted correctly.
Are you sure that your timezone is set ?

the "found in" calculations are totally wrong! :o

Yes, still not fixed. It doesn't affects anything, just check the block timestamp instead of "found in" until this issue is resolved.

[1713461758]

1713461758

[fcmatt]

Time/Link   Found in Your   Total   Reward
29.05 12:09:48   1h 35m     10   12601     0.0xxx
29.05 12:05:19   1h 30m     8   7930     0.0xxx
29.05 12:00:23   1h 25m     750   984518     0.0xxx

The amount of my shares compared to the pool seems very odd when looking
at the amount of time to solve a block for the last two blocks.

Did something just recently change? And yes I read back a few pages of this
thread but did not find anything related.

No, nothing was changed. Shares should be accounted correctly.
Are you sure that your timezone is set ?

the "found in" calculations are totally wrong!

Yes, still not fixed. It doesn't affects anything, just check the block timestamp instead of "found in" until this issue is resolved.

I should have said found in was wrong like the other person. I said shares looked wrong due to found in being so long yet i had few shares. Reward is normal. Time zone set correctly. Sounds like known issue popping up again. Thanks

[cowhead2oo3]

29.05 20:44:35   9h 10m    7500   9474710     0.0xxx
29.05 17:38:53   6h 04m    1233   2379184     0.0xxx
29.05 17:10:31   5h 36m    2274   2575146     0.0xxx
29.05 16:14:51   4h 40m    743   1066043     0.0xxx
29.05 15:59:12   4h 24m    539   825492     0.0xxx
29.05 15:48:50   4h 14m    212   289992     0.0xxx
29.05 15:43:06   4h 09m    3887   6744061     0.0xxx

something is wrong xD

[[Tycho]]

something is wrong xD

This was mentioned a few times already.
A temporary fix was implemented now :)

[cowhead2oo3]

something is wrong xD

This was mentioned a few times already.
A temporary fix was implemented now

Sorry and thanks xD...

[Fiyasko]

something is wrong xD

This was mentioned a few times already.
A temporary fix was implemented now

Did this fix cause the "found in" block times on the stats page to all show nulls?

[Tittiez]

something is wrong xD

This was mentioned a few times already.
A temporary fix was implemented now

Did this fix cause the "found in" block times on the stats page to all show nulls?

Haha Tycho you so funny.

[DeepBit]

This was mentioned a few times already.
A temporary fix was implemented now :)

Did this fix cause the "found in" block times on the stats page to all show nulls?

Yes, it prevents wrong data from being displayed.
Round timer will be enabled again after appropriate repairs.

[P4man]

Round timer will be enabled again after appropriate repairs.

Have to say, Im perplexed and mildly amused by the irony; you seem to have no problems keeping the biggest pool up with basically zero down time, extremely low stales etc, yet calculating the difference between two times on a webpage is a problem that takes months and countless attempts to fix? I would assume you store those date/times as unixtime in the database, and its literally as simple as subtracting 2 numbers and applying strftime to the result 

[DeepBit]

I would assume you store those date/times as unixtime in the database, and its literally as simple as subtracting 2 numbers and applying strftime to the result  ???

Yes, subtracting two numbers is easy, but first I have to find some elusive glitch that causes round end time to be missed in stats counter.
Of course I can just subtract block timestamps that are always correct and get stats table instantly fixed, but this way I won't find the cause of that glitch.

Sorry for the inconvenience, I hope to solve this problem today.

[smracer]

Is something going on right now?  My cgminer screens show I am connected to Deepbit and all shares are saying accepted but no shares are registered on my account screen. 

[DeepBit]

Is something going on right now?  My cgminer screens show I am connected to Deepbit and all shares are saying accepted but no shares are registered on my account screen.

No, currently everything should work fine.
PM me your login name.
Are you talking about the workers table ?

[martychubbs]

How about Team RP2012 join with America?

[P4man]

Im not sure, but I may have stumbled upon the cause of your timing issue. Is it possible the website is not showing orphaned blocks and that gets the timing confused?

These 2 blocks were orphaned and reported by blockchain as originating from deepbit. I know blockchain isnt all that reliable, so it could be wrong, but since they dont show up on blockorigin at all, you may want to check if indeed those blocks werent yours:

00000000000008f768a2d460398108897d26ec3f99d9017463162116e720a5f4
0000000000000a840c96d0bd6555aa98a18fd380873ed1192db59f3ea6cc71b3

[DeepBit]

These 2 blocks were orphaned and reported by blockchain as originating from deepbit. I know blockchain isnt all that reliable, so it could be wrong, but since they dont show up on blockorigin at all, you may want to check if indeed those blocks werent yours:

00000000000008f768a2d460398108897d26ec3f99d9017463162116e720a5f4
0000000000000a840c96d0bd6555aa98a18fd380873ed1192db59f3ea6cc71b3

This issue can't be related to invalid blocks at all, it only affects stats collection.
As for those blocks, you can check if they are present in the stats table or not, block hashes are provided there.

[hi]

It appears that deepbit has had bad luck for last few months...my workers are not getting their daily avg of BTC for quite some time now. 

[rjk]

It appears that deepbit has had bad luck for last few months...my workers are not getting their daily avg of BTC for quite some time now. 

If you are using proportional scoring, your "bad luck" would be due to pool hoppers taking the profits. The only thing that changes the PPS price (if you are using that) is the difficulty.

[[Tycho]]

It appears that deepbit has had bad luck for last few months...my workers are not getting their daily avg of BTC for quite some time now.

Yes, there was a bad luck run some weeks ago, but looks like it's back to normal again.

[DeepBit]

We are experiencing some internal connectivity issues, I'm working on this.

UPDATE: Solved.

[DeepBit]

Some additional issues were caused by that bug with missed round ends. Sometimes a small amount of shares may be accounted for next blocks in the stats table instead of just finished one. No shares were or will be lost, but for someone this may be important.
Now I found out what should be done to prevent this and working on the fix.

Sorry for inconvenience.