bitHopper: Python Pool Hopper Proxy

[organofcorti]

I think Pay Per Last N Share pools could be worth hopping if you hop in when >250% shares are done (or another amount, calculated on statistics).

A sort of inversed hopping.
The chance is big that after >250 shares (or another amount, should be calculated on statistics) the block will be found and because you are paid PPLNS you get full reward for it.

Any thoughts?

Nope. Did a monte carlo on that (I'll post the results on hoppersden), PPLNS never pays above 1.0 and never pays 1.0 unless you're there the whole round. That isn't to say there aren't strategies though.

What if you were to do what we are doing to slush?  Like as soon as they hit difficulty number of shares we hop on for 10% and then hop off.  Most rounds we get nothing but some rounds we get full payment . . .

That's next on my list. These sims are computationally expensive though and I don't know how to get OpenGL working for them so a very accurate sim with lots of datapoints can take between 12 and 72 hours on my little old laptop.

[1714207144]

1714207144

[bitcoindaddy]

I was about to disable bitclockers and then their efficiency jumped from 78% to 228.5%.  Can't complain about that.

I've never seen any number besides 0.00 in my efficiency fields - of course, I restart the hopper at least once a day because of user.cfg changes, git pulls, etc.

[Zoomer]

If anyone pulled from the github and are gettings error 24, this is what it needs to be changed to:
api_key: <br/>Round Shares:([ 0-9]+)<br/>

Tried pushing but of course it doesn't work.

What pool is this?

BTCPool24

[muyoso]

I was about to disable bitclockers and then their efficiency jumped from 78% to 228.5%.  Can't complain about that.

I've never seen any number besides 0.00 in my efficiency fields - of course, I restart the hopper at least once a day because of user.cfg changes, git pulls, etc.

You have to manually input earnings to see any efficiency ratings.

[bitcoindaddy]

You have to manually input earnings to see any efficiency ratings.

Do you enter a number every time you take money out of the pool (payout to your wallet) (is it additive)?, or do you update the BTC value occasionally with your pool BTC balance?

And it's only good for the shares that bitHopper "knows" about, right? There's no way to enter previous shares into the database.

[Endeavour79]

How do I completely disable the status page and the server at port 8337?

[jkminkov]

I think Pay Per Last N Share pools could be worth hopping if you hop in when >250% shares are done (or another amount, calculated on statistics).

A sort of inversed hopping.
The chance is big that after >250 shares (or another amount, should be calculated on statistics) the block will be found and because you are paid PPLNS you get full reward for it.

Any thoughts?

250% is too early, biggest ever block was 16M shares - 846%, so you should hop @ 430% * difficulty and you will always end in 2nd half of any round, but that long blocks are rare, so maybe 300-350% is good target

organofcorti, PPLNS pool should not be backup pool alone, change your setup for simulation - at least 3 pools - 1 prop, 1 pps and 1 pplns

[c00w]

How to completely disable the status page?
Um I can add an option I guess. Or just delete all of the stuff in bitSite's getchild besides return self.

I just finished reworking LP to poll all servers. I'm not sure if I should release it yet however as well all the testing I have done is with sending works and I'm waiting to see how it works when it receives an LP response.

Then its slicing time as that appears to be really needed. And its the oldest issue.

[Clipse]

How to completely disable the status page?
Um I can add an option I guess. Or just delete all of the stuff in bitSite's getchild besides return self.

I just finished reworking LP to poll all servers. I'm not sure if I should release it yet however as well all the testing I have done is with sending works and I'm waiting to see how it works when it receives an LP response.

Then its slicing time as that appears to be really needed. And its the oldest issue.

I think you should really add the work ryo did to your version, from my testing the dynamic penality system is working out alot more profitable.

It just makes it easier to move on with latest updates you make since ryo's version is pretty much done afaik and he is only updating it from time to time with few changes you make in the master version thus it would be less time wasting if we could put his fork into master version.

[c00w]

Merging ryo's version in:
I'm working on it. I don't understand why dynamic penalties + slicing are needed. But I'm merging in slicing right now. Then lots of cleanup. Then dynamic penalties. Especially for backup servers to represent their fee percentage.

[paraipan]

How to completely disable the status page?
Um I can add an option I guess. Or just delete all of the stuff in bitSite's getchild besides return self.

I just finished reworking LP to poll all servers. I'm not sure if I should release it yet however as well all the testing I have done is with sending works and I'm waiting to see how it works when it receives an LP response.

Then its slicing time as that appears to be really needed. And its the oldest issue.

I think you should really add the work ryo did to your version, from my testing the dynamic penality system is working out alot more profitable.

It just makes it easier to move on with latest updates you make since ryo's version is pretty much done afaik and he is only updating it from time to time with few changes you make in the master version thus it would be less time wasting if we could put his fork into master version.

Correct me if I'm wrong but what c00w tries to do here with LP has nothing in common with ryo's penalty and slicing from flower altough it would be nice to have it all in one package

[c00w]

I just added a new LP system and a slice scheduler similar to flowers. New lp is on by default. Scheduler uses --scheduler SliceScheduler

Oh and ryou's dynamic penalty doesn't conflict with my code. Its just another item that needs to get added.

[paraipan]

I just added a new LP system and a slice scheduler similar to flowers. New lp is on by default. Scheduler uses --scheduler SliceScheduler

wow, nice man, eh the LP stuff in beta-testing I guess, my production serv. wouldn't be very grateful if I mess up with it again

edit: testing in progress...  just joking about the server

[burp]

Why do we need slicing? Can't we just mine on multiple pools simultaneously? That should work with current versions that sort the shares to the correct pools. If two pools roughly have the same amount of shares, just mine on both at the same time.

[c00w]

Thats the next step. And if you want to modify the slice scheduler to do that go ahead. But currently you can only have 1 current server so you need to change it in order to give a decent amount of work to each valid server. I want to slice it based on shares submitted to server in the current block. However a time based slice is a lot quicker to implement.

[muyoso]

You have to manually input earnings to see any efficiency ratings.

Do you enter a number every time you take money out of the pool (payout to your wallet) (is it additive)?, or do you update the BTC value occasionally with your pool BTC balance?

And it's only good for the shares that bitHopper "knows" about, right? There's no way to enter previous shares into the database.

Yea, you have to only give it the rounds that bithopper has kept track of.  Whenever you update the client with a new version it resets and I don't know of how to carry stats over.  Its not additive, you have to add in a new total each time.

[c00w]

@muyuso
Thats actually a bug. It should store the payouts but for some reason it is not working for basically everyone.

[iopq]

why don't we scrape balances from pool pages? slush has lots of balances and stuff

[c00w]

stats.py scrapes balances from user apis. Its just not seen a lot of love and supports like two sites.

[gerOZ]

Code:

Unhandled error in Deferred:
Unhandled Error
Traceback (most recent call last):
  File "G:\bitcoin\hopping\c00w-bitHopper-f597e2a\bitHopper.py", line 44, in __i
nit__
    self.db = database.Database(self)
  File "G:\bitcoin\hopping\c00w-bitHopper-f597e2a\database.py", line 37, in __in
it__
    call.start(60)
  File "G:\Python27\lib\site-packages\twisted\internet\task.py", line 163, in st
art
    self()
  File "G:\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 "G:\Python27\lib\site-packages\twisted\internet\defer.py", line 133, in m
aybeDeferred
    result = f(*args, **kw)
  File "G:\bitcoin\hopping\c00w-bitHopper-f597e2a\database.py", line 96, in writ
e_database
    self.update_user_shares_db()
  File "G:\bitcoin\hopping\c00w-bitHopper-f597e2a\database.py", line 167, in upd
ate_user_shares_db
    self.curs.execute(sql)
sqlite3.OperationalError: no such column: user

hmm... i have a trouble with new update