bitHopper: Python Pool Hopper Proxy

[Clipse]

thanks, works.

[1714324579]

1714324579

[1714324579]

1714324579

[1714324579]

1714324579

[ed64]

For pools that don't show round shares, but show duration and hashrate, we can estimate the # of shares:

Total_Hash/s = (((Current_Shares - Shares_Before_Delta) * 2^32) / Delta)

Assume we compare from the start of the round, so
Total_Hash/s = ((Current_Shares) * 2^32)) / Round_Duration
Current_Shares = Total_Hash/s * Round_Duration / 2^32

And then apply some factor to during depending on stats delay...

Thoughts?

[Clipse]

For pools that don't show round shares, but show duration and hashrate, we can estimate the # of shares:

Total_Hash/s = (((Current_Shares - Shares_Before_Delta) * 2^32) / Delta)

Assume we compare from the start of the round, so
Total_Hash/s = ((Current_Shares) * 2^32)) / Round_Duration
Current_Shares = Total_Hash/s * Round_Duration / 2^32

And then apply some factor to during depending on stats delay...

Thoughts?

Doable except pools who dont show round shares also dont tell you exactly when round started(sometimes current round is delayed by an hour)

[ryouiki]

For pools that don't show round shares, but show duration and hashrate, we can estimate the # of shares:

Total_Hash/s = (((Current_Shares - Shares_Before_Delta) * 2^32) / Delta)

Assume we compare from the start of the round, so
Total_Hash/s = ((Current_Shares) * 2^32)) / Round_Duration
Current_Shares = Total_Hash/s * Round_Duration / 2^32

And then apply some factor to during depending on stats delay...

Thoughts?

the estimator is already implemented in my bitHopper mod (for btcg), but it don't work good because the estimation is always based on ~1 hour delay.

you can try (just enable btcg) but you will be dissapointed with real earning

[hawks5999]

did bitclockers get completely disabled in the latest test build, ryouiki?

[Clipse]

For pools that don't show round shares, but show duration and hashrate, we can estimate the # of shares:

Total_Hash/s = (((Current_Shares - Shares_Before_Delta) * 2^32) / Delta)

Assume we compare from the start of the round, so
Total_Hash/s = ((Current_Shares) * 2^32)) / Round_Duration
Current_Shares = Total_Hash/s * Round_Duration / 2^32

And then apply some factor to during depending on stats delay...

Thoughts?

the estimator is already implemented in my bitHopper mod (for btcg), but it don't work good because the estimation is always based on ~1 hour delay.

you can try (just enable btcg) but you will be dissapointed with real earning

One thing that confuse me with btcguild atm is the fact that my shares value drop to 0 , I dont think they use normal prop anymore since there is no way shares could become worth 0 within prop, no matter how long a round may last.

Only thing I can think of why the my account display 0 is cause it shows the actual round in progress earnings and is unrelated to any other fake(delayed) stats on the website.

[ryouiki]

did bitclockers get completely disabled in the latest test build, ryouiki?

i'd removed bitclockers on 2e5188.. build (4 hours ago) by mistake
bitclockers is back after f7a2a2.. build (2 hours ago)

edit : oops, test branch is not fixed yet.. i'll fix it asap fixed. thanks

[Clipse]

did bitclockers get completely disabled in the latest test build, ryouiki?

i'd removed bitclockers on 2e5188.. build (4 hours ago) by mistake
bitclockers is back after f7a2a2.. build (2 hours ago)

Bit unrelated to recent discussions but have you figured out what bitcoinpool is doing to their shares yet, or atleast which shares to work from. json shares looks more realistic but it seems they payout based on the website shares/elapsedtime and those stats are totally out of wack.

Also this is prob more directed to c00w/flower/ryo, any idea yet how to capture the counting current round_shares for x8s ?

[zybron]

2) So what have you been doing over the last two days?
Database changes, Stability changes, code reorg, a flat info page, dynamic api polling changes, oh and the difficulty module now will deal with changing difficulty correctly.
So the main code is really solid now.

