[CLOSED] MaxBTC.com Pool - Closed Indefinitely Aug 3rd 2013

[zvs]

epic

too bad i was wasting time with p2pool =/

[1714103063]

1714103063

[1714103063]

1714103063

[1714103063]

1714103063

[P_Shep]

sweet

[martychubbs]

Wheeeee!  Wow, it must be the Irish in me, cause we are lucky! 

[P_Shep]

If this round becomes invalid, I'm going to cry.

[martychubbs]

If this round becomes invalid, I'm going to cry.

I am already on the ledge!

Taking the 3.5% insurance helps!  Not too late is it?

What is the longest for this pool?

[zvs]

If this round becomes invalid, I'm going to cry.

I am already on the ledge!

Taking the 3.5% insurance helps!  Not too late is it?

What is the longest for this pool?

6.4 mil and 6.2 mil are the two longest in terms of shares

besides block #1, this is the longest one, though (ed: in amt of time)

so much for my 0.000034xx since may  

[zvs]

i'll put magical worker 4F back to work, 2 bitcoin solves in 400k shares!

[martychubbs]

i'll put magical worker 4F back to work, 2 bitcoin solves in 400k shares!

come on 4F, make it rain!!!!

[zvs]

i'll put magical worker 4F back to work, 2 bitcoin solves in 400k shares!

come on 4F, make it rain!!!!

4F needs another couple weeks to get to 200k, then it should have it solved =p

[zvs]

i'll put magical worker 4F back to work, 2 bitcoin solves in 400k shares!

come on 4F, make it rain!!!!

4F needs another couple weeks to get to 200k, then it should have it solved =p

all but one of my non-busted gpus (a growing collection) are now in use.  using top secret methods to solve block, im rdy for bonus

[LightRider]

No rewards in the last few days. What's up?

[martychubbs]

What's up?

Not our luck!

[tarrant_01]

Thanks for finally pressing the solve button. Now just put it on turbo.

[P_Shep]

100 hours! Yay!

[P_Shep]

Less of the invalid blocks pleeeeeese!

[JWU42]

Bad stretch of luck along with invalids had me worried.  Luck has improved of late and getting closer to 100% PPS...

[jamesg]

Hi maxbtc,

It seems your rollntime implementation is incorrect.

<Ukto> hmm, no rollntime on maxbtc
<gigavps> they have rollntime
<Ukto> well
<Ukto> i dont know
<Ukto> i get  X-Roll-NTime: Y
<Ukto> for a header "sometimes"\
<Ukto> which is not correct
<Ukto> should be seconds
<Ukto> not "Y"
<gigavps> are you sure "Y" is not in the protocol
<Ukto> this is from bitminter: X-Roll-NTime: expire=150
<Ukto> ozco: X-Roll-NTime: expire=120
<gigavps> i'll let them know
<gigavps> do you mind if i quote this convo?
<Ukto> https://en.bitcoin.it/wiki/Getwork#rollntime
<Ukto> no known specification of "Y"
<Ukto> sure

So the correct implementation is an http header like so:

Code:

X-Roll-NTime: expire=120

Hope this helps.

Best,
gigavps

[zvs]

Bad stretch of luck along with invalids had me worried.  Luck has improved of late and getting closer to 100% PPS...

looks like above avg luck since 8/21

and rather freakish since 9/20!

[btcx]

Hi maxbtc,

It seems your rollntime implementation is incorrect.

Thanks for the heads up.  We're a bit busy right now but have fixed the headers and are adding a few more options.  We'll roll it out once they're tested and ready.

[streetuff]

pool is down!