nice feature, exactly what was needed man
you feel like making a git pull request ?
Topic: bitHopper: Python Pool Hopper Proxy - page 109. (Read 355689 times)
@burp
nice feature, exactly what was needed man
you feel like making a git pull request ?
nice feature, exactly what was needed man
you feel like making a git pull request ?
Also: Why do I have to speficy api_* now though I only use a pool for backup? This wasn't required earlier…
I'm getting "Error in pool api for …" which is unnecessary for backup pools.
pool.py: api_pull should not include 'backup', should it?
I'm getting "Error in pool api for …" which is unnecessary for backup pools.
pool.py: api_pull should not include 'backup', should it?
This is prob a slight mixup in code with regards to the charity pool mining that would mine at the backup pool with highest share count.
Also: Why do I have to speficy api_* now though I only use a pool for backup? This wasn't required earlier…
I'm getting "Error in pool api for …" which is unnecessary for backup pools.
pool.py: api_pull should not include 'backup', should it?
I'm getting "Error in pool api for …" which is unnecessary for backup pools.
pool.py: api_pull should not include 'backup', should it?
I have written a patch so that only the really wanted pools, that is pools you specify in the user.cfg are used. You don't have to specify all pools from the pools.cfg you would have to before, because of interpolation key requirements (like with btcg).
Code:
diff --git a/pool.py b/pool.py
index 6b5d8ca..571ca02 100644
--- a/pool.py
+++ b/pool.py
@@ -28,6 +28,9 @@ class Pool():
if len(read) == 0:
bitHopper.log_msg("user.cfg not found. You may need to move it from user.cfg.default")
os._exit(1)
+
+ userpools = parser.sections()
+
try:
# determine if application is a script file or frozen exe
if hasattr(sys, 'frozen'):
@@ -40,8 +43,9 @@ class Pool():
if len(read) == 0:
bitHopper.log_msg("pool.cfg not found.")
os._exit(1)
+
pools = parser.sections()
- for pool in pools:
+ for pool in userpools:
self.servers[pool] = dict(parser.items(pool))
if self.servers == {}:
haha sigh ive decided to just give up on bitclockers their system doesnt seem to handle more than 230Gh and everyone start to get cycled, it has nothing to do with being a hopper since I saw other users reporting they also keep getting idle miner, 20second reconnect.
Till they upgrade its just not sane to waste gpu cycles there.
Till they upgrade its just not sane to waste gpu cycles there.
Does anyone know what causes this error: Im trying to use nofeemining's new pool as a backup but I get the above error when trying to use it. they use the address: http://nofeemining.appspot.com now.
Code:
File "/home/user/bitHopper/_newclient.py", line 1331, in _finishResponse
connHeaders = self._parser.connHeaders.getRawHeaders('connection')
exceptions.AttributeError: 'NoneType' object has no attribute 'connHeaders'
There is nothing to revert when the file was not in the repository before. I didn't know git allowed such things to happen, well now I do
Ouch indeed - created a quick fix renaming pool.cfg to pools.cfg.Sorry for that!
You can however just use the default for a minute and check out the nice clickable links to each pool on the statpage!
Oh, the json seems nice, I'll edit it in.
Edit: done
Can you also add correct config for btcpool24.com. They have a JSON stats now at http://www.btcpool24.com/json_stats.php
Thank you.
There is nothing to revert when the file was not in the repository before. I didn't know git allowed such things to happen, well now I do
Ouch indeed - created a quick fix renaming pool.cfg to pools.cfg.Sorry for that!
You can however just use the default for a minute and check out the nice clickable links to each pool on the statpage!
Oh, the json seems nice, I'll edit it in.
Edit: done
api_key:
Round Shares:([ 0-9]+)
For BTCPool24.com
Missing the "/" after "br"...
Adding them fixed it.
Round Shares:([ 0-9]+)
For BTCPool24.com
Missing the "/" after "br"...
Adding them fixed it.
They have json now, should we use that?
http://www.btcpool24.com/json_stats.php
Does reverting not work/help?
Anyways, the bmunion fail is maybe part of their "heavily being worked on security" https://bitcointalksearch.org/topic/m.417892
Seems like a very sophisticated system to... being able to cheat your own miners unnoticed at will!
Anyways, the bmunion fail is maybe part of their "heavily being worked on security" https://bitcointalksearch.org/topic/m.417892
Seems like a very sophisticated system to... being able to cheat your own miners unnoticed at will!
There is nothing to revert when the file was not in the repository before. I didn't know git allowed such things to happen, well now I do
Oh well, fantastic choice to put pool.cfg in the repository after it was used as a custom user configuration. I had several customized pool configurations there, not to mention all the usernames and passwords. Now everything is lost during the pull.
A warning to everyone: backup your pool.cfg before pulling or commit it to the repository and merge, otherwise it's los!
A warning to everyone: backup your pool.cfg before pulling or commit it to the repository and merge, otherwise it's los!
Ouch man, that sucks. I'm glad I haven't pulled it yet
Does reverting not work/help?
Anyways, the bmunion fail is maybe part of their "heavily being worked on security" https://bitcointalksearch.org/topic/m.417892
Seems like a very sophisticated system to... being able to cheat your own miners unnoticed at will!
Anyways, the bmunion fail is maybe part of their "heavily being worked on security" https://bitcointalksearch.org/topic/m.417892
Seems like a very sophisticated system to... being able to cheat your own miners unnoticed at will!
Oh well, fantastic choice to put pool.cfg in the repository after it was used as a custom user configuration. I had several customized pool configurations there, not to mention all the usernames and passwords. Now everything is lost during the pull.
A warning to everyone: backup your pool.cfg before pulling or commit it to the repository and merge, otherwise it's los!
A warning to everyone: backup your pool.cfg before pulling or commit it to the repository and merge, otherwise it's los!
seem like bmunion's owner doesn't like the "attention" he's getting
Or the pool just broke down a bit...
seem like bmunion's owner doesn't like the "attention" he's getting
@MaGNeT:
Weird, I got the (badly translated...) german version and it readsAlso you seem to have brackets () there?!
Weird, I got the (badly translated...) german version and it reads
Code:
Aktueller Block: 139170
Aktuelle Difficulty: 1888786.71
PPS BTC/Share: 0.00002647
Runden Shares: 4687996
Maybe it depends on your IP?
I'm in the Netherlands, next to Germany so you would expect... German... But the stats page is English when I look at it
@MaGNeT:
Weird, I got the (badly translated...) german version and it readsAlso you seem to have brackets () there?!
Weird, I got the (badly translated...) german version and it reads
Code:
Aktueller Block: 139170
Aktuelle Difficulty: 1888786.71
PPS BTC/Share: 0.00002647
Runden Shares: 4687996
what is "mine_friendly" and how it works?
It is a way to mine hopper friendly pools, in hopes that it'll give hoppers a bad name. Some people are more interested in squeezing every last percent of efficiency more than being good community members. What it does is hop the pool normally, leaving after 43%, but when they have particularity bad blocks (> 200% difficulty) and there is nowhere to hop, it jumps to them to help get a new block.
api_key:
Round Shares:([ 0-9]+)
For BTCPool24.com
Missing the "/" after "br"...
Adding them fixed it.
Round Shares:([ 0-9]+)
For BTCPool24.com
Missing the "/" after "br"...
Adding them fixed it.
It kills your hopping income by hopping back into long rounds of prop pools instead of mining at a proper backup pool.
We really should rename it "mine_charity"... You only risk being tagged by the pool as hopper and still loosing massive on long rounds, there is no reason other than charity to use this method.
We really should rename it "mine_charity"... You only risk being tagged by the pool as hopper and still loosing massive on long rounds, there is no reason other than charity to use this method.
Jump to: