bitHopper: Python Pool Hopper Proxy

[c00w]

Triple error?
I get no error. However I did just change how re matching works. check that your triple pool matches the pool in pool.cfg.default.

Namecoins?
Yeah I'm going to add a namecoin difficulty. I'm not sure how we want to deal with the exchange rate issues however...

[1714151932]

1714151932

[1714151932]

1714151932

[1714151932]

1714151932

[1714151932]

1714151932

[kbsbtc]

c00w, whats the point of having both password.py and pool.cfg?

Should I only set up pool.cfg?

[anty]

Another pool:

Code:

[btcmonkey]
name: bitcoinmonkey.com
mine_address: bitcoinmonkey.com:8332
api_address: http://bitcoinmonkey.com
api_method:re
api_key:Shares\s+this\s+round:\s+<strong>\s+(\d+)
#CHANGE THIS
#http://bitcoinmonkey.com/
role: mine
user: x.y
pass: x

Thanks for implementing the regex-change so fast, c00w!

[c00w]

password.py is not needed. If I left it in I'll delete it.

[paraipan]

interesting talk on mtred ... http://www.reddit.com/r/mtred/comments/iu8d3/status_update_on_pool_hopping_protection/c26p2mz

edit: veeery long chat, you've been warned

[muyoso]

Wow, today and yesterday have been AWESOME.  Literally made 5 days worth in 2 days, and there is still 6 hours left to go in day 2.

[kbsbtc]

c00w bithopper wont run with the latest version where you removed config files.

Code:

ImportError: No module named password 

[paraipan]

c00w bithopper wont run with the latest version where you removed config files.

Code:

ImportError: No module named password 

remove this line

Code:

from password import *

at the beginning of "pool.py" file, and make sure you renamed "pool.cfg.default" to "pool.cfg"

[c00w]

Fixed.

[paraipan]

Fixed.

microsoft users would only be dreaming getting bug fixes at that speed

[Tmoney]

Poolhop with 5GH of raw power.

Code:

[poolmunity]
name: poolmunity.com
mine_address: poolmunity.com:8332
api_address:https://poolmunity.com/api.php?server
role:mine
api_method:json
api_key:totalShares
#CHANGE THIS
#http://poolmunity.com/index.php?PHPSESSID=3iglliv6bvs1r8fvve993l5sd2&action=register
user: little.chinese
pass: nuts

[kbsbtc]

Fixed.

THANKS! You are too fast haha. Last question I promise :p Any way to make arsbitcoin the main backup pool? Eliguis gives me a ton of stales.

[c00w]

Poolmunity is added.

kbsbtc:
Either delete eligius or wait. It should select the backup pool with the lowest percentage of rejections.

Look at localhost:8337/stats to see what it believes the rejection rate is.

[ahitman]

interesting talk on mtred ... http://www.reddit.com/r/mtred/comments/iu8d3/status_update_on_pool_hopping_protection/c26p2mz

edit: veeery long chat, you've been warned

Pool hoppers aren't the problem, you can choose to hop or not (or move somewhere where they will not be affected), its everyone else who's hashing, every time they get a new GPU I loose BTC!??!?! Why cant they all just stop hashing an let me have more income.

[organofcorti]

The expected value of a share in a (properly implemented) PPLNS pool is exactly 1.0 (relative to solo or PPS).

Once a share is submitted, the fundamental question of its value is: how many blocks will be found before N more shares have been submitted. This can be modeled as a Poisson process with the expected number of blocks equal to N / difficulty. (If N is the difficulty, you'd expect to find one block. If N is twice the difficulty, you'd expect to find two blocks, and so on.) If (for example), N is one-half the difficulty, you'd expect a share to be paid approximately as follows:

• No payout: ~60.65%
• 1 payout: ~30.33%
• 2 payouts: ~7.58%
• 3 payouts: ~1.26%
• 4 or more payouts: ~0.18%

Regardless of the value of N or the difficulty, the expected value will sum out to 1, however.

To make it relevant for this thread, PPLNS pools should be used only as backups, and definitely not as hopping targets.

You're completely right, PPLNS isn't hoppable. (Although PPLNS is subject to a share-withholding attack)

@Aexoden -  PPLNS definitely won't have a 1.0 expected value, since if the round goes long, you shares are dead

@streblo - first you post a great intro to the topic, then you post more details on PPLNS - thanks btw - now you say you *can't* hop PPLNS? My mind is reeeling, damn you! Why have you changed your mind?

[flower1024]

@Aexoden -  PPLNS definitely won't have a 1.0 expected value, since if the round goes long, you shares are dead

it has an expected value of one in a (very) long term view (if you really hop in/out randomly).

@streblo - first you post a great intro to the topic, then you post more details on PPLNS - thanks btw - now you say you *can't* hop PPLNS? My mind is reeeling, damn you! Why have you changed your mind?

he just misunderstand the system and thought N/2 shares means round_shares.
but n/2 shares means difficulty/2 shares - and with that pplns is just not hoppable. the window is to big

(please correct me if i am wrong)

[Aexoden]

@Aexoden -  PPLNS definitely won't have a 1.0 expected value, since if the round goes long, you shares are dead

Sometimes (60% of the time, with N = difficulty / 2 like mineco.in) you get nothing, but sometimes you get paid 5 times for a single share. It averages out to 1 over time.

As far as PPLNS's ability to be hopped, it doesn't really matter how large or small N is. You can pay the last 1000 shares only, and it still won't be hoppable. (And your expected value will still be 1.0, with a high variance, though not as high as that of solo mining.) PPLNS with N=1 is effectively solo mining (minus pool fees).

[Sukrim]

The other extreme btw. would be PPAS (Pay per all shares) - a pool then would always pay out for each and every share that was ever submitted. I call it "ponzi mining"!

After some time however it might get less and less interesting as a new miner to join in such a pool - already with PPLNS some people are complaining that it takes some time until the true hash rate is valued (= until N shares have been mined while you were hashing at full power - everything before underestimates your hash rate and thusly your contribution).

In the end: Every system that starts at round borders is hoppable to some extent (as far as I read about slush's algorithm, he is hoppable too, but only until ~14% into the round afair.)

Should we btw. add configs for as many pools as possible (even non-hoppable ones or ones that fake/delay stats)? After all some people might still choose to mine there for whatever reason + bitHopper seems to develop into a nice statistical tool + providing automatic failover etc. as well with usefulness beyond pool hopping.


On a different note: Does someone know of some machine learning library for Python? I would need in the end to have it look at some data (collection of IP adresses + timestamps) and (based on previous data) determine into which category it falls...

[joulesbeef]

in the new cfg.. arsbitoin is the only one with ' ' s around the username and pass.. I assume this is a mistake?

[organofcorti]

The other extreme btw. would be PPAS (Pay per all shares) - a pool then would always pay out for each and every share that was ever submitted. I call it "ponzi mining"!

Plus after the first round it wouldn't be hoppable!