Prohashing Mining Pool Forums

Good morning!

• We'll be doing a major release today to prepare for parallel mining servers, and to replace Novaexchange with livecoin.net. The release is scheduled to start in 2-3h.
• The code to handle parallel mining servers is feature-complete, so we are actually going to release what could be the final code to a single instance today. However, I have only tested it working with one instance, so we can't yet spin up multiple servers without further testing. The reason we want to get this version out is because there are issues present in the current version of the mining server that cause share corrections. Another major reason is because Wednesday will see the conclusion of our current commitments and the hiring of new staff, so this release needs to be out of the way before then.
• The main reason we are not reopening registrations right now is the support tickets, rather than being unable to rush the parallel servers release. The number of tickets was reduced from 210 to 60 over the past two days, so we made a lot of progress. However, until we can figure out how to get a better handle on the tickets, we can't take on more customers. The biggest problem is that the tickets from bugs (which affect one person) take away time from fixing the bugs (which affect every person), and we can never get around to actually fixing the issues that would prevent the tickets permanently. Suggestions are welcome. Maybe someone can figure out some way to prioritize the tickets without making the customers who are assigned the lower priority angry. Something needs to be done, because while every person's problem is important, it takes almost as much time to solve a few individual problems as it does to permanently fix the problem for many people who didn't complain at all.

Hello,

You could publish the table(s) of the bugs/improvement requests, register users could up/doan vote them , similar to what Slushpool do in their development corner (https://slushpool.com/devcorner/).

For the bugs you could have a column of the % of affected customers, so if you submit one that only affect you, you could see it there with 0.0001% share you can just half self pitty and be pacient.

Please add earnings by algo or per machine. maybe make password argument to separate machines into separate earnings tables.