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

[[Tycho]]

Is long polling useful at all for solo mining?

Yes, but it's not supported by official bitcoind, so you can't use it in solo mining yet.

[Kiv]

Great to see long polling arrive! I will update my GUI this weekend with support for it.

[[Tycho]]

Update your miners, please.

Long Polling is working now, so you can download latest poclbm miner and use it with DeepBit.
This new feature will eliminate stale shares and your mining efficiency may rise up to ~1.7% more on average (depends on your GPU speed and luck).

What is Long Polling ? Explained here.


Font size was increased in some parts of the site. Is it better or worse now ?

[Neereus]

Font size increase was mostly good. Only the payments section seems to be adversely affected with the date causing it to "double line" the table. But not a big deal so overall the change was good.

[kosovito]

Have a little problem.

Since a couple of days, i cant receive payments, i dunno why, but my maximum value for automatics payments is set to "1", but i have 3btc's in my account.

[FairUser]

Update your miners, please.

Long Polling is working now, so you can download latest poclbm miner and use it with DeepBit.
This new feature will eliminate stale shares and your mining efficiency may rise up to ~1.7% more on average (depends on your GPU speed and luck).

What is Long Polling ? Explained here.


Font size was increased in some parts of the site. Is it better or worse now ?

That certainly is one way to do it!  Not bad...

[[Tycho]]

Since a couple of days, i cant receive payments, i dunno why, but my maximum value for automatics payments is set to "1", but i have 3btc's in my account.

Tell me your login name please, i'll check it.

[kosovito]

Since a couple of days, i cant receive payments, i dunno why, but my maximum value for automatics payments is set to "1", but i have 3btc's in my account.

Tell me your login name please, i'll check it.

Fixed

Thanks

[Neereus]

Currently using the GUI version of poclbm with long polling. (The new one)
I have actually gotten 4 stale shares since using it, when before long polling I never got one.
Just wondering how normal that is?

Edit: Just checked the console, seems there were some "long poll exceptions". I suppose it could have been because of these?

[wootwoot]

When will the graph section of the website be functional?

[BitLex]

it seems i get more and more of these

Stale hash. To reduce stales, use long polling, e.g. latest m0mchil's python miner

while already using latest m0mchil's python miner.

[marcus_of_augustus]

Hi Tycho,

my timezone is not supported, my machines are operating in Timezone GMT+13

would you mind adding that one?

cheers.

[[Tycho]]

my timezone is not supported, my machines are operating in Timezone GMT+13
would you mind adding that one?

Fixed.

[[Tycho]]

it seems i get more and more of these

Stale hash. To reduce stales, use long polling, e.g. latest m0mchil's python miner

while already using latest m0mchil's python miner.

I see that you are sending more stale shares than expected (but less than 1%, anyway).
Trying to find the cause of this.

[ronaldmaustin]

Please remove the word "fair" from your thread title. Implying that Slush is purposefully "unfair" is an offensive patently false lie propagated through an unwillingness to understand statistics. (and pure malice by some)

Slush has shown the statistical charts proving that the score based reward system distributes just as equally as a shares based reward system.

I also "like" the implication that a 3% fee is more "fair" than a 2% fee.

Please remove the words "patently false" from your post.  Any lie is, by definition, patently false.  Please also remove the words "Slush" and "purposefully" since there is nothing in the original post mentioning Slush or that anybody has done anything on purpose.  While you are at it, remove the word "imply"  since the original statements did not imply anything more than stated.  "Propagated" is improper since the misunderstanding of statistics actually diminishes on this board, as good people like yourself explain probability.  "Unwillingness" is also incorrect, since the people who spread rumors are usually just stupid and not "unwilling" to "understand".  In fact, we know nothing about their level of understanding, so strike that too.  Your post must read, "Please the thread title offensive lie statistics."  When you are done editing, please leave this forum for one week in compliance with your new rule that one forum member can direct another on what he or she must do.
 

[bombo999]

troll

[[Tycho]]

UPDATES:

• Now you can see number of contributed shares per each worker.
• Stale shares percentage is also shown. If you are sending more than 1% stale shares and are mining with GPU, please update your miner to the latest version of m0mchil's poclbm miner.
• Worker names are shown in red color if no share was received in the last 30 minutes.

[mrballcb]

it seems i get more and more of these

Stale hash. To reduce stales, use long polling, e.g. latest m0mchil's python miner

while already using latest m0mchil's python miner.

I see that you are sending more stale shares than expected (but less than 1%, anyway).
Trying to find the cause of this.

I've got two machines mining, both at fairly low bitrates, 6M and 73M.  Both of them are running the latest poclbm.  My status page (for accounts tlyons@ive.*) show my two accounts at 1.91% and 1.49% stale, respectively.  Is that statistic over the life of the account?  Because I just started using the new poclbm about 24 hours ago, but was using it for a couple weeks before that.

In addition, I see log entries such as this occasionally (times are UTC -0700) :

Code:

15/03/2011 06:40:30, 5ab08224, accepted
15/03/2011 06:41:38, long poll: Deepbit is temporarily unavailable
15/03/2011 06:42:13, ea0227f4, accepted
15/03/2011 06:42:57, d260477e, accepted
15/03/2011 06:43:45, long poll: new block

I suspect the last line is long polling working as suspected, where the server pushes out an update request to me when it receives a new block.  I also suspect the second line is just you doing work on the system and restarting things, but that's a guess.

I also see this occasionally:

Code:

15/03/2011 08:41:16, long poll: backend error

Is there anything I might want to tweak on this?

Regards...        Todd

[[Tycho]]

I've got two machines mining, both at fairly low bitrates, 6M and 73M.  Both of them are running the latest poclbm.  My status page (for accounts tlyons@ive.*) show my two accounts at 1.91% and 1.49% stale, respectively.  Is that statistic over the life of the account?  Because I just started using the new poclbm about 24 hours ago, but was using it for a couple weeks before that.

Look at each worker's page - there is a time and date of last reset for those counters. Today i'll add manual reset button for users.
If you switched to long polling just one day ago, then it includes old results too. If everything is working correctly, then stale percentage should be decrementing slowly.

I also see this occasionally:

Code:

15/03/2011 08:41:16, long poll: backend error

Is there anything I might want to tweak on this?

This one is already fixed.

[Dr. Arnold]

Hey Tycho, Great pool you've got running however I've been using the latest version (2011/03/11) m0mchil's python miner but it seems that long polling isn't working for some reason.

I get these messages when mining occasionally:

15/03/2011 17:41:31, long poll: new block
Stale hash. To reduce stales, use long polling, e.g. latest m0mchil's python min

And my stats page says I've been submitting 0.97% and 2.21% stale shares for my miners

Any idea how I can get long polling working? There's no extra flags required to enable it, correct?