[unitedminers]
name: unitedminers.com
mine_address: pool.unitedminers.com:8332
api_address: http://www.unitedminers.com/?action=statistics
api_method:re
api_key:Valid shares for current round:([,\d]+)
api_strip:','
role:mine
#CHANGE THIS
#unitedminers.com
user: workername
pass: workerpassword
yes we should. There can be a 2 - 5% difference (depending on total pool stale) and I'd rather get the numbers right.
Also I think everyone is very mean and horrible and cruel.
I also hope his server is immersed in mineral oil, or liquid nitrogen, or something.shouldn't we use the valid share count opposed to the total share count?Code:[unitedminers]
name: unitedminers.com
mine_address: pool.unitedminers.com:8332
api_address: http://www.unitedminers.com/?action=statistics
api_method:re
api_key:Valid shares for current round:([,\d]+)
api_strip:','
role:mine
#CHANGE THIS
#unitedminers.com
user: workername
pass: workerpassword
I guess so, but in the end there is a small difference between the twoshouldn't we use the valid share count opposed to the total share count?Code:[unitedminers]
name: unitedminers.com
mine_address: pool.unitedminers.com:8332
api_address: http://www.unitedminers.com/?action=statistics
api_method:re
api_key:Valid shares for current round:([,\d]+)
api_strip:','
role:mine
#CHANGE THIS
#unitedminers.com
user: workername
pass: workerpasswordlet's test the load balancing and redundancy
How does one enter the payout information in this new index.html?
i will add this (together with role changes)
this evening
for the time being you can just arrow your browser back, enter the payout info then hit refresh. worked fine as a hack.How does one enter the payout information in this new index.html?
i will add this (together with role changes)
this evening1)Payout info?
Um you don't. Flower is adding it soon or I'll add it once I get worker stuff going and the LP stuff as well.How does one enter the payout information in this new index.html?The website was getting slow then it sped up... I didn't get a api_disable though.got an api disabled with them.. i guess that means it was lagging?
and they only have 3 people mining right now
mtred is kicking ass today another block down.. 58 minutes
I'm considering disabling them. The website is already noticeably slower... And I haven't even mined on them yet.EDIT: Oh and I'm adding united miners. The frontpage gave me a lot of confidence in them. This should be funny.
Now that's just cruel...
@c00w: Yes please! Long poll timings will be the next step in hopping I hope (and will also shock a few "normal" miners about the bad performance of some pool backends!). A unix style timestamp with 3 places after the comma should be fine I guess...
Oh, and I'll most likely also need the time stamp of the most recent block on blockexplorer (as a comparison and to rule out blocks that were not found by any monitored pool) by checking http://blockexplorer.com/q/getblockcount and then requesting that number via http://blockexplorer.com/b/[blocknumbergoeshere]
The best thing to have then would be a delta between LongPoll_received and Block_found for each pool, sorted from lowest to highest.
Something like:
4.123 deepbit
4.512 uswest.btcguild
5.012 mtred
etc.sukrim: I can do that in the default bitHopper if you like.
Oh and I noticed polmine and already fixed it. And added slush. Tell me how it goes.
EDIT: Oh and I'm adding united miners. The frontpage gave me a lot of confidence in them. This should be funny.Jump to:
