bitHopper: Python Pool Hopper Proxy

[Clipse]

Im thinking they have some "sophisticated" antihopping strategy, new block found and pool hashrate doesnt remain as high as it used to.

What im thinking some hoppers figured out how to get around the dropped connections, whereas most hoppers havnt.

I will have to look into this.

nofee is showing like 25% stales for me this round.

Its wasting gpu cycles, it keeps dropping and doesnt accept all shares. Something is stuffed there or they have figured out how to detect hoppers better than other sites.

I notice in the listed stats that there is people staying connected, so I doubt its just their server being crap unless those users also keep reconnecting and their hashrates just reflect a time delayed update on stats.

[1714220681]

1714220681

[1714220681]

1714220681

[1714220681]

1714220681

[1714220681]

1714220681

[flower1024]

btw nofee blocks are easily detectable through mail (i always get the block found mail max 1min after they found a block).

what i think is curious about nofee:
with bithopper i get much more "pool downs" as with my miner. thats the reason i made an api for bithopper and switch my miner directly (there are still some pool downs and i still have a higher reject rate than usual (noofee is 5% atm for this round) - but its better as with the proxy). maybe they are trying to detect us and close the connection on a random basis - but i am not sure.

[Clipse]

btw nofee blocks are easily detectable through mail (i always get the block found mail max 1min after they found a block).

what i think is curious about nofee:
with bithopper i get much more "pool downs" as with my miner. thats the reason i made an api for bithopper and switch my miner directly (there are still some pool downs and i still have a higher reject rate than usual (noofee is 5% atm for this round) - but its better as with the proxy). maybe they are trying to detect us and close the connection on a random basis - but i am not sure.

Its definitely related to bithopper in some way and not just a user-agent thing detecting bithopper then dropping the IP.

Ive tested with miner directly and get ~2% stales which is sorta within norm, and no dropped miners.

Peh. :/

[organofcorti]

btw nofee blocks are easily detectable through mail (i always get the block found mail max 1min after they found a block).

what i think is curious about nofee:
with bithopper i get much more "pool downs" as with my miner. thats the reason i made an api for bithopper and switch my miner directly (there are still some pool downs and i still have a higher reject rate than usual (noofee is 5% atm for this round) - but its better as with the proxy). maybe they are trying to detect us and close the connection on a random basis - but i am not sure.

Ah, it was you. I'd forgotten who did that. Is slush on your bitHopper api?

[anty]

1. NoFeeMining - yep me too. But unless they have a sophisticated antihopping strategy, I don't think they're handling the heat well.

2. Anyone spot the problem with this? I can't figure why it's not working. Something dumb I've missed probably.

Code:

api_address:http://api.bitcoin.cz/stats
api_method:re
api_key:<tr><td><strong>Shares contributed in current round:</strong></td><td>(\d+)</td></tr>

I'd welcome any help

Regex should be correct, must be something else.

K thx anty

Found the problem: Your URL seems to redirect or something. Here's the correct code. I don't know if slush hopping is correctly implemented, though?

Code:

[slush]
name: bitcoin.cz
mine_address: http://api2.bitcoin.cz:8332
role: mine_slush
api_address: http://mining.bitcoin.cz/stats/
api_method: re
api_key:Shares\s+contributed\sin\s+current\s+round:</strong></td><td>(\d+)
#CHANGE THIS
#http://www.bitcoin.cz
user: username
pass: password

[flower1024]

btw nofee blocks are easily detectable through mail (i always get the block found mail max 1min after they found a block).

what i think is curious about nofee:
with bithopper i get much more "pool downs" as with my miner. thats the reason i made an api for bithopper and switch my miner directly (there are still some pool downs and i still have a higher reject rate than usual (noofee is 5% atm for this round) - but its better as with the proxy). maybe they are trying to detect us and close the connection on a random basis - but i am not sure.

Ah, it was you. I'd forgotten who did that. Is slush on your bitHopper api?

not atm.
but on sunday i'll release my pool watch project which will print round-stats for as many pools as possible (even slush-a-like). it will be published as json, webservice and xml (which will all contain the same data) - and a field which tells the payout system they are using.

i won't make it advise any pool - thats your job. but there will be a site provide pool graphs and such things.

