bitHopper: Python Pool Hopper Proxy

[muyoso]

thanks I thought I looked everywhere. They didnt hide it or anything huh? Surprised it wasnt down a broken flight of stairs in a darken room with a sign on the door saying beware of leopard.

What I am wondering is why it switched off of mtred and went back to ozcoin before hitting the magic 43% or whatever number.

Try as I might, I cant seem to figure out the logic in the hopper but I havent tried to look too much at the code.

No kidding right?  I was freaking out a little when I saw:
Current Balance   0.00000000 BTC
Total Earned   0.00000000 BTC

and no payment in my wallet.  They really need to add an unconfirmed balance.

As for the logic of bithopper, I have no clue either.  I gotta say it works though.  Ive only been mining with it for like 36 hours but the first 24 has made me a believer.

[msb8r]

thanks I thought I looked everywhere. They didnt hide it or anything huh? Surprised it wasnt down a broken flight of stairs in a darken room with a sign on the door saying beware of leopard.

What I am wondering is why it switched off of mtred and went back to ozcoin before hitting the magic 43% or whatever number.

Try as I might, I cant seem to figure out the logic in the hopper but I havent tried to look too much at the code.

No kidding right?  I was freaking out a little when I saw:
Current Balance   0.00000000 BTC
Total Earned   0.00000000 BTC

and no payment in my wallet.  They really need to add an unconfirmed balance.

As for the logic of bithopper, I have no clue either.  I gotta say it works though.  Ive only been mining with it for like 36 hours but the first 24 has made me a believer.

As far as I can tell looking through the code - and someone please correct me, if I'm wrong - it uses the pool with fewest shares. The exception to this is if the pool with fewest shares has 10% or less fewer shares than the pool currently being mined for.

e.g. if you're currently mining for Mt Red and Mt Red has 200K shares, then any pool with less than 180K shares will be hopped to.

[OCedHrt]

thanks I thought I looked everywhere. They didnt hide it or anything huh? Surprised it wasnt down a broken flight of stairs in a darken room with a sign on the door saying beware of leopard.

What I am wondering is why it switched off of mtred and went back to ozcoin before hitting the magic 43% or whatever number.

Try as I might, I cant seem to figure out the logic in the hopper but I havent tried to look too much at the code.

No kidding right?  I was freaking out a little when I saw:
Current Balance   0.00000000 BTC
Total Earned   0.00000000 BTC

and no payment in my wallet.  They really need to add an unconfirmed balance.

As for the logic of bithopper, I have no clue either.  I gotta say it works though.  Ive only been mining with it for like 36 hours but the first 24 has made me a believer.

For ozcoin your earnings are here: https://ozco.in/blocks.php

[OCedHrt]

a solution to btc guild and deepbit delayed stats ?
1) run a bitcoin client for each of this pools on different ports
2) config that bitcoin clients to allow the connection ONLY to this pools
3) record the time for the new block found whit each bitcoin clients, check this time against normal "new block" event, the time on the bitcoin clients should be lower
4) suppose that if the time is lower the pool got block and change the hopper on that pool


if the hopper mine at pool X and the bitcoin client is connected only on pool Z when pool Z get new block the "announcement" goes from the pool Z to bitcoin client and normal scenario from the pool Z to pool X then to the hopper

I don't think that would work. BTCG will still report new block for anyone who finds it, not necessarily just BTCG.

[flower1024]

it'll only work if you bitcoind client listens to MANY other clients.

when it sees the message from btcguild first it's very likely btcguilds block.

shouldn't be that difficult to code either.

[muyoso]

As far as I can tell looking through the code - and someone please correct me, if I'm wrong - it uses the pool with fewest shares. The exception to this is if the pool with fewest shares has 10% or less fewer shares than the pool currently being mined for.

e.g. if you're currently mining for Mt Red and Mt Red has 200K shares, then any pool with less than 180K shares will be hopped to.

OK, so in the situation where ozcoin is at 250k shares and then mtred finds a block, bithopper jumps to mtred until mtred has 10% more shares than ozcoin?  Is that the most efficient?  I am sure people smarter and more well versed in hopping than I know better, but wouldn't it be smart to have bithopper stay with mtred until a certain % of difficulty was reached?  Or is the benefit of mining at a much smaller much slower pool greater than staying with mtred?

[flower1024]

earlier sharesare worth more than later shares.
you always (prop) want to go the pool which founds a block.

it gets a little tricky if two pools found a block very close. i made a patch for that - have to discussed with c00w (just see git if interested)

[joulesbeef]

Ive only been mining with it for like 36 hours but the first 24 has made me a believer.

LOL without a doubt me too. Sometimes I get ahead of myself with the desire to "tweak" just a little more. But I have to say I am very happy with the results of the hopper so far. I am doing far better than I was mining pools solo.

[Clipse]

earlier sharesare worth more than later shares.
you always (prop) want to go the pool which founds a block.

it gets a little tricky if two pools found a block very close. i made a patch for that - have to discussed with c00w (just see git if interested)

I will wait till c00w update bithopper if neccesary.

So what you suggest is, no matter the speed of a pool, if one pool moves above X shares in current difficulty, it is allways better to switch to another pool that has lower than X shares in current difficulty, even if X shares from first pool is less than the predefined hop percentage ie. 40% ?

[flower1024]

earlier sharesare worth more than later shares.
you always (prop) want to go the pool which founds a block.

it gets a little tricky if two pools found a block very close. i made a patch for that - have to discussed with c00w (just see git if interested)

I will wait till c00w update bithopper if neccesary.

So what you suggest is, no matter the speed of a pool, if one pool moves above X shares in current difficulty, it is allways better to switch to another pool that has lower than X shares in current difficulty, even if X shares from first pool is less than the predefined hop percentage ie. 40% ?

this current version i published to discuss it only works with pools which has an more-or-less equal hashrate.

i don't say you should ever not switch to a pool with the most less shares.

but if there are two pools which found a block the same second you don't know which of them is better (means: who will solve this block first).

so best thing would be to divide your shares 50/50 (again: same hashrate atm only, could be improved)

i would prefer to switch pool whenever a share is found on a random basis (see my other version, not on git but in this forum - just for a look; it isnt really usable), but that just do only work if you have just one miner attached. with two or more you'll fuck up some getworks and get way more stales.

i am using my "time-slice" method since ten hours now (tweaked it a little more) and it seems good.

eg: the last mtred -> ozcoin switch. for you it switched immediatly. for me my shares has been splitted

[Clipse]

Well it would be nice to get a seperate bithopper version using your method, so I can run both evenly split among my available mhash and see over 24-48hrs if there is a different in earnings.

[flower1024]

here you go:

www.k1024.de/dev.7z

it has a small web interface:

http://ip:mineport/current/index

i emptied password.py completely

EDIT: please check pool.py. sometimes i change keys there too.... to lazy to look at it right now

[Clipse]

Thanks will check it out and report back.

Appreciate it

[muyoso]

Damnit, bitcoins.lc. . .   They routinely let their site misreport the length of rounds and then after the fact correct them.  They had a "14 hour" round that suddenly turned into a 12 hour round, a 13 minute round and an hour and 45 minute round.  Bithopper didn't jump in on the 13 minute or hour and 45 minute round because of the misreporting.  They do this almost everytime there is a very long round.  Wonder if its an attempt to stop hopping or if there is an issue with the pool itself.  People complain about this regularly in their thread in the Pools section.

[flower1024]

bitcoins.lc is known to HATE hoppers.
and the owner is a really unkind person

i wont ever mine their again (even when hopping [hopefully someday] becomes unprofitable)

i don't work for douches!

[joulesbeef]

yeah not a fan of bitcoin.lc.. how he handled the whole multiclone affair left a foul taste in my mouth. He eventually gave them back their bitcoin but doesnt change how he handled it in the first place.

I'd rather just deal with one less place to hop even if our list is rather short.


cool flower, I will check out your hopper as well. and let you know.

[flower1024]

cool flower, I will check out your hopper as well. and let you know.

its not mine... its c00w. just for clarification
i am just playing with the maths

and it is not perfect right now!

planned:
 - better handling of backup bools
 - regard pools hashrate

but next i'll try to patch bitcoin itself to detect btcguild block - just because i think its possible

[muyoso]

yeah not a fan of bitcoin.lc.. how he handled the whole multiclone affair left a foul taste in my mouth. He eventually gave them back their bitcoin but doesnt change how he handled it in the first place.

I'd rather just deal with one less place to hop even if our list is rather short.


cool flower, I will check out your hopper as well. and let you know.

Yea, the way he handled that was ridiculous.  I think his issue was the thousands of connections going to one account, but trying to keep the money is plain theft.

The only reason I would consider to continue mining there is because there simply isn't that many pools to hop to right now, and I feel the larger the list of hoppable pools the more I will make.

[flower1024]

you take the risk of getting banned.
its VERY easy for pool operators to caught a hopper if he stays for more- let's say - 5 rounds.

and make a new account every 3 blocks: you need much hashrate to afford that, as there is a minimum payout

edit: btw the time-slice-method makes it more difficult for pool operators will detect you. as your hashrate will slowly go down

[joulesbeef]

I meant your modification of his hopper.
I do like how you cleaned out the cobwebs

but I am having problems making it work, cause I am soo noob

Code:

D:\Users\joulesbeef\Desktop\dev\dev\c00w-bitHopper-50ab019>bithopper.py
Unhandled error in Deferred:
Unhandled Error
Traceback (most recent call last):
  File "D:\Users\joulesbeef\Desktop\dev\dev\c00w-bitHopper-50ab019\bitHopper.py"
, line 391, in <module>
    main()
  File "D:\Users\joulesbeef\Desktop\dev\dev\c00w-bitHopper-50ab019\bitHopper.py"
, line 383, in main
    slice_call.start(2)
  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\dev\dev\c00w-bitHopper-50ab019\bitHopper.py"
, line 48, in slice_server
    select_best_server()
  File "D:\Users\joulesbeef\Desktop\dev\dev\c00w-bitHopper-50ab019\bitHopper.py"
, line 128, in select_best_server
    log_msg("reslice 1: " + str(info["slice"]) + " " + str(info["shares"]) + " "
 + str(info['slicedShares']))
exceptions.KeyError: 'slice'
[15:14:39] bitHopper Calculating MHash
[15:14:39] MHash0
[15:14:41] nofee:   5773049 3.69107
[15:14:41] Error in pool api for nofee
"[Failure instance: Traceback: <type 'exceptions.KeyError'>: 'slice'\nD:\\Python
27\\lib\\site-packages\\twisted\\internet\\defer.py:1076:gotResult\nD:\\Python27
\\lib\\site-packages\\twisted\\internet\\defer.py:1063:_inlineCallbacks\nD:\\Pyt
hon27\\lib\\site-packages\\twisted\\internet\\defer.py:361:callback\nD:\\Python2
7\\lib\\site-packages\\twisted\\internet\\defer.py:455:_startRunCallbacks\n--- <
exception caught here> ---\nD:\\Python27\\lib\\site-packages\\twisted\\internet\
\defer.py:542:_runCallbacks\nD:\\Users\\joulesbeef\\Desktop\\dev\\dev\\c00w-bitH
opper-50ab019\\pool.py:132:selectsharesResponse\nD:\\Users\\joulesbeef\\Desktop\
\dev\\dev\\c00w-bitHopper-50ab019\\bitHopper.py:195:server_update\nD:\\Users\\jo
ulesbeef\\Desktop\\dev\\dev\\c00w-bitHopper-50ab019\\bitHopper.py:128:select_bes
t_server\n]"
[15:14:42] mtred:             1172395 0.74959
[15:14:42] Error in pool api for mtred

using python 2.7 if that makes any difference.

I copied over my password file from the cows unmodified version, erasing what i didnt need

any ideas?