bitHopper: Python Pool Hopper Proxy

[phorensic]

OK bitHoppers, I have created a simple JSON api that will feed your script without destroying our server.  Please use https://bitcoinmonkey.com/json/api.php .  Also, please note that we have full SSL support.  The config in bitHopper was using the non-SSL port of our Apache.

I will slowly start unblocking IP's so those of you using bitHopper will regain access.

[1714278099]

1714278099

[1714278099]

1714278099

[hawks5999]

Probably beats the alternative of never finding a block. BitHoppers may fly away with some profits, but at least you have profits. Otherwise you just sit and burn electricity and wear down your components.

Funny thing is you could probably go back 6 months and find complaints about pools.
And go back further and find complaints about GPU miners.

Next up: complaints about p2pool destroying all other pools
Then: complaints about FPGA miners destroying all our investments in GPUs.

It's called evolution.

Let's face it, by the time the 21st million block is found there will be 3 international mining conglomerates left fighting over that last satoshi. Probably they will be Visa-Mart (from the 2024 merger of MasterVisa (2019) and WalCosTarget-Mart (2020) representing consumer financial), Chase-Exxon (from the 2027 merger of Chase-Sachs (2016 when JPMChase takes over every other Wall Street bank) and Exxon-BP (2014) representing institutional energy and finance)  and GMBY (which will be a global GSE a la FNMA - and yes it will be pronounced "Gumby"). They will have a combined 97% of the hashing power and the other 3% will be the small gamblers hoping to compete with their personal 2 Exahash/s Intel Quantum Home PCs. There will be probably 10,000 or so of these miners. Probably none of us will be them...

[enmaku]

It's called evolution.

Indeed, and it works MUCH faster in the IT world than in nature. The people complaining are almost always the ones who can't keep up.

[paraipan]

@hawks5999 nice... my imagination just got loose

just managed to conf. bitcoinmonkey (thanks phorensic)

Code:

[btcmonkey]
name: bitcoinmonkey.com
mine_address: bitcoinmonkey.com:8332
api_address: https://bitcoinmonkey.com/json/api.php
api_method:json
api_key:shares_this_round
role: info
#CHANGE THIS
#http://bitcoinmonkey.com/
user: x
pass: x

(i get an api error though, shit)

[ed64]

• Merged flower's time slicing mod
• Added startup options to enable slicing (off by default) and set slicing size
• Also showed slice (seconds) left in web stats as well
• Refactored backup server into it's own function
• Added additional parameters to log_msg and log_dbg to prefix log messages

Available in my tree for now: https://github.com/echiu64/bitHopper

Feel free to pull back into your respective trees.

Only tested it briefly... more changes to come.

Tested it for a few hours now, made a few more changes pushed to git (penalty wasn't being factored in the initial commit). Looks like it works. Threw in btcg for fun, time slicing between 3 pools now...

[ewibit]

is this worth to be a
backup pool?

since today it is possible PPS
and 1.95 BTC Bonus for block finding
---------------------------

[btcpool24]
name:btcpool24
mine_address:min.btcpool24.com:8338
role:backup
#CHANGE THIS
#http://www.btcpool24.com/register.php
user = 'x.1'
pass = 'x'
---------------------------
http://forum.bitcoin.org/index.php?topic=31633.msg397847#msg397847

[anty]

@hawks5999 nice... my imagination just got loose

just managed to conf. bitcoinmonkey (thanks phorensic)

Code:

[btcmonkey]
name: bitcoinmonkey.com
mine_address: bitcoinmonkey.com:8332
api_address: https://bitcoinmonkey.com/json/api.php
api_method:json
api_key:shares_this_round
role: info
#CHANGE THIS
#http://bitcoinmonkey.com/
user: x
pass: x

(i get an api error though, shit)

You get an error because there's html in the json response (view source).
Here's a working one:

Code:

[btcmonkey]
name: bitcoinmonkey.com
mine_address: bitcoinmonkey.com:8332
api_address: https://bitcoinmonkey.com/json/api.php
api_method:re
api_key:"shares_this_round":"(\d+)
role: mine
#CHANGE THIS
#http://bitcoinmonkey.com/
user: username
pass: password

[murfshake]

user = 'x.1'
pass = 'x'
---------------------------
http://forum.bitcoin.org/index.php?topic=31633.msg397847#msg397847

Why is your formatting with the "=" and a space " " where as every other one is with a

"user:x"
"pass:x"

??

Also btcguild has the wrong formatting it looks like.

[paraipan]

thanks anty, working now

[phorensic]

@hawks5999 nice... my imagination just got loose

just managed to conf. bitcoinmonkey (thanks phorensic)

Code:

[btcmonkey]
name: bitcoinmonkey.com
mine_address: bitcoinmonkey.com:8332
api_address: https://bitcoinmonkey.com/json/api.php
api_method:json
api_key:shares_this_round
role: info
#CHANGE THIS
#http://bitcoinmonkey.com/
user: x
pass: x

(i get an api error though, shit)

You get an error because there's html in the json response (view source).
Here's a working one:

Code:

[btcmonkey]
name: bitcoinmonkey.com
mine_address: bitcoinmonkey.com:8332
api_address: https://bitcoinmonkey.com/json/api.php
api_method:re
api_key:"shares_this_round":"(\d+)
role: mine
#CHANGE THIS
#http://bitcoinmonkey.com/
user: username
pass: password

I tried to include no HTML besides a <pre> tag that other pools are using in their JSON output.  What is the most compatible way to output my JSON?

[paraipan]

........
it's working fine that way, you should consider memcaching and updating every minute if you want to have efficient stats and low cpu on server

edit: now working with json, count with us in the next run

[anty]

I tried to include no HTML besides a <pre> tag that other pools are using in their JSON output.  What is the most compatible way to output my JSON?

No HTML at all. Just the JSON text.

Edit: now it's valid JSON, here's the correct code for bitHopper:

Code:

[btcmonkey]
name: bitcoinmonkey.com
mine_address: bitcoinmonkey.com:8332
api_address: https://bitcoinmonkey.com/json/api.php
api_method:json
api_key:shares_this_round
role: mine
#CHANGE THIS
#http://bitcoinmonkey.com/
user: username
pass: password

Thanks phorensic!

[phorensic]

Alright, I removed the <pre> tag.

[macboy80]

Alright, I removed the <pre> tag.

Phorensic. You are a scholar and a gentleman. Thanks for your cooperation.

[Moussekateer]

Can someone explain the behaviour of this proxy please. Why is mine currently mining on my backup pool when there are no errors on any of the 4 pools that are configured? Is it because they have passed a certain number of total shares?

[phorensic]

Alright, I removed the <pre> tag.

Phorensic. You are a scholar and a gentleman. Thanks for your cooperation.

Thanks.  This was actually a good little stress test for my code and database.  Identified a big bottleneck in two queries that I fixed today.  Just about done unbanning IP's that are still using the old HTML method on our site.  Use the new config if you are reading this!

[anty]

Can someone explain the behaviour of this proxy please. Why is mine currently mining on my backup pool when there are no errors on any of the 4 pools that are configured? Is it because they have passed a certain number of total shares?

Yes, at the current difficulty bitHopper mines until a sharecount of 1690906*0.4 = 676362.4 is reached and then switches to a backup pool.

[paraipan]

yep that should be normal behavior, while waiting to see the script hopping I would be reading some pages of this thread to understand how it works, increase efficiency

[Moussekateer]

Can someone explain the behaviour of this proxy please. Why is mine currently mining on my backup pool when there are no errors on any of the 4 pools that are configured? Is it because they have passed a certain number of total shares?

Yes, at the current difficulty bitHopper mines until a sharecount of 1690906*0.4 = 676362.4 is reached and then switches to a backup pool.

Ah gotcha. Thanks very much.

[ewibit]

Why is your formatting with the "=" and a space " " where as every other one is with a

"user:x"
"pass:x"

??

sorry was a mistake...