Pages:
Author

Topic: [NEW POOL & MINER] - BitcoinPool.com - Jump In! ~NO FEES~ :) - page 10. (Read 101960 times)

sr. member
Activity: 258
Merit: 250
I updated my copy of poclbm and haven't gotten any stales since, so I guess that was the problem. Thanks.

Cool, glad to see it worked.
full member
Activity: 140
Merit: 101
I updated my copy of poclbm and haven't gotten any stales since, so I guess that was the problem. Thanks.
sr. member
Activity: 258
Merit: 250
What would you consider a safe amount in % of stale shares with long polling with 270 Mh/s? I vary, but my top would be 0.75%, atm according to deepbit's pool I have 0.57% though

< 1%.
full member
Activity: 126
Merit: 100
What would you consider a safe amount in % of stale shares with long polling with 270 Mh/s? I vary, but my top would be 0.75%, atm according to deepbit's pool I have 0.57% though
full member
Activity: 140
Merit: 101
I thought I was already using a miner with long polling support. I'll take another look.
sr. member
Activity: 258
Merit: 250
*** ATTENTION ***

I have temporarily enabled accepting shares for the previous block. This will temporarily prevent you from getting invalid/stale shares.

I'm doing this as a favor to give you time to update your miner to one with with long polling support.

I will be switching back to current block only in a few hours from now. Please update your miners to one that has support for long polling.

We will be back to current block only by the end of the day.

This is the last time we will be paying this courtesy to miners in our pool.

Thank you.
sr. member
Activity: 258
Merit: 250
I seem to be getting stale/invalid shares at about twice the rate on Bitcoin Pool that I get with slush's pool (26/1900 versus 131/17300). This seems like a pretty big difference to be explained by normal variance, especially since BitcoinPool is advertising "no more stale shares". What other explanation is there?

No more stale shares is only for the miner from here
If you use something else like me (puddinpops) you will get stale shares here

excuse me puddinpop  I was told it's rude if your not exactly correct in a persons handle
I think it's rude to correct for minor stuff like exact spelling of aliases but that's only me

Thats entirely wrong Bobr.

"No more stale shares" is if you're using a miner that has long polling, and even then, there is still the rare possibility that you could submit a share at the same time long polling updates you, and it will be invalid.

We switched to only accepting shares for the current block, which requires that long polling is enabled for you to not be submitting invalid/stale shares.

Miners that support long polling:
poclbm-mod
poclbm
kiv's gui frontend for poclbm
jgarzik's cpu miner

...possibly some others, but I haven't checked in a day or two.
sr. member
Activity: 1344
Merit: 264
bit.ly/3QXp3oh | Ultimate Launchpad on TON
In regards to what happened the other day with the network being flooded with unconfirmed transactions and the delay in payouts that it caused, we think we have a solution.

Geebus and I want to make sure that you get paid at a normal rate, and the way we can do that is to apply a 0.01 tx fee to the payment, but if we did 0.01 for 100 users, that's 1.00 BTC just to get all payments out the door with priority.  The solution is a new patch for bitcoin called sendmanytx, and sendmanytx allows us to make many payments in 1 transaction vs making 100 individual payments in 100 individual transactions.  With sendmanytx, would could make a single payment to many parties in 1 transaction, and then we could apply a 0.01 tx fee to that transaction to make sure it gets priority when blocks are processed.

We'll be making this change sometime in the next week. 
However, my day job is requiring a lot of me right now and I have to make that priority 1 in my life, so I'll get to this when I have time.

Thank you for your patience and understanding while we attempt to adjust our pool to be more consistent. Smiley
sr. member
Activity: 1344
Merit: 264
bit.ly/3QXp3oh | Ultimate Launchpad on TON
That explains why I'm getting some stale shares, but not why I'm getting more.

If you use our miner, poclbm-mod, it support long polling which will reduce the number of stale shares.
Poclbm-mod also works through the entire getwork, and when it is finished with it's work, it will ask for more work.
Poclbm-mod will not find MORE or LESS shares than the regular poclbm, it will find the SAME number of shares but does this with less getwork requests.

If you believe your getting more shares with poclbm-mod, I'd be very curious to see some logs from poclbm vs poclbm-mod. 
We ran both poclbm and poclbm-mod until it found 1000 shares and recorded how long that took.  It was about the same amount of time, give or take a minute. 
Each test took about 10 hours.

sr. member
Activity: 1344
Merit: 264
bit.ly/3QXp3oh | Ultimate Launchpad on TON
I'm getting the impression  http://www.bitcoincharts.com/bitcoin/
runs in conjunction with this pool

