deepbut hopping works fine here, last version 1d3aa44, smallest number of active pools for testing purposes (mine and info) atm I'm running 4 on mine (triple, ozco, mt.red, deepb) and slush on info. rfc and btcmonkey spit a lot of LP from what I've seen
edit: DefaultScheduler here with --startLP only
Topic: bitHopper: Python Pool Hopper Proxy - page 44. (Read 355813 times)
mine_deepbit should have worked. What scheduler are you using?
I just fixed the LP system, I shouldn't have tried to be lazy and use an int as a semaphore.
It should work with all of the schedulers.
It should work with all of the schedulers.
I noticed it reset shares just fine with deepbit, but wouldn't switch to it while there were "better" targets around. I forced it to deepbit by switching role from mine_deepbit to mine after it's shares were reset. Possible to automate this change?
I just fixed the LP system, I shouldn't have tried to be lazy and use an int as a semaphore.
It should work with all of the schedulers.
It should work with all of the schedulers.
nice avatar @joules means you got super hopping powers from c00w... 
does --startLP work with olddefault?
From a previous post a few pages back c00w said it should work with them all.
Um, I just redid the whole deepbit system again to produce estimated share counts. So every scheduler now works!
Am I right about this c00w?
does --startLP work with olddefault?
Yeah but see how it doesn't make another lp call? Thats a problem. And why it works for at most 1 round for eveybody. I think I fixed it, but I'm still testing.
I use bitHopper.py --startLP. It works:
Code:
[20:31:25] RPC request [708e7000] submitted to ArsBitcoin.com
[20:31:26] RPC request [getwork] submitted to ArsBitcoin.com
[20:31:39] RPC request [getwork] submitted to ArsBitcoin.com
[20:31:39] received lp from: deepbit
[20:31:39] New Block: 9ed812147aff42bca7ef15c53da75da0329f721c3d8ba8c20000064500000000
[20:31:39] Block Owner deepbit
[20:31:40] LP triggered serving miner
[20:31:40] RPC request [getwork] submitted to ArsBitcoin.com
[20:31:40] received lp from: btcworld
[20:31:40] RPC request [getwork] submitted to ArsBitcoin.com
[20:31:41] received lp from: digbtc
[20:31:41] received lp from: btcserv
[20:31:42] received lp from: bclc
[20:31:43] RPC request [getwork] submitted to ArsBitcoin.com
[20:31:43] received lp from: arsbitcoin
[20:31:43] received lp from: bcpool
[20:31:45] received lp from: triple
[20:31:48] Server change to deepbit
[20:31:52] RPC request [getwork] submitted to DeepBit
[20:31:54] received lp from: ozco
[20:31:55] RPC request [d2a39000] submitted to ArsBitcoin.com
[20:32:04] RPC request [getwork] submitted to DeepBit
BTCmine was added only for 'info' back when we thought cow was going to use a different strategy.
I still only have the one single share to deepbit and I got that on the last version of the hopper.
so what is different between us no deepbit shares and those with deepbit shares?
so kenesia and gomad.. tell me what pools you are mining besides deepbut
and what version of c00w do you use
edit btcpool chaned to btcmine.. stupid too many btc pools
I still only have the one single share to deepbit and I got that on the last version of the hopper.
so what is different between us no deepbit shares and those with deepbit shares?
so kenesia and gomad.. tell me what pools you are mining besides deepbut
and what version of c00w do you use
edit btcpool chaned to btcmine.. stupid too many btc pools
Yeah been running deepbit for 9 hours, no shares yet. 
but I have to say this slicing is working real well even though payout on larger pools is less.
but I have to say this slicing is working real well even though payout on larger pools is less. totally agree about time slicing, and when you think I was supporting the OldScheduler, not too much though because we're learning every day here
btw @c00w dunno what happened with the shares estimation for deepbit but yesterday was working fine and with last update just stopped for unknown reason
edit: it works like magic now
Yeah been running deepbit for 9 hours, no shares yet. but I have to say this slicing is working real well even though payout on larger pools is less.
but I have to say this slicing is working real well even though payout on larger pools is less.
There is a bug with deepbit and LP in general where once it gets called once it isn't called again. I'm debugging.
@gtrrkicw
No need to set disabled pools to info. It works with all schedulers. It looks like you make the most money off of olddefaultscheduler
@gtrrkicw
No need to set disabled pools to info. It works with all schedulers. It looks like you make the most money off of olddefaultscheduler
Just so I fully understand mining deepbit here, I have to set it to mine_deepbit, set my disabled pools to info and then run it with --startLP? What if I'm using the OldDefaultScheduler will it work? Or do I have to use the current default scheduler?
We're missing a lot of great short blocks on Deepbit, bithopper only picked up the one where "Your Shares" are shown, the others were ignored.
http://i.imgur.com/xEN51.png
http://i.imgur.com/xEN51.png
What scheduler are you using?
Trying to mine Deepbit and using slicing at the same time might not work so well unless the slices are very very small. It doesn't take them long to get past the default 43.5% mark. If you are in the middle of a slice when Deepbit starts a new round, it could be over before you get a chance to hop.
Also, Deepbit support doesn't seem to be working perfectly yet, so it might just be an issue with BH. Like others, I found that I only hopped to Deepbit once after updating bitHopper and running it for 10 hours or so.
btcpool24 found a new block. Got my payout fro the one before. Happy Hippedi Hopp
Surprise, hit payout two times for 0.0005 extra.. harhar
Surprise, hit payout two times for 0.0005 extra.. harhar
We're missing a lot of great short blocks on Deepbit, bithopper only picked up the one where "Your Shares" are shown, the others were ignored.
Anyone else seeing deepbit timing out after a little bit?
Woke up this morning and it's red, and goes red pretty quickly after a couple of shares are sent.
Woke up this morning and it's red, and goes red pretty quickly after a couple of shares are sent.
Code:
2011-08-09 08:37:21-0700 [HTTPChannel,12,A.B.C.D] RPC request [] submitted to DeepBit
2011-08-09 08:37:25-0700 [-] Unhandled Error
Traceback (most recent call last):
Failure: twisted.internet.error.TCPTimedOutError: TCP connection timed out: 110: Connection timed out.
2011-08-09 08:37:25-0700 [-] 'Caught, jsonrpc_call insides'
2011-08-09 08:37:25-0700 [-] Unhandled Error
Traceback (most recent call last):
Failure: exceptions.Exception: Response is none
afaik its cause pident is down.
Why is btcmine in the new config, they seem to be using a score based system: http://btcmine.com/page/faq/#rewardcalc (@paraipanakos, joulesbeef)?
correction en route, I don't think originally was score based, one missed detail
Anyone else seeing deepbit timing out after a little bit?
Woke up this morning and it's red, and goes red pretty quickly after a couple of shares are sent.
Woke up this morning and it's red, and goes red pretty quickly after a couple of shares are sent.
Code:
2011-08-09 08:37:21-0700 [HTTPChannel,12,A.B.C.D] RPC request [] submitted to DeepBit
2011-08-09 08:37:25-0700 [-] Unhandled Error
Traceback (most recent call last):
Failure: twisted.internet.error.TCPTimedOutError: TCP connection timed out: 110: Connection timed out.
2011-08-09 08:37:25-0700 [-] 'Caught, jsonrpc_call insides'
2011-08-09 08:37:25-0700 [-] Unhandled Error
Traceback (most recent call last):
Failure: exceptions.Exception: Response is none
Jump to: