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.
-
Steve Sokolowski
- Posts: 4585
- Joined: Wed Aug 27, 2014 3:27 pm
- Location: State College, PA
Post
by Steve Sokolowski » Wed Sep 24, 2014 8:44 am
Here's the current status of the project as of today:
- Chris continues to test the next release of the project. Two major issues were identified and resolved so far. Hopefully, he will fully validate the changes before Friday, so that we can issue a deployment on Saturday morning. We only want to perform deployments on Saturdays because that gives the maximum amount of time to fix something if it does wrong.
- While the site is ready for marketing, no time has been put into it and the existing marketing has been largely ineffective. We contacted Kristof about it, but he's busy and hasn't had a chance to reply. We need to locate someone who can deal with business and legal matters who has less experience in that area (since although people like Kristof are perfect, they can't do it). We need to be able to continue to focus on the technical work.
Here are the new features in the next release:
- The ability to ignore Coinwarz's data for specific coins, since their data is not always correct.
- The backend infrastructure for multiple exchange support, although multiple exchanges won't actually be enabled.
- An option to pay coins below the payout threshold, at the cost of the transaction fee.
- The ability to hide usernames in the "found blocks" table, at jimlite's request.
- A more accurate BTC per day reading on the top bar of the site; the current reading takes the dollar earnings and converts them to BTC, which makes the pool appear to be less profitable on days that BTC value increases and the other way around.
- An option to reduce the number of blocks required until mined blocks reach maturity on a per-coin basis, to reduce slippage so that mined coins can be sold faster than 120 blocks when possible.
- A new 19th error condition that disables a coin when the last 30 blocks average twice as profitable than the second most profitable coin's last 30 blocks, as another way of detecting forks.
Finally, in other news, we got our upload bandwidth increased from 65Mbps to 150Mbps at no cost. We're not using anywhere close to that, but hopefully it will be useful in the future.
