bitHopper: Python Pool Hopper Proxy

[macboy80]

could you also add my pool-stats graph

Pict looks cool.. did you change the addy to reach the webpage?... I've tried all I can think of to reach it.


c00w.. i get this when I start up yours.. probably something I did.. do you have an idea?

[09:50:43] Database Setup

Code:

Unhandled error in Deferred:
Unhandled Error
Traceback (most recent call last):
  File "D:\Users\joulesbeef\Desktop\c00w-bitHopper-july24th\bitHopper.py", line
425, in <module>
    main()
  File "D:\Users\joulesbeef\Desktop\c00w-bitHopper-july24th\bitHopper.py", line
420, in main
    stats_call.start(117*4)
  File "D:\Python27\lib\site-packages\twisted\internet\task.py", line 163, in st
art
    self()
  File "D:\Python27\lib\site-packages\twisted\internet\task.py", line 194, in __
call__
    d = defer.maybeDeferred(self.f, *self.a, **self.kw)
--- <exception caught here> ---
  File "D:\Python27\lib\site-packages\twisted\internet\defer.py", line 133, in m
aybeDeferred
    result = f(*args, **kw)
  File "D:\Users\joulesbeef\Desktop\c00w-bitHopper-july24th\stats.py", line 106,
 in update_api_stats
    d = work.get(self.bitHopper.json_agent,info['user_api_address'])
exceptions.NameError: global name 'work' is not defined

@ JB: That is the same error I got yesterday. Issue #45 on GitHub. I believe it happens when you enable/mine bitclockers. c00w had me fixed in the latest commit.

[1714216299]

1714216299

[1714216299]

1714216299

[1714216299]

1714216299

[1714216299]

1714216299

[1714216299]

1714216299

[hawks5999]

is mtred IP banning now? or is it just me?

[Tmoney]

is mtred IP banning now? or is it just me?

I'm also banned.

[macboy80]

is mtred IP banning now? or is it just me?

I'm still mining away...

EDIT: MtRed timed out for me now.

[c00w]

1)beef errors wtih stats.py?
Yeah turning on bitclockers screwed things up. Its fixed in the latest version.

2) mine_slush?
I thik I accidentally made it jump at 1.6 instead of .1. Oops. I'll fix that.

[EskimoBob]

Code:

[22:02:43] Error in pool api for nofeemining
[22:02:45] Error in pool api for bitclockers

In localhost:8337/stats, both those jump to 10000000000 and obviously another pool is selected

When shares can be submitted just fine but the pools web page is not answering in a split second, scripts starts a completely unnecessary hop from a perfectly working pool.  Can you calm this down a bit?

Cheers!
 

[Sukrim]

*snip*

What do you guys think about it? I'll use it for sure. 

This would totally invalidate the whole effort of pool hopping and roughly be the equivalent of just mining at the same pool for a longer period of time.

Not if we use only pools as backup that have hopping proof algorithms. It just lowers variance to mine at one of the 3 *PPS pools (ars, eligius, bitpit), in the longer run it does NOT hurt anyone to mine at PPLNS pools or others instead as backup.

After all, I still have a lot of accounts on a lot of pools where I could mine instead when no Prop. Pool is "hot" right now.

If we use "highest number of round shares" as measurement, we will help these pools even more, as many less educated miners tend to run away once rounds take longer and we can provide a quite high hash rate with the users of this program (~100 GH/s). Also we have more backup pools.

I personally would enable any pool with automatic + full 8-digit payouts (I hate checking + logging in to a dozen webpages every few days) as backup pool.

[macboy80]

Code:

[22:02:43] Error in pool api for nofeemining
[22:02:45] Error in pool api for bitclockers

In localhost:8337/stats, both those jump to 10000000000 and obviously another pool is selected

When shares can be submitted just fine but the pools web page is not answering in a split second, scripts starts a completely unnecessary hop from a perfectly working pool.  Can you calm this down a bit?

Cheers!
 

+1

[c00w]

1) Calm down api?
Yeah. I can make it not set the shares to 10,000 but if an api goes down then that pool will hover at its current share level and may result in people mining it for way to long. Or i could make the api_disable work but then the pool will get api_disable if its shares are static/the website is down for to long.I could add an api delagger to solve that problem.

