Pages:
Author

Topic: *BTC Poolwatch* - no new dev for now (Read 33495 times)

member
Activity: 100
Merit: 10
March 06, 2012, 03:04:10 PM
indeed.

focus on getting better.

we'll see ya when we see ya!

'monkey
hero member
Activity: 868
Merit: 1000
March 05, 2012, 07:08:43 PM
I'm genuinely sorry to hear about the health issues. Take care of the health, everything else can wait.
hero member
Activity: 774
Merit: 500
Lazy Lurker Reads Alot
March 04, 2012, 08:15:52 AM
Poolwatch does no longer work with ozco.in


A PHP Error was encountered
Severity: Notice
Message: Undefined index: roundduration
Filename: models/ozcoin.php
Line Number: 40
A PHP Error was encountered
Severity: Notice
Message: Undefined index: activeworkers
Filename: models/ozcoin.php
Line Number: 43
A PHP Error was encountered
Severity: Notice
Message: Undefined index: hashrate
Filename: models/ozcoin.php
Line Number: 44
A PHP Error was encountered
Severity: Notice
Message: Undefined index: roundduration
Filename: models/ozcoin.php
Line Number: 45
A PHP Error was encountered
Severity: Notice
Message: Undefined index: shares
Filename: models/ozcoin.php
Line Number: 46
A PHP Error was encountered
Severity: Notice
Message: Undefined index: hashrate
Filename: models/ozcoin.php
Line Number: 73
A PHP Error was encountered
Severity: Notice
Message: Undefined index: hashrate
Filename: models/ozcoin.php
Line Number: 74
A PHP Error was encountered
Severity: Notice
Message: Undefined index: confirmed_rewards
Filename: models/ozcoin.php
Line Number: 75
A PHP Error was encountered
Severity: Notice
Message: Undefined index: workers
Filename: models/ozcoin.php
Line Number: 77
A PHP Error was encountered
Severity: Warning
Message: Invalid argument supplied for foreach()
Filename: models/ozcoin.php
Line Number: 78
BTC Poolwatch
donator
Activity: 2058
Merit: 1007
Poor impulse control.
February 23, 2012, 01:12:54 AM
Hi all,

I will be stopping all development and changes for a while (8 months at least).

I've been diagnosed with Acute Myeloid Leukemia, and have just gone through 1st round of chemo therapy.

I'll be going for another round of chemo therapy, and than bone marrow transplant (thank god my sis is a match), and i'll take at least 6 months to recover from the transplant.

At this point, btc-poolwatch.com will have to take a backseat. I'll keep the service running.

I'll be back.

Regards,
Koo


Get well soon, Koo. I hope it all goes well for you.
sr. member
Activity: 444
Merit: 254
February 22, 2012, 09:56:22 PM
Hi all,

I will be stopping all development and changes for a while (8 months at least).

I've been diagnosed with Acute Myeloid Leukemia, and have just gone through 1st round of chemo therapy.

I'll be going for another round of chemo therapy, and than bone marrow transplant (thank god my sis is a match), and i'll take at least 6 months to recover from the transplant.

At this point, btc-poolwatch.com will have to take a backseat. I'll keep the service running.

I'll be back.

Regards,
Koo
sr. member
Activity: 271
Merit: 250
February 21, 2012, 05:30:07 PM
Any plans for poolwatch to add Bitlc.net to the supported sites list. It's now stickied in the Top 10 Pools list.

https://bitcointalksearch.org/topic/down-bitlcnet-p2sh-no-invalid-blocks-custom-payouts-eu-0-fee-lp-10121

https://www.bitlc.net/

member
Activity: 100
Merit: 10
February 14, 2012, 01:51:15 PM
is poolwatch working for eclipsemc at present?

i'm showing data error for most of the user stats.

speed of workers is shown correctly though.

thanks for your time.

'monkey
Eligius has switched servers apparently. The url you are using to get the required data is now wrong.

It is now http://eligius.st/~luke-jr/raw/7/ instead of the old http://eligius.st/~luke-jr/raw/5/.

Rearwheels, can you please fix this?

Updated. Please let me know if your information is still not reflected correctly. Tks.

Looks good now, thanks.  Smiley
sr. member
Activity: 383
Merit: 250
February 09, 2012, 12:24:47 PM
Hey, could you change the pull of eligius stats to use port 8080 instead of the standard 80? Their stats/web/mining are now on the same ip address, and port 80 and 8337 are for mining.

Thanks.  Smiley
sr. member
Activity: 383
Merit: 250
January 17, 2012, 03:57:11 AM
Eligius has switched servers apparently. The url you are using to get the required data is now wrong.

It is now http://eligius.st/~luke-jr/raw/7/ instead of the old http://eligius.st/~luke-jr/raw/5/.