About the dynamic api polling - if shares remain the same from previous poll to current poll, refresh rate is incremented by 10% of current rate, correct? (If I read the code correctly.) Once refresh rate exceeds 1800 seconds, the pool is disabled. With polling starting at 60 seconds, if a pool's shares became static, it would take 5 1/2 hours before that pool is disabled. I got that from summing the incremental increases from 60 to 1854 over 37 10% steps.

Am I missing something? Is my math wrong? I wouldn't think we would want to wait 5 1/2 hours before changing from a low-ball static round share api poll.

[ryouiki]

i hope u are mining on bitcoins.lc guys ....


@ryouiki i cant disable manually ars ffs

in the latest version (master branch), you can manually remove ars ( 'role':'removefromlist' ) by modifying pool.py

[zybron]

Something is obviously off about the math I used before or how I understand the polling refresh rate increments, cause I just had ozco get disabled because of timeouts, it seems. It was significantly less time than 5 1/2 hours after I last started bitHopper.

However, once ozco was disabled, bitHopper didn't immediately switch to another pool, either. It did eventually switch over to a backup pool, but I would think it should immediately switch, right?

[ryouiki]

Bit unrelated to recent discussions but have you figured out what bitcoinpool is doing to their shares yet, or atleast which shares to work from. json shares looks more realistic but it seems they payout based on the website shares/elapsedtime and those stats are totally out of wack.

Also this is prob more directed to c00w/flower/ryo, any idea yet how to capture the counting current round_shares for x8s ?

http://www.bitcoinpool.com/forum/viewtopic.php?f=1&t=103

they say, they would reduce our earning based on mining time window.
in fact, we can beat this kind of algorithm with forced (scheduled) hopping

as for x8s, they added json yesterday.
recent main branch of my fork may work on x8s, but not tested yet..

Code:

                'x8s':{ 'name': 'btc.x8s.de',
                    'mine_address': 'pit.x8s.de:8337', 'user': x8s_user, 'pass': x8s_pass,
                    'api_address':'http://btc.x8s.de/api/global.json', 'role':'disable'},

Code:

    def x8s_sharesResponse(self, response):
        round_shares = int(json.loads(response)['round_shares'])
        self.UpdateShares('x8s',round_shares)

Code:

            'x8s':self.x8s_sharesResponse,

[c00w]

1) API polling and ozco getting disabled?
There was a bug in an older version which caused things to get disabled too soon.

2) Once the api is disabled the pool isn't?
Um yeah. I need to call a server_update. Forgot about that. My bad.

3)x8s?
I'll finish it.

[joulesbeef]

i hope u are mining on bitcoins.lc guys ....

WHY?!?!


they have been annoying the crap out of me since i discovered them.

are you actually working on new blocks or are they doing that crazy crap with their stats still.. to make us mine there?

[hawks5999]

looks like crazy crap.

[msb8r]

as for x8s, they added json yesterday.
recent main branch of my fork may work on x8s, but not tested yet..

Works very well. Added to pool.py literally 5 minutes before they found the block

[joulesbeef]

yeah screw bitcoin.lc with a chainsaw.. i want nothing to do with them.

They ban hoppers, steal their coins, and screw with the mining stats to make sure we always hop to them.

and when you withdrawn your coin, all you can get out is in increments of 0.01 coins.. the change just annoyingly sits there.

[hawks5999]

Couple of feature requests:

1) Add unhoppable pools such as deepbit or slush as backups - I'd rather failback to deepbit than eligius I think. Seems deepbit has a better payout due to super short (<30 Minute) rounds on average.
2) Add web based control (in ryouiki's fork) to set backup pool - something like a B button to go along with X/O of enable/disable.

Thanks!

[Clipse]

If you followed this thread, you would find the bitcoins.lc stats fix.

Or you can goto ryo github under test branch.

[Clipse]

Couple of feature requests:

1) Add unhoppable pools such as deepbit or slush as backups - I'd rather failback to deepbit than eligius I think. Seems deepbit has a better payout due to super short (<30 Minute) rounds on average.
2) Add web based control (in ryouiki's fork) to set backup pool - something like a B button to go along with X/O of enable/disable.

Thanks!

1. Just use arsbitcoin as backup, dont really need more than one backup.