my hopper integration is atm very poor. its just a hopper restarter (with an 10secs delay before stopping the old one).

[organofcorti]

OK, while I can't get a good feed for Slush I trialled mineco.in on mine_slush. Unfortunately Mine_slush is just doing backup duty It should be doing this: a normal hop at start of round then leaving when it hits diff*0.1

tl;dr leave mine_slush for the moment.

edit: just checked source looks like it should start at 0 hop at 0.25

[organofcorti]

Awesome work anty many thx. I'll be ready for when mine_slush is sorted.

[flower1024]

its a bad idea to use slush as a backup as many of your shares will go to hell.

i tried an approach of joining slush @300% and stay until they found a block. but it's just not working well - so i disabled it

[organofcorti]

I'm looking forward to seeing your pool watch service!

its a bad idea to use slush as a backup as many of your shares will go to hell.

i tried an approach of joining slush @300% and stay until they found a block. but it's just not working well - so i disabled it

if you look at streblo's explanation, he stated that any scoring pool and any PPLNS pool would be hoppable. You just have to leave earlier. His graphs were pretty, not sure about the math and he hasn't been back since to explain except to leave a very mysterious agreement that I didn't follow.

On multipool and multclone I got good slush scores - around 110% - so I know it can be done (or I was very lucky). Either way I want to give it a try. The role:mine_slush is supposed to hop on and leave after diff*0.1

[flower1024]

with pplns he is wrong.
he made the (wrong) assumption that the N in pplns means just N to round start. but with pplns some shares get double paid - which makes hopping useless.

score could be - i haven't dive into that yet

[organofcorti]

Bitcoin just crashed for me:

Code:

[11:41:23] Updating Difficulty
[11:41:24] 1690906.2047244
[11:41:24] Updating NameCoin Difficulty
[11:41:25] 94037.96
[11:41:25] Checking Database
[11:41:25] DB Verson: 0.1
Traceback (most recent call last):
  File "bitHopper.py", line 220, in <module>
    bithopper_global = BitHopper()
  File "bitHopper.py", line 39, in __init__
    self.db = database.Database(self)
  File "/home/user/bitHopper/database.py", line 21, in __init__
    self.check_database()
  File "/home/user/bitHopper/database.py", line 50, in check_database
    self.curs.execute(sql)
sqlite3.OperationalError: unknown database bitcoin

Any ideas before I delete the db?

edit: Solved. Never call your pool database name [bitcoin.cz]

[EskimoBob]

here are some more errors I get

Code:

[15:18:47] bitclockers: 1,529,462
[15:18:56] RPC request [69e7e000] submitted to mtred
[15:19:00] RPC request [] submitted to mtred
[Failure instance: Traceback (failure with no frames): <class 'twisted.internet.error.TimeoutError'>: User timeout caused connection failure.
]
[15:19:06] LP triggered from server mtred
[15:19:07] triple: 4,932,232
[15:19:13] RPC request [59a31000] submitted to mtred
[15:19:14] RPC request [3e23d000] submitted to mtred
[15:19:16] Error in pool api for nofeemining
[15:19:18] RPC request [7e170000] submitted to mtred
[15:19:22] RPC request [0589c000] submitted to mtred
[15:19:23] RPC request [] submitted to mtred
[15:19:24] RPC request [] submitted to mtred
[15:19:30] RPC request [a17f3000] submitted to mtred
[15:19:34] triple: 4,932,555
Error in json decoding, Server probably down

[15:19:46] RPC request [] submitted to mtred
[15:19:47] nofeemining: 198,400
[15:19:48] bitclockers: 1,531,414
[15:19:48] RPC request [] submitted to mtred
[15:19:53] RPC request [ca6f5000] submitted to mtred
[15:20:02] triple: 4,932,918
Caught, jsonrpc_call insides
User timeout caused connection failure.

[organofcorti]

here are some more errors I get

Code:

[15:18:47] bitclockers: 1,529,462
[15:18:56] RPC request [69e7e000] submitted to mtred
[15:19:00] RPC request [] submitted to mtred
[Failure instance: Traceback (failure with no frames): <class 'twisted.internet.error.TimeoutError'>: User timeout caused connection failure.
]
[15:19:06] LP triggered from server mtred
[15:19:07] triple: 4,932,232
[15:19:13] RPC request [59a31000] submitted to mtred
[15:19:14] RPC request [3e23d000] submitted to mtred
[15:19:16] Error in pool api for nofeemining
[15:19:18] RPC request [7e170000] submitted to mtred
[15:19:22] RPC request [0589c000] submitted to mtred
[15:19:23] RPC request [] submitted to mtred
[15:19:24] RPC request [] submitted to mtred
[15:19:30] RPC request [a17f3000] submitted to mtred
[15:19:34] triple: 4,932,555
Error in json decoding, Server probably down

[15:19:46] RPC request [] submitted to mtred
[15:19:47] nofeemining: 198,400
[15:19:48] bitclockers: 1,531,414
[15:19:48] RPC request [] submitted to mtred
[15:19:53] RPC request [ca6f5000] submitted to mtred
[15:20:02] triple: 4,932,918
Caught, jsonrpc_call insides
User timeout caused connection failure.

Triplemining was down while back. I'm getting normal results atm.

[EskimoBob]

btw nofee blocks are easily detectable through mail (i always get the block found mail max 1min after they found a block).

what i think is curious about nofee:
with bithopper i get much more "pool downs" as with my miner. thats the reason i made an api for bithopper and switch my miner directly (there are still some pool downs and i still have a higher reject rate than usual (noofee is 5% atm for this round) - but its better as with the proxy). maybe they are trying to detect us and close the connection on a random basis - but i am not sure.

Its definitely related to bithopper in some way and not just a user-agent thing detecting bithopper then dropping the IP.

Ive tested with miner directly and get ~2% stales which is sorta within norm, and no dropped miners.

Peh. :/

And the result is this? http://imageshack.us/photo/my-images/38/snapshot28nodeedrop.jpg

[Clipse]

Looking at their network swing rates, thats probably issues with the pool rather than just hoppers.

The network speed goes up and down as if the actual server is crashing constantly.

I think even regular users are just quitting cause of these issues.

EDIT: Mining with miner only having same issues as mining with bithopper. Network resets constantly.

[farfiman]

pool is crap, simply it can't handle 80-100Ghash/s ...

to keep the hoppers away...

[organofcorti]

pool is crap, simply it can't handle 80-100Ghash/s ...

to keep the hoppers away...

They have a 'crap pool' to keep hoppers away? I thought that would keep everyone away 

So how's the infrastructure change coming - can we expect consistent connection soon?

[joulesbeef]

could you also add my pool-stats graph

Pict looks cool.. did you change the addy to reach the webpage?... I've tried all I can think of to reach it.


c00w.. i get this when I start up yours.. probably something I did.. do you have an idea?

[09:50:43] Database Setup

Code:

Unhandled error in Deferred:
Unhandled Error
Traceback (most recent call last):
  File "D:\Users\joulesbeef\Desktop\c00w-bitHopper-july24th\bitHopper.py", line
425, in <module>
    main()
  File "D:\Users\joulesbeef\Desktop\c00w-bitHopper-july24th\bitHopper.py", line
420, in main
    stats_call.start(117*4)
  File "D:\Python27\lib\site-packages\twisted\internet\task.py", line 163, in st
art
    self()
  File "D:\Python27\lib\site-packages\twisted\internet\task.py", line 194, in __
call__
    d = defer.maybeDeferred(self.f, *self.a, **self.kw)
--- <exception caught here> ---
  File "D:\Python27\lib\site-packages\twisted\internet\defer.py", line 133, in m
aybeDeferred
    result = f(*args, **kw)
  File "D:\Users\joulesbeef\Desktop\c00w-bitHopper-july24th\stats.py", line 106,
 in update_api_stats
    d = work.get(self.bitHopper.json_agent,info['user_api_address'])
exceptions.NameError: global name 'work' is not defined

[flower1024]

i'll add the stats graph this evening to c00w's version (still unsure if its gonna be a complete client-side approach [means graph data is only collected when browser is open] or if bitHopper itself send its data [means more traffic, more load])

(yes i changed the location, sorry. link ist http://<ip>/info