bitHopper: Python Pool Hopper Proxy

[hawks5999]

With "mine_deepbit" when do we jump away from a pool?  I think bithopper is staying longer than 43%, which should be around 10 minutes right?  It almost feels like I am mining deepbit until 100% of difficulty.

How do you set threshold with 1.6.1?

startup parameter

--threshold=

1 = 100%
.90 = 90%
.43 = 43% (default)

[1714029066]

1714029066

[1714029066]

1714029066

[1714029066]

1714029066

[muyoso]

I see bitclockers is better than before but still far from perfect.  Is there anyway to just reduce the getwork requests?  I'm ignorant as to why cherrypicker for example hops it flawlessly with a normal number of getwork requests and bithopper doesn't.

Also, when Slush finds a block why isn't BH switching to it?  It just keeps mining at deepbit. 

[enmaku]

So all this craziness with IXCoin recently has me thinking... How hard would it be to code in some checks to automatically compare the profitability of BTC, NMC etc. to automatically make the switch for the brief span in which NMC mining is more profitable? Once difficulty settles down on IXC we could do the same for them (easy enough since bitparking runs both the NMC and IXC exchanges). We could hack together the logic and just have the appropriate bitparking pool represented as some arbitrary low percent when it's more profitable and use the standard 10^10 when it's not, all configurable of course.

Anyone know how hard it would be to do this?

[c00w]

@Muyoso
Reducing the number of getworks?
We are working on it. Also issues with scheduling are confusing and I need to rewrite the whole scheduler system. Which scheduler are you using?

@enmaku
Its not very hard. Someone just has to code it.

[enmaku]

@enmaku
Its not very hard. Someone just has to code it.

I'll see if I can find the time this weekend to give it a shot. The big hurdle is that, to my knowledge neither of the bitparking exchanges has an API available, and I'm not exactly a regex master.

If anyone knows of such an API or happens to have some already-existing regex to get the current NMC value I'd be forever in your debt. 

[muyoso]

@Muyoso
Reducing the number of getworks?
We are working on it. Also issues with scheduling are confusing and I need to rewrite the whole scheduler system. Which scheduler are you using?

Default scheduler. 

[Sukrim]

Do you think the current value is really the best one? I'd rather use the 24h average from http://www.nmcwatch.com/...

"average: ([\.0-9]+).*<br/>" should work I think... Unfortunately (for them) there isn't any API advertised.

[c00w]

Oh and if you want to integrate all the info on nmc etc... into the difficulty module including prices that would be awesome. There already is nmc difficulty and adding everything else should be pretty quick.

[enmaku]

I'll see what I can do. NMCWatch looks quite promising and I thank you in advance for the regex Sukrim. c00w, I'd completely forgotten we already have NMC difficulty as well as bitparking, so I'd just need to do the math and override the percentages where necessary... And perhaps add a new role, similar to what you did with mine_slush (mine_nmc perhaps?).

Could also let someone else do the math for us and just compare the USD figures from http://tvori.info/bitcoin/charts/ - easy regex too, from the look of it.

[deepceleron]

I'm trying the pool block detection features in this software. The LP detection algorithm needs the ability to fine-tune timing. Some pools announce blocks by LPs faster than others; the problem manifests that a fast/close pool can get LP push to the miner before the pool that actually solved the block. A block-finding pool can be slower than others from the pool's infrastructure, number of pool miners in that pool needing the LP push, and geographic location (and perhaps even by pool ops messing with LP timing themselves).

The correction factor could be a pool.cfg option to 'slow down' fast-announcing pools that cause false positives, a user.cfg option like "Delay_LP: 2" seconds if block-finding pools are consistently being beaten in LP push speed by this fast/small pool by a second.

Also, if anyone with a btcmine account would be willing to add worker for me to get info with and PM me, it would be appreciated!

[muyoso]

Its almost as if I am just mining exclusively on deepbit now.  I almost never leave.  I think instead of trying to estimate shares through the hashrate it would be better to just leave after 10-12 minutes after a round start.  I find on the longer rounds.  I SHOULD be submitting no more than 100ish shares per round as that is about the time that deepbit passes the 43% threshold.  I am submitting 2-500 shares on the longer rounds and its obliterating my efficiency.  I am at 115% efficiency with deepbit overall.



A round with 6 million shares should have no more shares submitted by me than a round with 1 million shares, but they have 2-4x as many.  Something is either causing bithopper to miscalculate the 43% threshold or allowing me to mine right through it.

[TenthReality]

Random question here, if an LP new block comes in from a pool, should that not override anything the API is telling the scheduler?

Update:
I may have answered it myself after digging through lp.yc,  if the pool is set to mine_deepbit' and LP is going, ,it'll reset the shares count.

[creativex]

so why not just raise db's penalty so you leave sooner?

[muyoso]

so why not just raise db's penalty so you leave sooner?

I have it at the default of 43%.  If I do that then won't I leave sooner on the short round and kill my efficiency even more?  What I am saying is that something isn't right.

[r2edu]

@deepceleron: I don´t understand your final request.. (i´am from Arg. so my english is not that good), if you can explain me better i can help, i got a btcmine account

---

I´m with latest version 0.1.6.2-1, and deepbit doesn´t work.. when start a round my miner just die. I wait for about 2-5 min. and nothing, so i disable it and hop to another pool, then the share count of db never stops...

As i said, Polmine is working really good, and BCLC founds blocks that doesn´t belong to it (i mean in BH, resets to 0 but the stats in its web keeps counting for hours), so i´am mining it "the old way"

Maybe the problem is my location, Argentina?

[creativex]

I like aiming for 25% on db, but sometimes it skips over it and I'm there a little bit longer, but it's not exactly killing efficiency. I suggest fiddling with the penalties till you get what you're looking for.

[muyoso]

I like aiming for 25% on db, but sometimes it skips over it and I'm there a little bit longer, but it's not exactly killing efficiency. I suggest fiddling with the penalties till you get what you're looking for.

Yea, I could do that.  I think an easier way would just be a timer though.  Deepbit is almost always 26-27 minutes per block average.  So just hop after 26.5*.43 minutes = 11.395 or say 11.5 minutes.

Damnit, bithopper missed out on a fast round on bitcoinpool because it was too busy mining at deepbit for hours on end.  Back to cherrypicker.

[c00w]

@r2edu
Are you seeing any errors on the front end?

Lp Penalty?
Sure.

Oh and there already is a mine_nmc...

[r2edu]

@c00w: I don´t know if this is what you´re asking, but i think no, deepbit is in yellow and the share count of the round count normal, but my miner (GUIMiner x3vgas), just stop.

I´ll try to run BH with --debug so i can give you more details! (if it worth it, you tell me)

[joulesbeef]

move bitminers union to the unhoppable part of your lists