If anyone has feelings about json rpc calls they want in the client, speak now
I'm thinking:
list_addresses, getfresh, send, broadcast, getbalance <optional address>
@Fireduck use the median interval of the last 10 shares for difficulty ramping instead of a rolling average?
Probably smart
Really I hacked that MrPlow together in a day or so
I was hoping someone else would make improvements for me
i'd even peg it at the median of the past 100 share intervals, but i'm patient like that
if i'll touch it i'll most likely just attack the thread autotuning stuff
also just kill the solo miner at this point?
even something like 10Mh/s would not be viable to solo
I'd be inclined to leave the solo code there but not include it in release zip
seems fair if the codebase is mostly shared and there is no major engineering around also keeping the solo worker
the pool stats stuff is weird: ``` INFO: Mining rate: 5-min: 503.316K/s, 15-min: 1.091M/s, hour: 827.210K/s INFO: Mining rate: 0.000/sec - at this rate ∞ hours per block ```
i suppose the latter is based on actual blocks found and the first one on the shares * weight received?
It is just diff math based on 15 second rate and block difficulty
oh, so with less than 4+ miners (or probably less than 10+ miners) it cannot even
the data just falls through the sample window
Correct. It is dumb.
naw, that's fine
what is dumb is running a pool with practically zero miners on it
so things being flaky on the low end is quite acceptable
it was really a case of copying code from the solo miner and not adjusting it :wink: