Topic: bitHopper: Python Pool Hopper Proxy - page 165. (Read 355816 times)

Except that Triplemining is now stuck on 143849 shares for me, and bitHopper won't mine them because it's been on that for so long.

Yea, should be mining at triple right now but for some reason their stats are reporting way too high.

Heh, triplemining added an odd bit of code to their stats page:


I don't think it had the effect they wanted, though. Instead of bitHopper seeing the 1000 and assuming they are on a new block, it doesn't catch this line at all in the scrape and is grabbing the stats for the previous block. Or perhaps that was the intended effect?

It's funny that they have "No pool hopping protection!" on their home page, but want to start mucking with code to prevent/deter hopping?

Do you...understand the meaning of what script kiddie means? I don't think you do.  And no, i am not a pool operator though i did start writing my front end once only to find it a bother to maintain a pool.

I was doing that until a few friends decided to give a hand mining and they lack the patience to do advanced pc stuff
want to give some info on public ip to a select few persons (I know they could mess with enabling an setting penalty but they have been warned about that >

use a firewall and tunnel this port through ssh.
works fine for me (i am using my hopper on a vserver)

yup with pleasure (btc adress not in sight )

ryouiki would be hard to implement a basic password to stat page ? If you do it , great, if not please explain how to coz having it wide open on public ip just makes me feel uncomfortable. thanks

dont't start another round of that shit, this time I will personally see that the guilty gets banned. I came here to read good stuff not the ppl's personal vendetta's

btw: if a pool delays stats you cannot hopp in blindfolded, not knowing this tells us you are 1. a script kiddie jerkin' around 2. you are a pool op looking for trouble after seeing his pool hopped. In either case i recommend you reading at least some pages of this thread or go to another part of bitcoins.org forum, it' huge and you could fit perfectly in other thread

@c00w: if I update to a new version, how do I keep my stats to that point?

great, i'm testing it atm


Currently bithopper is only mining on tripple and not on the Namecoin pools.
The Problem for hopping Namecoins and Bitcoins is, that the Namecoin Profitabilty depends on the Exchange Price NMC/BTC. ATM Namecoin Mining is about 50% more Effective than mining Bitcoins, i tryed using 0.25 Penalty for the NMC Pools but it doesn`t work.

Maybe the easiest sollution is enabling the NMC pools and disabling the BTC pools, but bithopper is still submitting to the BTC Backuppools instead of the (mor profitale) NMC Pools.
So i had to disable the Backup Pools and use bitparking for backup and namebit for hopping.

//Edit:

ok was confused its working.

Early shares on BTC pools are more provitable, then shares on NMC Pools.
Namebit had a new block and BitHopper switched from MTRed to NameBit


I modified NMC Pool Penalty to adjust the NMC/BTC Value for me

Thanks

//Edit2:
Final thoughts.

On 50% [~15L Shares) BitHopper swtched from BitParking to Arsbitcoin.
But Namecoins are more effective, than Bitcoins. For Switching Pools you need the NMC/Bitcoin Profitably, so you only switch to a BTC Pool from a NMC pool when the NMC Pools has a "total efficentcy" of nmc_difficulty*.431 * NMC/Bitcoin Ratio (atm 1.39) > http://dot-bit.org/tools/nextDifficulty.php (or just use a price from namecoinexchange hey have an API http://dot-bit.org/forum/viewtopic.php?p=964#p964 )
But that's just to much work, for just 2 Days of Namecoinmining.

I'll disable the namecoin pools again.

latest Mod fully supports NameCoin pools
added BitParking and NameBit



if you feel lucky, now you can donate NMC to me

Good question, Dikidera. A lot of people confuse pool-hopping with randomly jumping from pool to pool to spread our your shares and minimise variance. But that is what it definitely is not. A few very clever people showed early this year (late last year? whatever) that in a proportional pool, you can increase your average coinage per share by never staying in the pool after the total shares have reached 0.43* Then you hop to another proportional pool with total shares under 0.43* or to a PPS pool.

Another point is that it turns out that earlier in a round a share has more worth than later in a round. This means it's also better to hop from a proportional pool at, for example, 0.3* to a proportional pool at 0.1*difficulty.

This is unintuitive, but if you have the time to go over the math, it's fascinating. I've posted these links before, but they're worth posting again:

http://mining.bitcoin.cz/media/download/poolcheating.pdf

http://www.bitcoinservice.co.uk/files/111


If you aren't interested in the math just try it your self for a week or so and look at the results.

Quote

Did i give you permission to speak slave?

Come on! Srsly? You can't tell when people are trying to get a rise out of you? My mum always told me, "ignore them and they'll stop bothering you". It didn't work, but whatever.

Anyone got some namecoin pools working?

Bitparking for backup purposes is no problem, but other namecoin pools seems to have no API too.

Theres Poolmunity with an API, but i didn't got it working.

The Problem with namecoins is, that the'll be unprofitable in 2 Days, so it's maybe not worth putting some serious work in it.

Pretty sure bitcoins.lc is delaying stats by 30 minutes.  By the time I switch over they usually already have 180k shares.  Is it still profitable to mine there when you miss the first 200k shares?  I see no real reason why it wouldn't be . . .

Edit:  Looks like it really effects payouts for smaller rounds.  I should be getting per round payouts in the .077 range for rounds under 700k shares if I was to jump in immediately, but I am seeing payouts in the .03 range instead.  Also missed a block entirely because it was less than 30 mins.  

Still more profitable than mining at Arsbitcoin with those same number of shares, but payouts are drastically reduced.

Did i give you permission to speak slave?

Sup Pinky, where is the Brain ?

What would be the use of doing that?  Do you know how inefficient that would be?  Request work from pool 1, send a share,  disconnect from pool 1, connect to pool 2, request work, send a share, etc, etc, etc. . .

If that was what pool hopping was, why wouldn't you just open up multiple workers, one per pool and let them mine away sharing your GPU?

Just to make it clear, your concept of pool hopping is not remotely correct.

Why is there a problem with delayed stats? Pool hopping is just that. You request work, send a share, switch, send a share, switch and so on....this is not how i imagine pool hopping to be.

The boost in hash rate is proportional to the number of people jumping to the pool. What this also means though is that there are more shares calculated by hoppers. So when a block is found, more bitcoins go to hoppers.

The essence of pool hopping is that statistically the first shares of a round are worth more than the last ones. Now the more pool hoppers come in to take a larger portion of early shares, the worse it is for single pool miners.

If this doesn't make enough sense, I can explain some more tomorrow. :-)


?

I really didn't have the math for this when I started, so I wiki'd up on the Poisson process and read the following papers:

http://mining.bitcoin.cz/media/download/poolcheating.pdf

http://www.bitcoinservice.co.uk/files/111


After about a month of reading, learning and experimenting I think I have a fair idea of what's going on, although I still make conceptual mistakes. The papers I've linked to will probably do a better job of teaching you about hopping than I can, so read them if you have the time and inclination - you won't waste time travelling down roads already travelled.

Cheers!