Topic: bitHopper: Python Pool Hopper Proxy - page 72. (Read 355813 times)

I fixed the default slicer to hop properly when pools go over the difficulty threshold and all schedulers should now ignore api_lag for backup pools.

[20:17:22] Error in pool api for bmunion
[20:17:22] Error in pool api for triple
[20:17:23] Error in pool api for ozco
[20:17:23] Error in pool api for mtred
[20:17:23] Error in pool api for nofeemining
[20:17:23] Error in pool api for mtred
[20:17:23] Error in pool api for mtred
[20:17:23] Error in pool api for bitp
[20:17:23] RPC request [69f06000] submitted to bitminersunion.org
[20:17:23] Error in pool api for bcpool
[20:17:23] Error in pool api for bcpool
[20:17:23] Error in pool api for slush
[20:17:24] Error in pool api for polmine
[20:17:24] Error in pool api for polmine
[20:17:24] Error in pool api for mtred
[20:17:24] Error in pool api for nofeemining
[20:17:24] Error in pool api for digbtc
[20:17:24] RPC request [getwork] submitted to BitHasher.com
[20:17:24] Error in pool api for digbtc
[20:17:24] RPC request [getwork] submitted to BitHasher.com
[20:17:25] Error in pool api for mtred
[20:17:25] RPC request [08edb000] submitted to bitminersunion.org
[20:17:25] btcmonkey: 3248969
[20:17:25] Error in pool api for btcmonkey
[20:17:25] Error in pool api for bithasher
[20:17:25] Error in pool api for bithasher
[20:17:25] Error in pool api for btcmonkey
[20:17:26] RPC request [getwork] submitted to BitHasher.com
[20:17:26] Error in pool api for btcpool24
[20:17:26] Error in pool api for btcpool24
[20:17:26] RPC request [getwork] submitted to BitHasher.com
[20:17:26] Error in pool api for btcworld
[20:17:26] Error in pool api for rfc
[20:17:26] Error in pool api for btcworld
[20:17:26] RPC request [getwork] submitted to BitHasher.com
[20:17:26] Error in pool api for digbtc
[20:17:27] Error in pool api for triple
[20:17:28] slush: 631954
[20:17:28] Error in pool api for slush
[20:17:28] Error in pool api for eligius
[20:17:28] Error in pool api for bcpool
[20:17:28] RPC request [getwork] submitted to BitHasher.com
[20:17:28] Error in pool api for slush
[20:17:28] Error in pool api for bcpool
[20:17:28] Error in pool api for polmine
[20:17:28] RPC request [getwork] submitted to BitHasher.com
[20:17:28] Error in pool api for polmine

Only way the price of BTC can move up is if you all stop mining!

. or, Amazon and or e-bay start accepting BTC.

I think, I am done with this experiment.  In need to get my 2.something  BTC more and then, I stop.
At 370 MHas/s it is absolutely pointless. I did hope, that hopping helps me a bit but I am not sure anymore.

Using the up-to-date c00w version, it mines slush even well above 10% with the default scheduler.  Slush is set to mine_slush, penalty=1

just tradebot with a weird algo

um yeah wtf

My stats page doesnt work properly even after deleting stats.db and I havent assigned any coin value

why is always Efficiency showing 0,00%?

sorry, I do not understand whats going on there except that someone is buying/selling much coins...
any hints?

Same problem as the last 10 version.  I have to use a very old version if I want the program to jump to my backup Deepbit, all the new versions only do 10 or so shares, and then jump to the lowest % pool, even if it is above the threshold.

Please tell me why this won't go to Deepbit when it should?

If I restart the program, it realized no good pools are worth being on, and it goes to my only backup, deepbit.  After 10 or so shares, it goes to a pool, even though it shouldn't.

I am stuck using a version from 2 weeks ago if I want it to work properly.
..........................................

[deepbit]
name: DeepBit
mine_address: pit.deepbit.net:8332
api_address: https://deepbit.net/
api_method: re
api_key: rate:([ 0-9]+)Gh/s<
api_strip: ' '
url: https://deepbit.net/account

um yeah wtf

Finally figured out the problem with the webpage stats, so anyone with stats db impermanence listen up:

Don't let any pool efficiency become Infinity. If you did delete stats.db and make sure you don't add any reward until you have shares for the pool. I was still having this problem on the latest build until I guessed why.

You may be asking: well why did you assign coinage to shares you dont have yet? Well I was actually adding negative reward - the amount the pool said I was owed but hadn't had confirmed yet. That way when it appeared in my bitcoin client I'd just add the amount with the owing - from prior to the db starting - and it would already be taken care of.

@c00w - any way we can have Infinity efficiency in the stats.db without making stats.db impermanent?

Anyone care to comment on this

I see Bitcoins @ 8 Dollar... That worries me...

If you go look around inside bitHopper.py towards the around the bottom quarter or so, you can locate command options.

Ugh this is frustrating, nowhere in the instructions does it even say I have to install python..