Rearwheels, can you please fix this?

Updated. Please let me know if your information is still not reflected correctly. Tks.

Looks good now, thanks.  Smiley
sr. member
Activity: 444
Merit: 254
January 16, 2012, 11:28:17 PM
Eligius has switched servers apparently. The url you are using to get the required data is now wrong.

It is now http://eligius.st/~luke-jr/raw/7/ instead of the old http://eligius.st/~luke-jr/raw/5/.

Rearwheels, can you please fix this?

Updated. Please let me know if your information is still not reflected correctly. Tks.
sr. member
Activity: 383
Merit: 250
January 16, 2012, 10:48:33 PM
Eligius has switched servers apparently. The url you are using to get the required data is now wrong.

It is now http://eligius.st/~luke-jr/raw/7/ instead of the old http://eligius.st/~luke-jr/raw/5/.

Rearwheels, can you please fix this?
sr. member
Activity: 383
Merit: 250
December 11, 2011, 01:56:10 PM

fixed. sorry about that.

I was overseas and was not monitoring the status of the server so it took a while to get it back up.

Thank you for fixing it.  Smiley
vip
Activity: 980
Merit: 1001
December 11, 2011, 01:35:24 PM
I hope it is for holiday Wink
thanks for taking the time to fix it Smiley
sr. member
Activity: 444
Merit: 254
December 11, 2011, 12:55:46 PM

fixed. sorry about that.

I was overseas and was not monitoring the status of the server so it took a while to get it back up.
vip
Activity: 980
Merit: 1001
December 11, 2011, 06:03:57 AM
Seems to be down again. Has been down for hours...  Sad

At least this time it does not appear to be a DNS problem.
for me too
I miss it - come back soon Cheesy
sr. member
Activity: 383
Merit: 250
December 10, 2011, 12:50:02 AM
Seems to be down again. Has been down for hours...  Sad

At least this time it does not appear to be a DNS problem.
sr. member
Activity: 444
Merit: 254
December 02, 2011, 02:31:32 AM
How come every so often btc-poolwatch goes down? Tonight neither my phone, or my computer can access it. Seems to be a dns issue. Usually I can get one or the other working when one is acting up (phone or computer aka diff isp's and diff dns servers).

The name server is down. I'm talking to the support guys on this. Sorry.

update: server is up.
sr. member
Activity: 383
Merit: 250
December 02, 2011, 02:25:22 AM
How come every so often btc-poolwatch goes down? Tonight neither my phone, or my computer can access it. Seems to be a dns issue. Usually I can get one or the other working when one is acting up (phone or computer aka diff isp's and diff dns servers).
sr. member
Activity: 444
Merit: 254
November 30, 2011, 09:24:30 PM
Hi! Could you please add yourbtc.net to your site?

Done! But please help me test if the workers' status is being shown correctly.

i.e.
Green = worker alive
Red = worker dead

The JSON API does not have explicit info on worker status, so I'm using the "Idle Since" value which should be NULL if worker is active (I guess).



Thanks a lot for adding us!

idle since = null means worker is active exactly.

What does confirmed value mean on btc poolwatch? BTC that have to be payed and not payed yet for whatever reason (payout threeshold for example) or do you mean the sum btc that have been payed out so far? The current value of "Confirmed" is btc that have been payed out, if it should be confirmed payout that has to be payed, please change the value to pending_payout.

Great service btw! I like it!

Thanks for the compliment.

Confirmed means it has got 120confirmations, but the pool has not paid it out to you via the auto payment (due to their batch schedule, or the confirmed amount has not reached the auto payment threshold)

From the JSON, this is what I have now:
confirmed = 'completed_payout'
unconfirmed = 'pending_payout'
estimated = 'estimated_payout'

If completed_payout means a cumulative/historical of all the payouts then my implementation is totally wrong. What I'll do is:
confirmed = 'pending_payout'
unconfirmed = *remove*
estimated = 'estimated_payout'

Regards,
Koo
full member
Activity: 142
Merit: 100
November 30, 2011, 11:27:53 AM
Hi! Could you please add yourbtc.net to your site?

Done! But please help me test if the workers' status is being shown correctly.

i.e.
Green = worker alive
Red = worker dead

The JSON API does not have explicit info on worker status, so I'm using the "Idle Since" value which should be NULL if worker is active (I guess).



Thanks a lot for adding us!

idle since = null means worker is active exactly.

What does confirmed value mean on btc poolwatch? BTC that have to be payed and not payed yet for whatever reason (payout threeshold for example) or do you mean the sum btc that have been payed out so far? The current value of "Confirmed" is btc that have been payed out, if it should be confirmed payout that has to be payed, please change the value to pending_payout.

Great service btw! I like it!
Pages:
Jump to: