 Show Posts
|
|
Pages: « 1 2 [3] 4 »
|
Try #[btcserv.net]
#name: btcserv
#mine_address: btcserv.net:8335
#api_address: https://btcserv.net/pool/round-stats/
#api_method: re
#api_key: ([,0-9]+)\s+shares
#api_strip: ','
#url: https://btcserv.net/user/stats/
edit: shortened api_key |
|
|
|
Error in pool api for btcg Get this for BTC Guild even if it's added as backup, and bithopper doesn't hop to BTCG when there's no other pools available. Is there an easy way to fix this? |
|
|
|
run with --debug like c00w said xxx@yyy:~/bitHopper$ python bitHopper.py --debug and post output here or in pastebin ------------------------------------ xxx@yyy:~/bitHopper$ python bitHopper.py --debug [15:14:48] Updating Difficulty [15:14:48] 1690895.8030524 [15:14:48] Updating NameCoin Difficulty [15:14:49] 94037.96 Traceback (most recent call last): File "bitHopper.py", line 227, in <module> bithopper_global = BitHopper() File "bitHopper.py", line 43, in __init__ self.pool = pool.Pool(self) File "/home/xxx/bitHopper/pool.py", line 33, in __init__ self.servers[pool]['default_role'] = self.servers[pool]['role'] KeyError: 'role' ------------------------------------ its always the same (and I have done the latest git pull...)  Something else that c00w said: Errors with role:
Um check you pool.cfg and make sure very pool has its role specified. Thats the error. Some pool doesn't have a role. |
|
|
|
My guess is that pool op did some maintenance. I had no updates on shares for about an hour, but things look fine now. Also after the no-update period the invalid block has been removed from unconfirmed balance..
MtRed had an invalid block too? Thats like the third invalid block in the last couple of days for the various pools I mine. This was an invalid block from 5-6 days (?) ago, that stayed in the unconfirmed payout.. Edit: Invalid block was from 2011-07-21 |
|
|
|
Also had Mt.Red Api disabled. Restart fixed it.
seems like mtred slowed down their api update  My guess is that pool op did some maintenance. I had no updates on shares for about an hour, but things look fine now. Also after the no-update period the invalid block has been removed from unconfirmed balance.. |
|
|
|
+1 for pixmania Also I would like to show support for cdjapan and/or yesasia |
|
|
|
Bithopping increases difficulty.
So it does work for you for a short period...
Care to elaborate? |
|
|
|
Do I need to restart script after difficulty is changed?
No bitHopper checks for difficulty every 6 hrs (and on startup). Restarting will force the change immediately, but with a few hours patience it will update automatically |
|
|
|
So which Pools would you recommend right now??
Mine: Ozco, Mt Red, Nofee, TripleM, Polmine, bclc (I'm probably pretty much alone on this one). Backup: bitp.it and ArsB Any way to add deppbit?
See 4 posts up |
|
|
|
[18:39:28] Error in pool api for ozco
[18:59:11] Error in user api for btcg
[18:59:11] Error in pool api for arsbitcoin
[18:59:11] Error in pool api for btcg
[18:59:11] Error in pool api for bclc
[18:59:11] Error in pool api for eligius
How can I fix this?
My config below..
BTCG doesn't have pool-shares in the api anymore, hence it defaults as disabled. If you want to use BTCG use it as backup. Eligius and ArsB are both *PPS, no api key defined, hence trying to look any information up will fail. ozco I don't see any problems with, except you have commented it out, so it shouldn't report anything at all.. |
|
|
|
is namecoin mining dead at this point?
I notice that role:disable is being used now in latest c00w pool.cfg.
With the current exchange rates, I'd say yes. Had nmc-mining enabled (bitparking) for ~18 hrs, and while my efficiency in terms of NMC was 135%, after exchange to BTC it came out to 65% |
|
|
|
Looks like polmine just went live with a new website. I think regex is broken.
[polmine]
name: Polmine
mine_address: polmine.pl:8347
api_address:https://polmine.pl/?action=statistics
role:mine
api_method:re
api_key: szystkich: </b> <br/>([ 0-9]+)<br/>
api_strip:' ' |
|
|
|
something is wrong with donation, I can't change that % that was entered during sign-up
Works fine for me. jkminkov, did you remember to enter the authorize pin? |
|
|
|
why just one backup? and which is it? It'd be good to do a poll and backups - which and why.
Why just 1? Because I in 3 days got 5 shares on my 2ndary backup pool. Ddin't seem worth it to have fractions of bitcents on yet a pool. Which is it? ArsBitcoin, which as things look now will probably be the pool I switch to full time should hopping become obsolete. |
|
|
|
Just to be sure. When I disable the backup pool it means that no new work will be pushed if there isn't a pool that's good to hop onto? Or does it mean it will stick using the last one or something like that?
you're only using one backup pool? Or you want to disable all backups for some reason? I think it will just go to the pool with the smallest total shares, even if they're above the cut off point. Correct. I run with just 1 backup pool, and if that fails it switches to the pool with the lowest share count, even if it's above the limit. |
|
|
|
|
Hopping is as ethical as shopping several places for your groceries to get the best prices.
I can chose to shop all my groceries in one place, or go several places to pick the best offers.
Am I cheating or stealing from my local grocery shop? No.
It's more work to shop several places, as it's more work to update/maintain the hopping proxy (another downside is having your earnings spread across a number of pools).
But as long as there's pool operators willing to pay me more for mining with them than the alternatives, I'll point my miner to them.
Edit: Am I cheating/stealing from other miners? No. They are free to make the same decisions that I have. Mine one pool for convenience, or hop around for profit.
|
|
|
|
json isn't applicable as [] are used instead of {}
json IS capable of [] - its just an array. index 1 is round shares (for me json.loads works) my bad. Got an pool api error when I tried the json approach. |
|
|
|
[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 {} |
|
|
|
[btcworld]
name: BTC World
mine_address: btcworld.de:8332
api_address:http://btcworld.de/statistics
role:info
api_method:re
api_key:Verifizierte\s+Anteile\s+der\s+aktuellen\s+Runde:</th><td>([0-9]+(,[0-9]+)*)
api_strip:','
#CHANGE THIS
#http://btcworld.de/signup
user: user
pass: x Working. I'm a stupid stupid man, as I manually set language to English in my browser, but the webpage defaults to German... |
|
|
|
[btcworld]
name: BTC World
mine_address: btcworld.de:8332
api_address:http://btcworld.de/statistics
role:info
api_method:re
api_key:Valid\s+shares\s+for\s+current\s+round:</th><td>([0-9]+(,[0-9]+)*)
api_strip:','
#CHANGE THIS
#http://btcworld.de/signup
user: user
pass: x This works just fine when I run it through the steps (selectSharesResponse) in python cmd line, but not when I run it "live". |
|
|
|
|
