Code:
[triple]
name: Triple Mining
mine_address: eu1.triplemining.com:8344
api_method:re
api_address:http://api.triplemining.com/json/stats
api_key:(\d+)
role:mine
new code for triple.
json isn't applicable as [] are used instead of {}
Topic: bitHopper: Python Pool Hopper Proxy - page 157. (Read 355816 times)
new code for triple.
json isn't applicable as [] are used instead of {}
Please push/spread this api method
2) Overhammering servers?
Well I raised the minimum to 30 seconds between hits. But you really should be caching your pages and not re-rendering every time you get hit. Or provide a json interface which is a flat file updated regularly...
Well I raised the minimum to 30 seconds between hits. But you really should be caching your pages and not re-rendering every time you get hit. Or provide a json interface which is a flat file updated regularly...
Stats allready cached, but please use http://api.triplemining.com/json/stats , this way you are not using SSL and not triggering other unusefull stats.
1)eskimo?
Fixed that.
2) Overhammering servers?
Well I raised the minimum to 30 seconds between hits. But you really should be caching your pages and not re-rendering every time you get hit. Or provide a json interface which is a flat file updated regularly...
Fixed that.
2) Overhammering servers?
Well I raised the minimum to 30 seconds between hits. But you really should be caching your pages and not re-rendering every time you get hit. Or provide a json interface which is a flat file updated regularly...
would you accept a service which has (sometimes) wrong stats?
I already am. Since I am usually asleep for ~ 6 hours a day my miners can (and have) get hung up on a pool faking stats.
It is true, it would be a big target and a possible point of failure...
Maybe at least if someone could code up a local proxy one can use to accomplish the same thing, then you would at least only have one request no matter how many bitHoppers you were running.
Maybe at least if someone could code up a local proxy one can use to accomplish the same thing, then you would at least only have one request no matter how many bitHoppers you were running.
would you accept a service which has (sometimes) wrong stats?
we would need a group of trusty people
after all wrong stats means less money
we would need a group of trusty people
after all wrong stats means less money
also it would be easier for pools to fake stats explicity for that service.
But it would reduce the work to adapt to any changes to modifying the code at one point, instead of modifying code in every client.
after last pull:
Code:
------
File "/usr/lib/python2.7/site-packages/twisted/internet/base.py", line 793, in runUntilCurrent
call.func(*call.args, **call.kw)
File "/blah/MINER/bitHopper/pool.py", line 144, in update_api_server
d = work.get(self.bitHopper.json_agent,info['api_address'],Headers({'User-Agent':'Mozilla/5.0 (X11; Linux i686) AppleWebKit/535.1 (KHTML, like Gecko) Ubuntu/11.04 Chromium/14.0.825.0 Chrome/14.0.825.0 Safari/535.1'}),None)
File "/usr/lib/python2.7/site-packages/twisted/web/http_headers.py", line 141, in __init__
self.setRawHeaders(name, values)
File "/usr/lib/python2.7/site-packages/twisted/web/http_headers.py", line 201, in setRawHeaders
"instance of %r instead" % (name, type(values)))
exceptions.TypeError: Header entry 'User-Agent' should be list but found instance ofinstead
I agree, there must be a big load on servers due to all the hoppers polling, is it possible to use something like: http://btc-poolwatch.com/ to do a central stats poll and let the clients use that instead of pools directly?
i was already thinking about that.
the problem is this site is big target. it could easily be put offline.
atm i have my poolhopper running at a vserver and its publishing its stats per json.
but i am afraid of publishing this address.
also it would be easier for pools to fake stats explicity for that service.
i would do it for btc. but this could get into a fulltime job very fast.
dont bother, they are changing to PPLNS soon.
Rather get away from them now, let them see how hoppers revolting isnt a good thing
Rather get away from them now, let them see how hoppers revolting isnt a good thing
While i have no real problem with poolhoppers, but what disturbs me is that i (triplemining) get now like 10 /stats url requests every second and that starts to put a way to heavy load on my servers.
I would recommend a central database that is beeing polled by all users ..
Either way, Clipse is right and we will switch to PPLNS soon.
you could have placed a json file on your server which updates thrrough a cron-job.
buty anyway: good look with pplns
would be glad if you tell us before you'll switch.
Okay, i re-enabled the default so triplemining should work for everyone again now.
I will post a message here before we make the switch to pplns... In the meantime: Happy Mining
I agree, there must be a big load on servers due to all the hoppers polling, is it possible to use something like: http://btc-poolwatch.com/ to do a central stats poll and let the clients use that instead of pools directly?
dont bother, they are changing to PPLNS soon.
Rather get away from them now, let them see how hoppers revolting isnt a good thing
Rather get away from them now, let them see how hoppers revolting isnt a good thing
While i have no real problem with poolhoppers, but what disturbs me is that i (triplemining) get now like 10 /stats url requests every second and that starts to put a way to heavy load on my servers.
I would recommend a central database that is beeing polled by all users ..
Either way, Clipse is right and we will switch to PPLNS soon.
you could have placed a json file on your server which updates thrrough a cron-job.
buty anyway: good look with pplns
would be glad if you tell us before you'll switch.
to get triple working again:
open work.py
function: get
header = {'User-Agent': ['Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20100101 Firefox/5.0'],'Content-Type': ['application/x-www-form-urlencoded'] }
d = agent.request('GET', url, Headers(header), None)
(this is from an old version, but should not be very hard to adapt)
dont bother, they are changing to PPLNS soon.
Rather get away from them now, let them see how hoppers revolting isnt a good thing
Rather get away from them now, let them see how hoppers revolting isnt a good thing
While i have no real problem with poolhoppers, but what disturbs me is that i (triplemining) get now like 10 /stats url requests every second and that starts to put a way to heavy load on my servers.
I would recommend a central database that is beeing polled by all users ..
Either way, Clipse is right and we will switch to PPLNS soon.
dont bother, they are changing to PPLNS soon.
Rather get away from them now, let them see how hoppers revolting isnt a good thing
Rather get away from them now, let them see how hoppers revolting isnt a good thing
1) Triple?
Yeah its down. They're doing some fancy lieing I can't figure out.
Its disabled in pool.cfg.default.
2) Being to sensitive with jumps?
If you are just doing a getwork we fail servers quickly because its easy to change servers. And otherwise miners will starve. Especially miners which give up quickly like poclbm.
If you are trying to submit work we won't change that requests server on you.
Yeah its down. They're doing some fancy lieing I can't figure out.
Its disabled in pool.cfg.default.
2) Being to sensitive with jumps?
If you are just doing a getwork we fail servers quickly because its easy to change servers. And otherwise miners will starve. Especially miners which give up quickly like poclbm.
If you are trying to submit work we won't change that requests server on you.
did Triplemining managed to kick poolhoppers in the nuts?
I restarted the bitHopper and:
Code:
[23:10:52] triple: 2,444,511
[23:11:14] triple: 600
[23:11:19] nofeemining: 6,849
[23:11:26] triple: 682
Caught, jsonrpc_call insides
'user'
[23:11:37] triple: 508
[23:11:46] triple: 1,387
[23:11:56] triple: 1,360
[23:12:06] triple: 811
[23:12:16] triple: 1,747
[23:12:17] nofeemining: 7,685
[23:12:26] triple: 988
[23:12:35] Error in pool api for triple
[23:12:46] triple: 1,393
[23:12:56] triple: 1,729
[23:13:06] triple: 537
[23:13:15] nofeemining: 8,591
[23:13:16] triple: 271
[23:13:26] triple: 881
I restarted the bitHopper and:
Code:
[23:23:49] Updating Difficulty
[23:23:49] 1690906.2047244
[23:23:49] Checking Database
[23:23:49] DB Verson: 0.1
[23:23:49] Database Setup
[23:23:50] triple: 1,474
[23:23:50] Server change to triple, telling client with LP
[23:23:50] mtred: 4,480,869
[23:23:50] nofeemining: 18,380
[23:23:50] RPC request [e83d3000] submitted to triplemining.com
Caught, jsonrpc_call insides
'user'
Caught, jsonrpc_call insides
'user'
...
and so on
triplemining just went nuts for me
api_key:-->([ 0-9]+)
api_strip:' '
doesnt work for it anymore.
api_key:-->([ 0-9]+)
api_strip:' '
doesnt work for it anymore.
1) Pool API Errors?
Well I think we crashed poolmonkey or triggered DDOS protections. I'm going to raise the lower limit from once every 10 seconds to once every 30.
2)Btcworld is added for hopping. bitp.it is added as a backup.
I can't get a translation of the x8s thread to work.
3)differences between this and flexible miner proxy?
This one hops. Oh and it changes servers in the case of server death etc... We also have LP support
I know they have support for individual worker statistics which we don't have yet.
Well I think we crashed poolmonkey or triggered DDOS protections. I'm going to raise the lower limit from once every 10 seconds to once every 30.
2)Btcworld is added for hopping. bitp.it is added as a backup.
I can't get a translation of the x8s thread to work.
3)differences between this and flexible miner proxy?
This one hops. Oh and it changes servers in the case of server death etc... We also have LP support
I know they have support for individual worker statistics which we don't have yet.
How does this proxy differ from the Flexible Mining Proxy: https://forum.bitcoin.org/index.php?topic=5506.0
I'm currently using that one and it works well. Not sure if they are for the exact same purpose though. Could I run both to get pool H/A and pool hopping? Hmmm... sort of not sure what the differences are between the two apps.
I'm currently using that one and it works well. Not sure if they are for the exact same purpose though. Could I run both to get pool H/A and pool hopping? Hmmm... sort of not sure what the differences are between the two apps.
Jump to: