Close to buying a 5970 that will take me close to 1Gh/s
Topic: [CLOSED] BTCMine - ZERO fee mining pool (LP, SSL, JSON API, P2SH) - page 40. (Read 171605 times)
April 06, 2011, 07:08:59 PM
Now back to more typical results after a great 7 hours stretch with 4 blocks found...
Close to buying a 5970 that will take me close to 1Gh/s
Close to buying a 5970 that will take me close to 1Gh/s
April 06, 2011, 08:01:49 AM
One more JSON API feature - stats for each miner.
API request:
Sample answer result:
API request:
Code:
http://btcmine.com/api/getminerstats/{YOUR_API_AUTH_TOKEN}/
Sample answer result:
Code:
{"dbitcoin": {"date_connected": "2011-04-06T08:20:16.781903", "solved_shares": 6167, "solved_blocks": 0}}
April 06, 2011, 07:54:32 AM
Sample answer result:
I would recommend using "confirmed_reward" key instead of "confirmed_bounty", so poclbm-gui can use same code for all 3 pools.Code:
{"total_bounty": "0.00000000", "confirmed_bounty": "0.00000000", "solved_blocks": 0, "round_shares": 28, "estimated_bounty": "0.10649149", "solved_shares": 6167, "unconfirmed_bounty": "0.00000000", "hashrate": 20.23, "total_payout": "4.23"}
Compare with examples from slush's and my pools.
Result returned as "confirmed" and "unconfirmed".
And it's already supported by poclbm-gui.
So util Kiv change this, I do not want broke calls to my api.
And there is no "reward" terms in my pool user profiles.
April 06, 2011, 07:39:45 AM
Sample answer result:
I would recommend using "confirmed_reward" key instead of "confirmed_bounty", so poclbm-gui can use same code for all 3 pools.Code:
{"total_bounty": "0.00000000", "confirmed_bounty": "0.00000000", "solved_blocks": 0, "round_shares": 28, "estimated_bounty": "0.10649149", "solved_shares": 6167, "unconfirmed_bounty": "0.00000000", "hashrate": 20.23, "total_payout": "4.23"}
Compare with examples from slush's and my pools.
April 06, 2011, 05:01:40 AM
JSON API extended
Now you able request full stats for your account.
API request:
Sample answer result:
Now you able request full stats for your account.
API request:
Code:
http://btcmine.com/api/getstats/{YOUR_API_AUTH_TOKEN}/
Sample answer result:
Code:
{"total_bounty": "0.00000000", "confirmed_bounty": "0.00000000", "solved_blocks": 0, "round_shares": 28, "estimated_bounty": "0.10649149", "solved_shares": 6167, "unconfirmed_bounty": "0.00000000", "hashrate": 20.23, "total_payout": "4.23"}
April 05, 2011, 10:13:10 AM
And another one found!!! 
Today's block generation rate anomaly high
Just look at http://blockexplorer.com/
April 05, 2011, 09:39:43 AM
And another one found!!!
April 05, 2011, 08:50:55 AM
I was glad we got the block 18 completed before the diff change...
April 05, 2011, 08:30:45 AM
I just can't rationalize the expense right now - especially with the mtgox going lower...
Great morning - 3 blocks found!!
Great morning - 3 blocks found!!
And difficulty going over 80000 soon making it even worse.
Well, probably rising difficulty will push BTC to higher levels
April 05, 2011, 07:58:58 AM
I just can't rationalize the expense right now - especially with the mtgox going lower...
Great morning - 3 blocks found!!
Great morning - 3 blocks found!!
And difficulty going over 80000 soon making it even worse.
April 05, 2011, 06:30:05 AM
I just can't rationalize the expense right now - especially with the mtgox going lower...
Great morning - 3 blocks found!!
Great morning - 3 blocks found!!
April 04, 2011, 11:02:15 PM
Yes, actually at 930m now. Late in the week or early next week it will go even higher.
April 04, 2011, 09:16:46 PM
Sometime next week I will add another 5870 to the pool.
It seems you just did - 800 Mhash now 
April 04, 2011, 08:27:00 PM
Can someone please explain to me what is happening in the screenshot here?
http://awesomescreenshot.com/0ebasxfb9
I would like to understand the charts better.
Thanks
On the pool start (month ago) 50 shares used as bonus for miner who found a block. http://awesomescreenshot.com/0ebasxfb9
I would like to understand the charts better.
Thanks
Right now it's just artifacts, because from 03/22 pool switched to score-base payout model and this shares do not used in payout calculation.
In latest update I removed all old code.
April 04, 2011, 06:26:14 PM
Early on I put in some shares that were on a PPS basis - maybe why it is a difference of 100.
The hash rates in the 500+ range are due to hashing with GPUs - namely AMD GPUs.
The hash rates in the 500+ range are due to hashing with GPUs - namely AMD GPUs.
April 04, 2011, 04:02:45 PM
Can someone please explain to me what is happening in the screenshot here?
http://awesomescreenshot.com/0ebasxfb9
I would like to understand the charts better.
Thanks
http://awesomescreenshot.com/0ebasxfb9
I would like to understand the charts better.
Thanks
April 04, 2011, 06:20:48 AM
Long polling support enabled for all poclbm miner versions from "poclbm/201103.beta1" and higher, but I strongly recommend update poclbm miner to the latest version.
April 04, 2011, 06:19:56 AM
Seems we lost a few folks overnight - were at well over 3Gh/s and now back towards 1.7Gh/s 
Probably this just weekend miners... April 04, 2011, 05:59:37 AM
Seems we lost a few folks overnight - were at well over 3Gh/s and now back towards 1.7Gh/s
April 03, 2011, 08:57:21 PM
2nd block found
Nice, you are tied with me now. Jump to: