I still have a problem with p2pLP - My router seems to drop connections (like LP connections...) quite fast, so I rarely actually get Longpolls. I hoped p2pLP would still notify me of found blocks (didn't yet look deeply into the code to find out what's going on) but this doesn't seem to be the case.
Would it be possible to just set up an IRC bot that announces each block on the network and the (either confirmed or guessed) pool that owns it for people like me? The input could still come from bitHopper users via this ranking mechanism or whatever you actually use...
Topic: bitHopper: Python Pool Hopper Proxy - page 16. (Read 355768 times)
@deepceleron: how are you getting on with LP penalty - Did you end up with a significant increase in accuracy?
OMG, look at slush's block #7543:
Lots of BTC for anyone who was able to squeeze a share in. To bad I didn't
OMG, look at slush's block #7543: 
Regarding this issue: https://github.com/c00w/bitHopper/issues/177#issue_comment_form
Manual triggers for mine_deepbit pools
If a feature like this was added, being also able to execute this function through win/*nix commandline, would allow for extremely easy writing of tcl/mirc scripts that could catch blockannounces in certain IRC channels and do manual triggers. This would effectively enable hopping on pools like deepbit, btcguild etc.
Manual triggers for mine_deepbit pools
If a feature like this was added, being also able to execute this function through win/*nix commandline, would allow for extremely easy writing of tcl/mirc scripts that could catch blockannounces in certain IRC channels and do manual triggers. This would effectively enable hopping on pools like deepbit, btcguild etc.
Anyone else getting an error where BitHopper stops after a period of time?
It just gets stuck...
[14:16:38] writing to database
[14:17:38] writing to database
[14:18:38] writing to database
[14:19:38] writing to database
[14:20:38] writing to database
[14:21:38] writing to database
[14:22:38] writing to database
[14:23:38] writing to database
It just gets stuck...
[14:16:38] writing to database
[14:17:38] writing to database
[14:18:38] writing to database
[14:19:38] writing to database
[14:20:38] writing to database
[14:21:38] writing to database
[14:22:38] writing to database
[14:23:38] writing to database
+1 for this since i got the latest version
EDIT: this still isn't fixed in the latest version... just a heads up.
I get an LP call then constant "writing to database" messages.
renders my miner useless until i restart bithopper
occurs every 30 minutes approximately for me.
mines always stuck after an "LP Call" to btcserv... 0.2.2.4-68
now I will try with 0.2.2.4-83
now I will try with 0.2.2.4-83
Anyone else getting an error where BitHopper stops after a period of time?
It just gets stuck...
[14:16:38] writing to database
[14:17:38] writing to database
[14:18:38] writing to database
[14:19:38] writing to database
[14:20:38] writing to database
[14:21:38] writing to database
[14:22:38] writing to database
[14:23:38] writing to database
It just gets stuck...
[14:16:38] writing to database
[14:17:38] writing to database
[14:18:38] writing to database
[14:19:38] writing to database
[14:20:38] writing to database
[14:21:38] writing to database
[14:22:38] writing to database
[14:23:38] writing to database
The poll is pointless. If enough people say it's ethical does BMU turn off their hopper-cheating mechanism or if enough people say hopping is unethical will he just keep cheating hoppers?
I doubt the former will happen and the latter will happen regardless. When you have an unethical pool operator who has no qualms with cheating a portion of his clients, there is really no limit to how unethical he'll be.
I doubt the former will happen and the latter will happen regardless. When you have an unethical pool operator who has no qualms with cheating a portion of his clients, there is really no limit to how unethical he'll be.
The real poll must be: "do you think BMU pool ops are ethical?" :p
all my shares from the _old_ pool are away https://bitcointalk.org/index.php?topic=32921.200
Poll
Question: do you think pool hopping is ethical? YES 2 (50%)
NO 2 (50%)
Total Voters: 4
Poll
Question: do you think pool hopping is ethical? YES 2 (50%)
NO 2 (50%)
Total Voters: 4
The real poll must be: "do you think BMU pool ops are ethical?" :p
LOTS of problems with that pool since ever... close it down, is a fail after fail after fail heheh
I got the same problem as @kbsbtc, BH just freeze the stats page and keep showing "writing to database", miner dies and have to close and run it again.. (v0.2.2.4-68 with --auth --p2pLP and OldDefaultScheduler)
Also getting a lots of "Not enough votes in one direction to make a decision"
and also I send my firsts shares to BtcGuild
exactly the same here... Also getting a lots of "Not enough votes in one direction to make a decision"
and also I send my firsts shares to BtcGuild
https://bitcointalk.org/index.php?topic=32921.200
Poll
Question: do you think pool hopping is ethical? YES 2 (50%)
NO 2 (50%)
Total Voters: 4
Poll
Question: do you think pool hopping is ethical? YES 2 (50%)
NO 2 (50%)
Total Voters: 4
Can anyone send me an invite, please? I am keen to read it.
Sorry, Tobin, hoppers only.
Is there some kind of examination which one has to pass
.Not really
But hoppersden is for info we don't really want leakedI saw you've been a forumite since early June and you've never posted anything anti-hopper (harrumph, Magnet
) so get in a few posts here and someone will send you an invite soon..One small contribution:
As most of you know, Bitcoinpool has wrong JSON stats. I have seen that bitHopper uses the round duration and the pool speed to approximate the current share number. A somewhat cheaper (in terms of bandwidth) and maybe more exact method is the following:
Grab the account info of an arbitrary user in json-format, e.g. http://bitcoinpool.com/user.php?u=cristy&json=1 .
You see his submitted shares and his estimated rewards for this round. You can get the approximated number of roundshares easily by
appr_shares = 50*(submitted shares)/(estimated rewards)
Example:
submitted: 14670
estimated: 0.52180054
appr_shares = 1405709.55
This method can be made even more exact if you know how much the user donates.
Maybe it is worth it to be added to bitHopper.
I posted this exact method a few days ago and nobody seemed to mather
****
I got the same problem as @kbsbtc, BH just freeze the stats page and keep showing "writing to database", miner dies and have to close and run it again.. (v0.2.2.4-68 with --auth --p2pLP and OldDefaultScheduler)
Also getting a lots of "Not enough votes in one direction to make a decision"
and also I send my firsts shares to BtcGuild
c00w, seem to be having a problem with the latest gitpull. BH got stuck on "Writing to database" kept looping that over and over. Running it with no flags
"How to hop Slush's pool" now posted to Hopper's Den. Comments welcome!
Please don't copy and paste it back here though.
http://hoppersden.info/entry.php?15-How-to-hop-1-Slush-s-pool.
Can anyone send me an invite, please? I am keen to read it.Please don't copy and paste it back here though.
http://hoppersden.info/entry.php?15-How-to-hop-1-Slush-s-pool.
The article doesn't exist on that site.
The link doesn't work for you? Does for me. Sorry. Just go to Blogs->recent entries
Nope, doesn't seem to be there at all. Weird.
Fixed, I think. I hit 'draft' instead of 'publish'. Duh. Mind checking to see if it worked?
So it seems I have to share my secret knowledge with you all .
One small contribution:
As most of you know, Bitcoinpool has wrong JSON stats. I have seen that bitHopper uses the round duration and the pool speed to approximate the current share number. A somewhat cheaper (in terms of bandwidth) and maybe more exact method is the following:
Grab the account info of an arbitrary user in json-format, e.g. http://bitcoinpool.com/user.php?u=cristy&json=1 .
You see his submitted shares and his estimated rewards for this round. You can get the approximated number of roundshares easily by
appr_shares = 50*(submitted shares)/(estimated rewards)
Example:
submitted: 14670
estimated: 0.52180054
appr_shares = 1405709.55
This method can be made even more exact if you know how much the user donates.
Maybe it is worth it to be added to bitHopper.
.One small contribution:
As most of you know, Bitcoinpool has wrong JSON stats. I have seen that bitHopper uses the round duration and the pool speed to approximate the current share number. A somewhat cheaper (in terms of bandwidth) and maybe more exact method is the following:
Grab the account info of an arbitrary user in json-format, e.g. http://bitcoinpool.com/user.php?u=cristy&json=1 .
You see his submitted shares and his estimated rewards for this round. You can get the approximated number of roundshares easily by
appr_shares = 50*(submitted shares)/(estimated rewards)
Example:
submitted: 14670
estimated: 0.52180054
appr_shares = 1405709.55
This method can be made even more exact if you know how much the user donates.
Maybe it is worth it to be added to bitHopper.
So simple, yet obvious in hindsight. Nice one!
While we're on the bcp subject, any ideas how to get around the IP blocking (for the stats, can still send through shares ok)? I'd just use hotspot shield and then set the url to be localhost:895 but hotspot shield is not available for linux. Know any handy (easy, free) browser based proxy/vpn? All the ones I looked at cost money, weren't available for linux or had no english translation.
Can anyone send me an invite, please? I am keen to read it.
Sorry, Tobin, hoppers only.
Is there some kind of examination which one has to pass
.Not really
But hoppersden is for info we don't really want leakedI saw you've been a forumite since early June and you've never posted anything anti-hopper (harrumph, Magnet
) so get in a few posts here and someone will send you an invite soon..One small contribution:
As most of you know, Bitcoinpool has wrong JSON stats. I have seen that bitHopper uses the round duration and the pool speed to approximate the current share number. A somewhat cheaper (in terms of bandwidth) and maybe more exact method is the following:
Grab the account info of an arbitrary user in json-format, e.g. http://bitcoinpool.com/user.php?u=cristy&json=1 .
You see his submitted shares and his estimated rewards for this round. You can get the approximated number of roundshares easily by
appr_shares = 50*(submitted shares)/(estimated rewards)
Example:
submitted: 14670
estimated: 0.52180054
appr_shares = 1405709.55
This method can be made even more exact if you know how much the user donates.
Maybe it is worth it to be added to bitHopper.
"How to hop Slush's pool" now posted to Hopper's Den. Comments welcome!
Please don't copy and paste it back here though.
http://hoppersden.info/entry.php?15-How-to-hop-1-Slush-s-pool.
Can anyone send me an invite, please? I am keen to read it.Please don't copy and paste it back here though.
http://hoppersden.info/entry.php?15-How-to-hop-1-Slush-s-pool.
The article doesn't exist on that site.
The link doesn't work for you? Does for me. Sorry. Just go to Blogs->recent entries
Nope, doesn't seem to be there at all. Weird.
Yeh, odd. I'm message myself and see if he knows what is going on. Maybe I missed some option to make it public
Anyone able to hook me up with an invite? About to go to sleep, so I can PM an email later on today.
Jump to: