bitHopper: Python Pool Hopper Proxy

[r2edu]

Getting error in pool api for Polmine and rfc and also bitcoinpool but that is probably because I tried to figure out by myself the right pool.cfg settings for bcpool to mine_deepbit.  Anyone have these working? 

Try polmine with "mine_deepbit", it´s working very good for me. RFC close down, disable it. And bitcoinpool by default at "mine_deepbit" work ok too..

[1714323989]

1714323989

[joulesbeef]

LOL.  Tried for the last half hour to figure out regex scraping so that I could get bitcoinpool to work by scraping from the website instead of the JSON, but its now obvious to me that I have no idea what I am doing.  Anyone got it working from the website stats?  Trying to do re_rate or re_rateduration on it.

are you on bleeding edge?
the newest one works. Though it operates on a new system than we used to have due to the problems we had with them.

I also mine polmine with just mine.. not sure if that is right but it seems to work fine.

[muyoso]

LOL.  Tried for the last half hour to figure out regex scraping so that I could get bitcoinpool to work by scraping from the website instead of the JSON, but its now obvious to me that I have no idea what I am doing.  Anyone got it working from the website stats?  Trying to do re_rate or re_rateduration on it.

are you on bleeding edge?
the newest one works. Though it operates on a new system than we used to have due to the problems we had with them.

I also mine polmine with just mine.. not sure if that is right but it seems to work fine.

I am on 1.7.2.  I tried mine_deepbit with bitcoinpool and it jumped almost immediately to it even though they are 18 hours into a block.  I looked at the pools.cfg and saw it was using the JSON for round shares and pool speed, all of which is currently being faked.  The round shares, duration and speed are WAY off in the JSON.  That is when I went on the adventure of trying to get BH to regex the stats from the website, which didn't work too well.

NVM, found that 1.7.2 isn't the "bleeding edge" and found the fix in the absolute latest.  Thanks.

[r2edu]

BTW, Slush with "mine_slush" with penalty at 0.5 FTW !!

[digger]

now http://digbtc.net

offer pool api

http://digbtc.net/papi.php

just tell every one know!

[Houseonfire]

A few questions:
What does it mean by penalty?

And, can someone help me add in a complete addition of all the gained BTC on the top of the page up by by speed? And also the current system time. For example:

Code:

bcpool @71MHash | 1.000 BTC Earned  |  10:00PM

And by earned, i dont mean cashed out. I mean the total of what is earned so far.

[joulesbeef]

the penalty on the stats page is a number that you multiply shares by.

so a pool with 20% shares and a penalty of 2, will be seen by the hopper as having 40% shares and will stop when the pool hits 21.5 on default threshold. cause it will see 21.5 as 43%

it is just a way to mine some pools more than others.



C00w small error

Code:

global name reject not defined.

[organofcorti]

I assume you are giving each pool a table of random block find times (randomly generate a high-precision round percentile 0% to 100%, turn that percentile into number of individual hashes required using correct math, turn that into times using hashrate), and then are simulating the switching and share percentages earned.

No. I am using Meni's formula.

You can't use anything that will provide a uniform random distribution. It has to be at least a binomially distributed random, and at best a time-distributed fractional poisson distribution.

I'm using the built in poisson distribution randomiser built into R with some jiggery pokery to make it a poisson time-distributed random(really share based) instead of the standard poisson distribution http://stat.ethz.ch/R-manual/R-patched/library/stats/html/Poisson.html. Ryouiki has a bespoke poisson randomiser built on mersenne twister as a random seeder.

So there's a bunch of examples to get you going!

[bb]

You can't use anything that will provide a uniform random distribution. It has to be at least a binomially distributed random, and at best a time-distributed fractional poisson distribution.

I'm using the built in poisson distribution randomiser built into R with some jiggery pokery to make it a poisson time-distributed random(really share based) instead of the standard poisson distribution http://stat.ethz.ch/R-manual/R-patched/library/stats/html/Poisson.html. Ryouiki has a bespoke poisson randomiser built on mersenne twister as a random seeder.

The described method does not result in uniformly distributed pool shares.

Also in case you missed it, Meni replied to you here.

[ryouiki]

My simulator uses randomly generated round shares that are generated with simple algorithm mimics block finding procedure. (poisson process) To get statistically meaningful result, I used high quallity Mersenne Twister as a base pseudo-random generator.

pseudo code:

Code:

var sparseness = RAND_MAX / BTC_DIFFICULTY;
var roundShare = 0
while (true)
{
    ++roundShare;
    if (MTrand() < sparseness) break;
}
return roundShare;

table of generated 120k round shares : http://cl.ly/8wg3

[cirz8]

BTW, Slush with "mine_slush" with penalty at 0.5 FTW !!

I have found 0.5 to work quite nice as well

[bb]

Btw, I got the latest c00w last night and have been mining with it since. Still no share at deepbit:



?

[bb]

My simulator uses randomly generated round shares that are generated with simple algorithm mimics block finding procedure. (poisson process) To get statistically meaningful result, I used high quallity Mersenne Twister as a base pseudo-random generator.

pseudo code:

Code:

var sparseness = RAND_MAX / BTC_DIFFICULTY;
var roundShare = 0
while (true)
{
    ++roundShare;
    if (MTrand() < sparseness) break;
}
return roundShare;

table of generated 120k round shares : http://cl.ly/8wg3

I plotted your sample:



and a sample I produced:



Please excuse the missing labels. x-axis is number of shares (in percentage of difficulty), y-axis is number of occurances (summing over windows of 10000 shares).

The results differ slightly, most significantly at around 0.

[Starlightbreaker]

back to good ol' bithopper, after done having fun with ixcoin.

look at the new changes.
niiiiiiice.

[organofcorti]

You can't use anything that will provide a uniform random distribution. It has to be at least a binomially distributed random, and at best a time-distributed fractional poisson distribution.

I'm using the built in poisson distribution randomiser built into R with some jiggery pokery to make it a poisson time-distributed random(really share based) instead of the standard poisson distribution http://stat.ethz.ch/R-manual/R-patched/library/stats/html/Poisson.html. Ryouiki has a bespoke poisson randomiser built on mersenne twister as a random seeder.

The described method does not result in uniformly distributed pool shares.

Also in case you missed it, Meni replied to you here.

I was responding to deepceleron, not you bb. My response to meni: https://bitcointalk.org/index.php?topic=36018.msg457483#msg457483

Edit: and now thanks to Meni I've sped up the simulator hugely by generating random numbers directly by using geomtrically distributed random number generator (rgeom) instead of using rpois and then a 'find block' loop.

[flower1024]

the owner of abcpool just let us know not to use them atm:
https://bitcointalk.org/index.php?topic=33586.msg457579#msg457579

there are problems with counting invalids (you get your payment though), but for them bh behaves a little dos-sing.

we don't know why yet; but we'll see. after that: it seems to be a really good pps pool as a backup

[cirz8]

I think I have read about the "DoS-like appearance" in some other thread before, can't remember where though.
But I don't think I have seen invalid shares being part of it, aggressive pulling/getwork I think it was when I read about it before.

The big question, is the massive amount of invalid shares only occurring on the ABCpool?

[joulesbeef]

back to good ol' bithopper, after done having fun with ixcoin.

need to add IOcoin support.. next.

[hawks5999]

the owner of abcpool just let us know not to use them atm:
https://bitcointalk.org/index.php?topic=33586.msg457579#msg457579

there are problems with counting invalids (you get your payment though), but for them bh behaves a little dos-sing.

we don't know why yet; but we'll see. after that: it seems to be a really good pps pool as a backup

Backup? We don't need no steenking backup!

 

[flower1024]

I think I have read about the "DoS-like appearance" in some other thread before, can't remember where though.
But I don't think I have seen invalid shares being part of it, aggressive pulling/getwork I think it was when I read about it before.

The big question, is the massive amount of invalid shares only occurring on the ABCpool?

i saw two differences with abcpool to other pools:

abcpool is lagging out very fast (only with bh)
and my hashrate has gone crazy (but seems feasible if they are counting invalids for their hashrate calculation)

i do think it is about bh's delag call; but i dont know how yet. it seems to be identic to a normal getwork. the delag calls are send every ten seconds; and thats really not much.