No.  Bitcoincharts.com is not run by us.
bob, it's just a matter of luck here.  I don't know why slush's pool isn't having the same problem as ours. 
Don't you think you should maybe ask him?
member
Activity: 112
Merit: 10
I have a new question
This is NOT a complaint
I've been watching http://www.bitcoincharts.com/bitcoin/
seems free confirms/transfers are going up & up  taking longer
especially for small or multiples of one on one transfer
Their has not been a single free transfer since before 13:00 utc today
Shortly before this pool confirmed (hit 120) for its last block http://www.bitcoincharts.com/bitcoin/
showed no unconfirmed  ... funny now it's chart just keeps going up & up again with uncompleted

while others offer a set amount of bitcoin and that is send it to several in one single shot
even including .01 or .02 bitcoin for doing so

Can't this be done here ??
I'd rather see the 50 per pool loosing a few cents per round than wait 6-12 or more hrs to get a payment confirmation
 
Just as a side note slush's pool doesn't seem to suffer from this problem 
I'm no expert on bitcoin or bitcoin pools
I'm just asking WHY ?


I'm getting the impression  http://www.bitcoincharts.com/bitcoin/
runs in conjunction with this pool
member
Activity: 112
Merit: 10
BTW this pool has NOT had a round go over a day in the past 10  blocks
so I'm beginning to DOUBT your claims
Current Round Duration: 01d 01h 50m 39s

Look at the time of my first post in this thread (saying I was joining in). It was about 15 hours ago. I'm not sure what room there is for doubt.

Ok  a half hr over a day when you made that statement

It's luck  my statement still stands correct
ok you're the jinks
you joined and now its over a day for a block

kidding aside it's just luck


EDIT:
we just hit .. hope that makes your day
full member
Activity: 140
Merit: 101
BTW this pool has NOT had a round go over a day in the past 10  blocks
so I'm beginning to DOUBT your claims
Current Round Duration: 01d 01h 50m 39s

Look at the time of my first post in this thread (saying I was joining in). It was about 15 hours ago. I'm not sure what room there is for doubt.
member
Activity: 112
Merit: 10
(Another question: why, right after I say 8.0 Ghash/s is low-variance enough, do I get to watch my first round go on for over a day? Just weird luck, I guess...)

This pool was way ahead of the curve (see geebus post)
again its luck some times as a group we get lucky ... you may have a lucky streak personally
That's mining
 
BTW this pool has NOT had a block that took over a day in the past 10  blocks
so I'm beginning to DOUBT your claims
member
Activity: 112
Merit: 10
I have a new question
This is NOT a complaint
I've been watching http://www.bitcoincharts.com/bitcoin/
seems free confirms/transfers are going up & up  taking longer
especially for small or multiples of one on one transfer
Their has not been a single free transfer since before 13:00 utc today
Shortly before this pool confirmed (hit 120) for its last block http://www.bitcoincharts.com/bitcoin/
showed no unconfirmed  ... funny now it's chart just keeps going up & up again with uncompleted

while others offer a set amount of bitcoin and that is send it to several in one single shot
even including .01 or .02 bitcoin for doing so

Can't this be done here ??
I'd rather see the 50 per pool loosing a few cents per round than wait 6-12 or more hrs to get a payment confirmation
 
Just as a side note slush's pool doesn't seem to suffer from this problem 
I'm no expert on bitcoin or bitcoin pools
I'm just asking WHY ?
full member
Activity: 140
Merit: 101
(Another question: why, right after I say 8.0 Ghash/s is low-variance enough, do I get to watch my first round go on for over a day? Just weird luck, I guess...)
member
Activity: 112
Merit: 10
That explains why I'm getting some stale shares, but not why I'm getting more.

also depends on you refresh rate
this pool mandates a longer refresh  slush don't care
If refresh is too long you'll get more stale on each transition of completed block
full member
Activity: 140
Merit: 101
That explains why I'm getting some stale shares, but not why I'm getting more.
member
Activity: 112
Merit: 10
I seem to be getting stale/invalid shares at about twice the rate on Bitcoin Pool that I get with slush's pool (26/1900 versus 131/17300). This seems like a pretty big difference to be explained by normal variance, especially since BitcoinPool is advertising "no more stale shares". What other explanation is there?

No more stale shares is only for the miner from here
If you use something else like me (puddinpops) you will get stale shares here

excuse me puddinpop  I was told it's rude if your not exactly correct in a persons handle
I think it's rude to correct for minor stuff like exact spelling of aliases but that's only me
full member
Activity: 140
Merit: 101
I seem to be getting stale/invalid shares at about twice the rate on Bitcoin Pool that I get with slush's pool (26/1900 versus 131/17300). This seems like a pretty big difference to be explained by normal variance, especially since BitcoinPool is advertising "no more stale shares". What other explanation is there?
Pages:
Jump to: