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

DeepBit

donator

Activity: 532

Merit: 501

We have cookies

Quote from: P4man on May 31, 2012, 02:35:23 AM

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.

P4man

hero member

Activity: 518

Merit: 500

Quote from: DeepBit on May 30, 2012, 07:48:51 PM

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 Huh

DeepBit

donator

Activity: 532

Merit: 501

We have cookies

Quote from: Fiyasko on May 30, 2012, 04:13:40 PM

Quote from: [Tycho] on May 30, 2012, 11:49:45 AM

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.

Tittiez

hero member

Activity: 686

Merit: 500

Quote from: Fiyasko on May 30, 2012, 04:13:40 PM

Quote from: [Tycho] on May 30, 2012, 11:49:45 AM

Quote from: cowhead2oo3 on May 29, 2012, 09:12:46 PM

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.

Fiyasko

legendary

Activity: 1428

Merit: 1001

Okey Dokey Lokey

Quote from: [Tycho] on May 30, 2012, 11:49:45 AM

Quote from: cowhead2oo3 on May 29, 2012, 09:12:46 PM

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?

cowhead2oo3

newbie

Activity: 40

Merit: 0

Quote from: [Tycho] on May 30, 2012, 11:49:45 AM

Quote from: cowhead2oo3 on May 29, 2012, 09:12:46 PM

something is wrong xD

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

Sorry and thanks xD...

[Tycho]

hero member

Activity: 742

Merit: 500

Quote from: cowhead2oo3 on May 29, 2012, 09:12:46 PM

something is wrong xD

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

cowhead2oo3

newbie

Activity: 40

Merit: 0

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

fcmatt

legendary

Activity: 2072

Merit: 1001

Quote from: [Tycho] on May 29, 2012, 04:01:59 PM

Quote from: fcmatt on May 29, 2012, 02:24:35 PM

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 ?

Quote from: luffy on May 29, 2012, 02:28:23 PM

the "found in" calculations are totally wrong! Shocked

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

[Tycho]

hero member

Activity: 742

Merit: 500

Quote from: fcmatt on May 29, 2012, 02:24:35 PM

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 ?

Quote from: luffy on May 29, 2012, 02:28:23 PM

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.

luffy

hero member

Activity: 607

Merit: 500

the "found in" calculations are totally wrong! Shocked

fcmatt

legendary

Activity: 2072

Merit: 1001

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.

DeepBit

donator

Activity: 532

Merit: 501

We have cookies

Quote from: splat44 on May 28, 2012, 03:03:26 PM

Quote from: DeepBit on May 28, 2012, 04:13:20 AM

Stale shares are not accepted by the pool.

Not accepted then why is a notion on website?

Stale shares percentage depends on used mining software, hardware, network connection quality and other parameters, so it's very useful to know how many shares were stale.

Quote from: splat44 on May 28, 2012, 03:03:26 PM

What's invalid bocks and when it become invalid?

Invalid block is a part of orphaned blockchain branch, no reward is given to the pool for it, but some pools (including DeepBit) still pay users for the "wasted" round anyway.

Quote from: splat44 on May 28, 2012, 03:03:26 PM

So far I got less than 7% to stale share to my worker place, what is this?

It means that 7% of your submitted shares were discarded as stale. Expected stale percentage for normal miners is less than 1%, so your mining setup is not optimal. May be you are trying to use VERY old mining software or trying to mine with your CPU instead of GPU.
Not enough information to find out the cause yet.

splat44

sr. member

Activity: 384

Merit: 250

Quote from: DeepBit on May 28, 2012, 04:13:20 AM

Quote from: splat44 on May 28, 2012, 03:06:05 AM

As far as I gather, when someone found a new block after I submit my share, it consider stale and wated. Now the real question, how is getting paid for those stale shares?

Stale shares are not accepted by the pool.

Not accepted then why is a notion on website?
What's invalid bocks and when it become invalid?

So far I got less than 7% to stale share to my worker place, what is this?

DeepBit

donator

Activity: 532

Merit: 501

We have cookies

Quote from: splat44 on May 28, 2012, 03:06:05 AM

As far as I gather, when someone found a new block after I submit my share, it consider stale and wated. Now the real question, how is getting paid for those stale shares?

Stale shares are not accepted by the pool.

splat44

sr. member

Activity: 384

Merit: 250

Hi,

I have question about stale shares:

As far as I gather, when someone found a new block after I submit my share, it consider stale and wated. Now the real question, how is getting paid for those stale shares?

Regards

luffy

hero member

Activity: 607

Merit: 500

why "Difficulty history" hasn't been updated any more?

Lem

newbie

Activity: 78

Merit: 0

Since block 181666, "block durations" in the pool stats page are going bananas one more time.

kano

legendary

Activity: 4634

Merit: 1851

Linux since 1997 RedHat 4

Quote from: bitfury on May 25, 2012, 08:29:37 PM

...

PS. And also - this is easily could be verified - first deepbit could review shares and find that they are a bit different from regular miners - as there's only specific subset of work processed because of 82/128 core design (each core processes parts of nonces). Also you could see that bitfury.org really has working hashing power, and not some kind of talks. Actually shares and method of getting work could be easily identified by freq. analysis of some bits of nonce.

You're not the only one that doesn't process the full nonce

All Icarus on cgminer up to 2.4.1 will only reply with nonce values approx 0x00000000-0x5AExxxxx and 0x80000000-0xDAExxxxx
(i.e. stop at ~71% on each of the 2 devices)

Though my pull request after 2.4.1 (that should be in the next version) puts it closer to the finish line a bit over 99%

As you clearly know, though others may not that read this, I'll state the obvious that:
early abort of the nonce range does not change any share/block probability or expectation.

DeepBit

donator

Activity: 532

Merit: 501

We have cookies

Quote from: os2sam on May 16, 2012, 12:46:38 PM

We're almost half way through this difficulty. Shouldn't there be enough data for the average and luck calculation to be present under the stat's page again?

Sorry, I accidentally the whole luckmeter while working on that round duration timer :)
Fixed.

Topic: [DEAD] DeepBit.net PPS+Prop,instant payouts, we pay for INVALID BLOCKS too - page 79. (Read 1601405 times)