Why do I get Invalid shares often? What are usual patterns getting those?
Invalid shares are
1) wrong calculated share (gpu calculation maybe wrong sometimes)
2) late share
if you didn't overclock GPU too much, your shares will be mostly late share.
When next block is found and changed, previous work jobs are invalid and treated like invalid shares.
profit info table api updates in 30min interval
Please could you update the API to provide live/regular stats and add the Date/Time that a block was found?
Just fall back to cached data if your server is overloaded/down.
1) live stat will harm multipoolminer because it will switch algo continually if there's no internal threshold
2) multipoolminer already made big ddos like traffic to server before and made things unresponsive.
Imagine 100000 miner rigs are all polling web server continually.
It's not running per one user, per rigs.
Polling massive amounts of rigs is far from ideal at all.
We should make some socket connecttion to get realtime api data if you really need realtime data.
I added "last_block" field at getminingandprofitsstatistics api as you requested.
It's unixtimestamp number.
thx for adding it, it's profitable thats why but do take note, most etn pools always get ddos from time to time. looking fwd to it n miners are ready to point to etn pool when it's ready.
thx for adding it, it's profitable thats why but do take note, most etn pools always get ddos from time to time. looking fwd to it n miners are ready to point to etn pool when it's ready.
ETN is a new kid on the block, another fork of Monero and, as far as I can see, it is quite profitable to mine at the moment.
Most, if not all, ETN pools have recently suffered from DDOS attacks and/or simply some poor pool configuration.
MPH should bear this in mind when opening up an ETN pool.
ETN thread:
https://bitcointalk.org/index.php?topic=2353282.1500Hmm.. I hate ddos.

Thank you for info.
I'll check deeply.