Page 1 of 1

Status as of Thursday, January 4, 2018

Posted: Thu Jan 04, 2018 10:22 am
by Steve Sokolowski
Good morning!

Now that we've proven that half of our customers weren't going to disappear once we started the tax compliance things, we are able to move forward with spending money to continue to fix issues and improve support. A few customers asked in the forums, so below I'm going to list some things that are coming up.

High priority items - this week
  • Expand the found blocks so that they display the last 35 days of blocks, instead of the last 12 hours. Constance was able to add in the performance improvements necessary to accomplish this. Then, we're going to wait a few days and see whether tickets continue to appear stating that blocks are not being paid to solo miners, or whether the tickets were being generated because old blocks have fallen off the list.
  • Enable bitcoin payouts through Coinbase with no fees, to resolve the many tickets from customers who aren't aware of the expense of using the bitcoin network.
Medium priority items - Sunday and next week
  • Post flyers to begin the hiring process of a student to provide tier 1 support.
  • Investigate the multiple issues reported by JiveTonto, regarding blocks that are duplicating height, as well as two other problems he reported that may also have been encountered by other customers
  • Hire an accounting firm to take tax preparation off of Chris's tasklist so that he can focus on the important technical stuff
Lower priority items
  • Hire someone to get maintenance tasks like updating coins, the development tools, and things like paying bills and health insurance documentation off of Chris's tasklist so that he can focus on moving forward with the technical tasks.
  • Once Chris is relieved from this other stuff, allow him to get back to adding new exchanges and payout coins to improve profitability.
  • In March, when the Enterprise-class Internet connection is installed, convert the system over to the new connection to improve the network connectivity issues.
Unfortunately, there are so many bugs and tickets that we still don't see a path to SHA-256 mining yet. We hope to get there soon, but the system needs to be more stable and we need to be able to train staff to get Chris out of the mess of administrative tasks he's buried in right now. Once we can get Chris actually able to move forward again, then he'll be able to quickly implement features that customers have been requesting.