But the question is: rewrite of api system or bitcoind integration?

2) Are bitclockers and triple still using a hoppable algorithms?
If they are i'll reenable them by default.

[Tmoney]

I've been testing mine_nmc.  It works great, however, total pool shares aren't displayed on the stats page.  This goes for mine_slush as well.

[Clipse]

1) Calm down api?
Yeah. I can make it not set the shares to 10,000 but if an api goes down then that pool will hover at its current share level and may result in people mining it for way to long. Or i could make the api_disable work but then the pool will get api_disable if its shares are static/the website is down for to long.I could add an api delagger to solve that problem.

But the question is: rewrite of api system or bitcoind integration?

2) Are bitclockers and triple still using a hoppable algorithms?
If they are i'll reenable them by default.

bitcoind integration seems higher priority when comparing the 2 issues

[EskimoBob]

1) Calm down api?
Yeah. I can make it not set the shares to 10,000 but if an api goes down then that pool will hover at its current share level and may result in people mining it for way to long. Or i could make the api_disable work but then the pool will get api_disable if its shares are static/the website is down for to long.I could add an api delagger to solve that problem.

But the question is: rewrite of api system or bitcoind integration?

2) Are bitclockers and triple still using a hoppable algorithms?
If they are i'll reenable them by default.

Pardon my bad English but by "pools web page is not answering in a split second, scripts starts a completely unnecessary hop from a perfectly working pool.  Can you calm this down a bit? " I am trying to say something like:

1. Get the stats
2. no connection (User timeout caused connection failure.)
3. try one more time if no connection move one and hop
  3.1 if connection OK, gets stats and do not hop.

Hopefully this makes more sense  
 

[hawks5999]

is mtred IP banning now? or is it just me?

I'm also banned.

Hmm... so were we regex'ing them or hitting json?

[Tmoney]

json, what about you?

[c00w]

1) mtred default is json

[dewon]

I got banned also 

[hawks5999]

so they are just being pricks about it then, I guess.
Oh well, moving on.
'role':'removefromlist'

[bb]

*snip*

What do you guys think about it? I'll use it for sure. 

This would totally invalidate the whole effort of pool hopping and roughly be the equivalent of just mining at the same pool for a longer period of time.

Not if we use only pools as backup that have hopping proof algorithms. It just lowers variance to mine at one of the 3 *PPS pools (ars, eligius, bitpit), in the longer run it does NOT hurt anyone to mine at PPLNS pools or others instead as backup.

After all, I still have a lot of accounts on a lot of pools where I could mine instead when no Prop. Pool is "hot" right now.

If we use "highest number of round shares" as measurement, we will help these pools even more, as many less educated miners tend to run away once rounds take longer and we can provide a quite high hash rate with the users of this program (~100 GH/s). Also we have more backup pools.

I personally would enable any pool with automatic + full 8-digit payouts (I hate checking + logging in to a dozen webpages every few days) as backup pool.

I think the proposal was to hop in late on proportional pools.

For pools with fair payout algorithms this would be an option, although I would prefer mining the pool with the least stale rate.

[joulesbeef]

me and a friend hopper can still get on mtred.

they did not sound like they were going to ban people.

they said they were going to change the payout methods.

Hey, the new code is almost complete, had to finish some things for work this week and been kinda hectic.
But we will soon be offering both prop/and pps models; similar to deepbit, but with 0% Fees as always


...


[–]RedditorRex (_) 3 points 6 days ago (4|1)
This plan will benefit both dedicated users and hoppers. Hoppers can continue to mine on a prop pool, while others can get paid via the pps method. Everyone gets paid how they want, and the pool will cover both long and short block rewards.
And those bullets are still 100% correct..

they dont want to ban us.. something is wrong on your end i bet

[macboy80]

But the question is: rewrite of api system or bitcoind integration?

I'm not sure what bitcoind integration entails. Does that mean we would be able to track payouts via the web interface?
Would that mean we needed a wallet.dat on our host machine? If so how would it be secured?

On the note about api failures, I think there should be something to keep from switching between the optimal pool that is lagging and the second option. Maybe a configurable countdown timer or X successful api polls before returning to a lagging pool. I too have noticed the constant switching back and forth.