1) Slush's servers seem to suck... But I'm only getting around 5% rejects when the api is up. And I'm getting it switching at around 10%.
But older versions have multiple bugs with regards to this behavior. Including switching at 160%
|
|
|
1) Slush. Is it working? It should switch at 10%. There may be a bug...
2) gngadget? Thanks.
3) everyone one else who has sent me donations: Thanks.
|
|
|
See if turning off LP fixes it. client4320 is in minerutils/something. Its one of the folders. And it is only used in longpolling. I hope.
|
|
|
beef: I think I identified a potential problem. And I fixed flowers website to properly start api info running. However I think the most likely explanation is you dropped role in a pool description...
|
|
|
The configuration in the trunk for polmine works...
|
|
|
Its back up but the polish and american polmine are giving different numbers...
Polish claims it just found a block though.
EDIT: Its all good. The english site just lags by about 2-3 minutes.
|
|
|
1)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.
|
|
|
The website was getting slow then it sped up... I didn't get a api_disable though.
|
|
|
I'm considering disabling them. The website is already noticeably slower... And I haven't even mined on them yet.
|
|
|
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.
|
|
|
total pool shares are shown in the html... They might not be shown for mine_slush and mine_nmc. I'll check and fix it.
|
|
|
I disabled nofee because I was getting spoofed api stats from them.
Does bitclockers work? I can reenable them.
|
|
|
1) Api connection issues. I'll put in a hack so that it will switch after the second time. EDIT: Done.
2)bitcoind integration? This means that if you label your addresses correctly it'll move the payments over into the database for you. No manual updating required.
EDIT: I'm probably going to do worker tracking first.
|
|
|
Has anyone noticed a memory leak with phoenix? I seem to be getting roughly 27% of memory usage after two days of running it.
|
|
|
1) Calm down api? Yeah. I can make it not set the shares to 10,000 but if an api goes down then that pool will hover at its current share level and may result in people mining it for way to long. Or i could make the api_disable work but then the pool will get api_disable if its shares are static/the website is down for to long.I could add an api delagger to solve that problem.
But the question is: rewrite of api system or bitcoind integration?
2) Are bitclockers and triple still using a hoppable algorithms? If they are i'll reenable them by default.
|
|
|
1)beef errors wtih stats.py? Yeah turning on bitclockers screwed things up. Its fixed in the latest version.
2) mine_slush? I thik I accidentally made it jump at 1.6 instead of .1. Oops. I'll fix that.
|
|
|
rampone: Red means it lagged out. Are you sure you didn't accientally change the api_address?
|
|
|
mtred should work by default. Are you using the latest version? Oh and mine_nmc and mine_slush are added.
Shares are stored in database as difficulty stamped (and once i add workers, difficulty and worker stamped). I'm not sure if the network code is taking that into account or if we serve the data like that. I should just serve an expected for each server. I'll take a look.
|
|
|
Custom difficulty cutoffs? Yeah. That would be pretty quick. I'll add it in. use mine_slush as role for a 10% cutoff.
|
|
|
|