bitHopper: Python Pool Hopper Proxy

[organofcorti]

New "how to hop" blog post:

How to hop part2: More on score

This week we discover Slush-type score systems fatal flaw, an update on the Slush hop point (previous estimate nearly 50% out), and what 'c' really means, and how to make a shower curtain into a muu-muu!

[1714241292]

1714241292

[1714241292]

1714241292

[1714241292]

1714241292

[1714241292]

1714241292

[1714241292]

1714241292

[TenthReality]

Tossing this one out there for including in index.html, been annoying me for awhile. Sorts your users by username alpha on the stats page.


Also if anyone really cares, I can provide code for worker average % on shares and rejects etc though the mod is a bit more complex.

Code:

					buildTable("#users", users, users,
						{
							"User": { 'data':getUserName } ,
							"Last Seen": { 'data':getUserTime, 'align':'left' },
							"Shares": { 'data':getUserShares, 'align':'center' },
							"Rejects": { 'data':getUserRejects, 'align':'center' },
							"Hashrate": { 'data':getUserHashrate, 'align':'center' }
						},
						function(c,d){
							return c > d;
						},""
					);

[paraipan]

Tossing this one out there for including in index.html, been annoying me for awhile. Sorts your users by username alpha on the stats page.


Also if anyone really cares, I can provide code for worker average % on shares and rejects etc though the mod is a bit more complex.

Code:

..........................

thanks, added to bH, any contrib. counts
you can checkout the project page on git if you really feel like modding some more

@techwtf thanks for the info

[r2edu]

I´m with v0.2.4.6-1 now, works fine, the only thing that i´m missing some db/guild/bclc blocks, or mining it more than once..

What I want to know is how it works better, with or without the --p2pLP? Does p2pLP work in conjunction with the LP, or does it "overwrite" it?

And in the bh.cfg, where it says "# not working yet", means the [altslice] only or the [backdoor] & [lpbot] options too?

btw, sometimes I see BH mining in X pool but some shares goes to others... this is normal?

[c00w]

When it says x is not working it means the options themselves. The underlying code does work we just don't have it checking the options yet.

[r2edu]

Ok, I guess it, my question is if only the options for altslice doesn´t work yet or the options for lpbot neither. (& backdoor)

thx

[TenthReality]

btw, sometimes I see BH mining in X pool but some shares goes to others... this is normal?

If a hop has happened recently, you might be seeing shares from miners still coming in from the previous pool, there is a window of delay there before the miners will all get new work from the newly hopped pool. 

[Keninishna]

guys I just want to let you know I have made a prop pool. The name was inspired by Joules.
http://asspennypool.com  

just add the following to pools.cfg

Code:

[asspenny]
name: asspennypool
mine_address: asspennypool.com:8443
api_address: http://asspennypool.com/api.php?api_key=454b6581f2c034f13c4cec9d27fb9309a5439e9c30e69f00f530015474bb2bd1
api_method: json
api_key: shares
api_key_mhashrate: hashrate
url: http://asspennypool.com

Change to your api key to yours if you want

user.cfg

Code:

[asspenny]
role: mine
user = keninishna.1
pass = x

[phase]

Change to your api key to yours if you want

I always love this remark as if some nut would actually install bithopper to mine for someone else...

[Keninishna]

thats not what I meant but yea feel free to mine for me lol. The api key just returns json info but bithopper only really uses the pool share count and speed.

[organofcorti]

guys I just want to let you know I have made a prop pool. The name was inspired by Joules.
http://asspennypool.com  

just add the following to pools.cfg

Code:

[asspenny]
name: asspennypool
mine_address: asspennypool.com:8443
api_address: http://asspennypool.com/api.php?api_key=454b6581f2c034f13c4cec9d27fb9309a5439e9c30e69f00f530015474bb2bd1
api_method: json
api_key: shares
api_key_mhashrate: hashrate
url: http://asspennypool.com

Change to your api key to yours if you want

user.cfg

Code:

[asspenny]
role: mine
user = keninishna.1
pass = x

That's awesome, K. You'll be seeing me there for the first 43% of the round, for sure! If only you'd started a new cryptocurrency to go with it. I want and clearly need asspennies. I would like to go into my local 7-11 and say "I'll have a diet coke, and I'd like to pay by asspenny".

[Starlightbreaker]

Change to your api key to yours if you want

I always love this remark as if some nut would actually install bithopper to mine for someone else...

it happened to me once, after i set up a new rig, and forgot to transfer user.cfg.

1 hr got lost...er.."donated".

[joulesbeef]

I am mining for ass pennies right now.
but it is no fun solo and you end up wiht stinky finger, so I think i will do it in a pool instead and mine for ass pennies in a group.

[Starlightbreaker]

