a form of proportional scoring for calculating a fair payout of your shares.
That pretty much kills it. Sounds like a score method to me |
|
|
|
quick question.. has anyone sent a single share to deepbit prop yet.. using the new c00w?
I have had it running with --startLP and mine_deepbit on both deepbit and btcguild since yesterday, and have yet to submit a single share. I don't think it is working |
|
|
|
I've tried to read through the thread but I haven't found the answer. Current balance is what you've earned after 100 confirmations? Estimated earnings is the current block. How do you find out what's waiting for confirmations? I guess it just shows up in 8-10 hours? If you could show unconfirmed earnings that would be awesome. If it's already displayed can someone tell me where.  |
|
|
|
based on the error message, I did this fix, and I am watching to see if it really was that simple: In lp.py: def set_owner(self,server):
if self.lastBlock != None:
self.blocks[self.lastBlock]["_owner"] = server
self.bitHopper.log_msg('Setting Block Owner :' + str(self.lastBlock))
I wrapped self.lastBlock in the last line in a str(). I'm not going to stand behind this fix, because I'm not even sure what lastBlock is for yet, but we will see |
|
|
|
yeah it appears to be in long polling.. c00w has some info on it a few pages back when he thought he might have fixed it.
I'm looking into it right now. What I have figured out is the error is in Long polling, but there is no lp receive. The reset was discovered on the status refresh. Still not certain why it is happening, I haven't looked much into the LP part of this code yet |
|
|
|
|
I managed to get the error with a log going. After a while (maybe when a block is found?) I get a LOT of these:
2011-08-08 11:50:54-0500 [HTTP11ClientProtocol,client] Error in pool api for triple
2011-08-08 11:50:54-0500 [HTTP11ClientProtocol,client] "[Failure instance: Traceback: <type 'exceptions.TypeError'>: cannot concatenate 'str' and 'long' objects\n/usr/lib/python2.7/dist-packages/twisted/internet/defer.py:1076:gotResult\n/usr/lib/python2.7/dist-packages/twisted/internet/defer.py:1063:_inlineCallbacks\n/usr/lib/python2.7/dist-packages/twisted/internet/defer.py:361:callback\n/usr/lib/python2.7/dist-packages/twisted/internet/defer.py:455:_startRunCallbacks\n--- <exception caught here> ---\n/usr/lib/python2.7/dist-packages/twisted/internet/defer.py:542:_runCallbacks\n/opt/bitHopper/pool.py:161:selectsharesResponse\n/opt/bitHopper/pool.py:124:UpdateShares\n/opt/bitHopper/lp.py:24:set_owner\n]"
Edit: yup when a new block is found
|
|
|
|
[18:04:49] Error in pool api for digbtc
...
[18:05:50] Error in pool api for digbtc
[code][18:22:58] Error in pool api for slush
[18:22:59] Error in pool api for slush
[18:22:59] Error in pool api for slush
[18:22:59] Error in pool api for slush
[18:22:59] Error in pool api for slush
[18:22:59] Error in pool api for arsbitcoin
[18:22:59] Error in pool api for arsbitcoin
[18:22:59] Error in pool api for arsbitcoin
[18:22:59] Error in pool api for arsbitcoin
[18:22:59] Error in pool api for arsbitcoin
[18:22:59] Error in pool api for arsbitcoin
[18:22:59] Error in pool api for arsbitcoin
[18:22:59] Error in pool api for arsbitcoin
[18:22:59] Error in pool api for arsbitcoin
[18:22:59] Error in pool api for arsbitcoin
[18:22:59] Error in pool api for arsbitcoin
[18:22:59] Error in pool api for slush
[18:22:59] Error in pool api for slush
[18:22:59] Error in pool api for slush
[18:22:59] Error in pool api for slush
[18:22:59] Error in pool api for arsbitcoin
[18:22:59] Error in pool api for arsbitcoin
[18:23:00] Error in pool api for arsbitcoin
[18:23:00] Error in pool api for arsbitcoin
I get the same thing after an hour or so with this latest version, haven't run it in debug yet. My stats page shows everything as lagged out, and nothing mining[/code] |
|
|
|
I would encourage you to help out ozco.in with their very long round. Currently 9,959,101 shares.
Just hop on them for half a day would really make a difference!
I put them on mine_charity yesterday, they have been good to us, and deserve a little push |
|
|
|
|
c00w, this software is really coming along. I haven't even been using it 2 weeks, and I am shocked at how much it has evolved in this short of a time. Good job
|
|
|
|
Well i guess if they were my "friends" they would be hopping over and helping us finish this very long block. But as most are only interested in maximising thier profits I dont expext that (or dontaions) from hoppers (always open to being surprised though).  I'll be your friend |
|
|
|
Just to clarify the Miner= lines: you need one for each GPU in the system. Since you don't have 1 system with 28 GPUs, you won't have 28 Miner= lines in one config.
I have 3 systems with 3, 3 and 4 GPUs. One cfg per pool per system.
Oh, I had misunderstood, I thought this was centralized |
|
|
|
|
Does it have to be one account per GPU? I haven't looked too much into this yet, but I have 28 GPUs, and I don't want to create a worker for each on each pool. Any way to make it per system?
|
|
|
|
|
It is important to remember that you would not have found those 3 blocks if you were mining solo. The header you were hashing for the pool would have been different than the header you would have hashed for yourself. Thus, you can't make the comparison. If you had mined solo, you might have found 10 blocks, you might have found 0 blocks. Likely, you would have found 1 block.
|
|
|
|
|
Ok, now slicing is picking up bitcoins.lc which is over 50% when there are 2 pools under 30%. Is there something I am not understanding about slicing? For the time being, I'm moving back to the old default scheduler
|
|
|
|
Hm.
bithopper refuses to hop from digbtc, even after i disabled digbtc.
He fixed that issue last night, did you get latest? |
|
|
|
Can someone post the info for digbit? I can't even find their URL
[digbtc] name: DigBTC.net mine_address: digbtc.net:8332 api_address:http://digbtc.net/ api_method:re api_key:Round Shares: <b>([ 0-9]+)</b> url: http://www.digbtc.net/main.phpThank you sir |
|
|
|
|
Can someone post the info for digbit? I can't even find their URL
|
|
|
|
|
Holy contrast batman! Refreshing was a bad idea. Sorry to whoever updated the colors, but I have a fever, and the only prescription is more contrast.
|
|
|
|
Ok, so BTCPool24 has a total of 18 GH and is at 41%, and MtRed has 400 GH and is at 23%. Why would slicer choose BTCPool24?
Slicers main flaw atm is that it doesnt recognize poolhashrate, that is something dynamicpenalty will introduce once it gets added I assume. If it isn't poolhashrate, what is making it select the 41% pool over the 23%? |
|
|
|
|
Ok, so BTCPool24 has a total of 18 GH and is at 41%, and MtRed has 400 GH and is at 23%. Why would slicer choose BTCPool24?
|
|
|
|
|
Show Posts
