Status as of Monday, June 5, 2017

Discussion of development releases of Prohashing / Requests for features
Forum rules
The Development forum is for discussion of development releases of Prohashing and for feedback on the site, requests for features, etc.

While we can't promise we will be able to implement every feature request, we will give them each due consideration and do our best with the resources and staffing we have available.

For the full list of PROHASHING forums rules, please visit https://prohashing.com/help/prohashing- ... rms-forums.
Post Reply
User avatar
Steve Sokolowski
Posts: 4585
Joined: Wed Aug 27, 2014 3:27 pm
Location: State College, PA

Status as of Monday, June 5, 2017

Post by Steve Sokolowski » Mon Jun 05, 2017 8:08 am

We have a new bugfix and oversight release which will be put out when testing is completed shortly. Here's what's in it:
  • The charts on the homepage which are currently reading "No data is able to be displayed" have been repaired. The cause of the problem was a race condition that was reintroduced in the last release.
  • Michael appears to have completed two-factor authentication.
  • The WAMP data that can be delayed will now include "server_timestamp" and "data_timestamp" to allow users to determine when it is live and when it is delayed, and to react accordingly.
  • There are performance improvements in the mining server to reduce memory usage from 1.5GB to about 100MB, which will increase the amount of data that can be held in the processor cache and therefore improve performance.
  • The mining server will now be able to start up in a few seconds, rather than after 15 minutes, because Chris optimized the query that determines the orphan rates of all coins.
  • The WAMP API will have a new "f_all_balance_updates" function that allows miners to obtain the initial balances of their accounts.
  • I implemented the new WAMP API feature on the website and deleted a lot of REST endpoints that were no longer being used, some of which were being pummeled with requests from bots for an unknown reason.
Other tasks I did this weekend include changing passwords for a number of auxiliary services like facebook and Verizon Wireless to improve security, and working with a customer who is implementing a script to save Chris 3 hours per week of tedious exchange coin checking.

The release is being tested and we hope to get it out today, but if two factor authentication needs more work, then we'll delay until tomorrow or Wednesday.
Top
Post Reply

Return to “Development Discussion and Feedback”