[14:38:39] Exception in wsgi server loop, restarting wsgi in 60 seconds
%s
Traceback (most recent call last):
  File "bitHopper.py", line 286, in <module>
    main()
  File "bitHopper.py", line 281, in main
    bithopper_instance.log_msg("Exception in wsgi server loop, restarting wsgi in 60 seconds\n%s") % (e)
TypeError: unsupported operand type(s) for %: 'NoneType' and 'error'

well, shit.

it ran for 10 minutes, and boom.

[Transisto]

I'll leave this shit here,   -Love the product.

Code:

Traceback (most recent call last):
  File "C:\Users\M7\Desktop\c00w-bitHopper-a911ec5\eventlet\greenpool.py", line 80, in _spawn_n_impl
    func(*args, **kwargs)
  File "C:\Users\M7\Desktop\c00w-bitHopper-a911ec5\eventlet\wsgi.py", line 514, in process_request
    proto = self.protocol(socket, address, self)
  File "C:\Python27\lib\SocketServer.py", line 641, in __init__
    self.finish()
  File "C:\Users\M7\Desktop\c00w-bitHopper-a911ec5\eventlet\wsgi.py", line 456, in finish
    BaseHTTPServer.BaseHTTPRequestHandler.finish(self)
  File "C:\Python27\lib\SocketServer.py", line 694, in finish
    self.wfile.flush()
  File "C:\Python27\lib\socket.py", line 303, in flush
    self._sock.sendall(view[write_offset:write_offset+buffer_size])
  File "C:\Users\M7\Desktop\c00w-bitHopper-a911ec5\eventlet\greenio.py", line 283, in sendall
    tail = self.send(data, flags)
  File "C:\Users\M7\Desktop\c00w-bitHopper-a911ec5\eventlet\greenio.py", line 269, in send
    total_sent += fd.send(data[total_sent:], flags)
error: [Errno 10054] An existing connection was forcibly closed by the remote host
Traceback (most recent call last):
  File "bitHopper.py", line 285, in <module>
    main()
  File "bitHopper.py", line 280, in main
    bithopper_instance.log_msg("Exception in wsgi server loop, restarting wsgi in 60 seconds\n%s") % (e)
TypeError: unsupported operand type(s) for %: 'NoneType' and 'exceptions.ValueError'

Solution : I have another .bat with pages of run_hopper.bat

[cuqa]

Severe Change from BitcoinPool.com - Read this !

After much consideration and review of how our anti-pool hopping system is looked upon by members of the Bitcoin community, we have chosen to change the way in which it is working.

In the Past:
If a user participated in less than 50% of the round, their shares would be reduced by 10%, unless a donation was set, in which case, no penalty was applied.

This allowed for our users with legitimate disconnects, or reasons for being unable to mine during long rounds to avoid being hit with a penalty.

Some people seem to belive that this is a negative aspect of the anti-hopping system due to the easily cheatable nature of the system and the fact that pool hoppers are still given a large incentive to exploit our pool.

From Now on:
If a user participates in less than 50% of the round, their shares will be reduced by 50%, regardless of donation. 50% of the penalty fee will be directed toward the donations account and will be applied to server costs and future monthly contests. The other 50% of the penalty will be removed from the total shares for the round, which will in-hand cause the value of all remaining shares in the round to increase.

Example -

100,000 shares are in the round.

User A has 5000 shares and is NOT a hopper. Their estimated earnings before penalties are applied is 2.5 BTC.

User B has 5000 shares and IS A hopper. Their estimated earnings before penalties are applied is 2.5 BTC.

Once penalties are applied, User B's shares are reduced to 2500 where 1250 has been credited to donations and 1250 has been removed from the round. After the penalty is applied, User B's unconfirmed earnings are 1.265 BTC and User A's unconfirmed earnings are 2.5316 BTC.

At this time, any donation currently set on your account will remain in place. Donations will be processed prior to any penalties. As a reminder, donations are entirely voluntary and are not required to use this pool.

We will use this new method of calculating penalties for a one week trial period, at which time we will decide whether or not it is effectively deterring pool hopping and effectively rewarding loyal members of the pool.

Regards,

BitcoinPool Staff

[iopq]

holy WHAT

I'm in an endless loop of getworks being submitted to slush
I'm going to update and see if it fixes it

[iopq]

updated, still getting getwork loops
also, had to disable plugins because windows can't find plugins/*.*

[Sukrim]

@Bitcoinpool.com stuff: How is "participating" measured? After all, submitting a share every once in a while after 43.5% could be enough.

[deepDown]

holy WHAT

I'm in an endless loop of getworks being submitted to slush
I'm going to update and see if it fixes it

I have exactly the same problem after all updates applied.
And it is not exclusive to any pool  - I have been stuck in getwork loops on deepbit, eligius and bitcoins.lc so far.

How can I revert back to an earlier version of bithopper using git?

thanks