Prohashing Mining Pool Forums

This weekend was spent improving stability and performance, as we expect next weekend to be spent as well. We won't be moving onto SHA-256 mining until almost all of the known issues are resolved.

• A release is planned to be issued this afternoon. There may be problems at first, but we plan for it to be the only one this week.
• The first change was that we reduced the startup time of the mining server from 15 minutes to about 8 seconds. Previously, coins were queried serially at startup to compute profitability. This was fine before when there were few coins, but now the system mines hundreds of coins. With this release, they are computed in parallel. If bugs need to be fixed in the future, it will be far quicker to get the server back online after making changes, resulting in less downtime.
• There were some merge mined coins that support only getauxblock, and do not support getblocktemplate, and these coins often had orphaned blocks. We modified the server to receive getauxblock responses from these daemons so that profitability will be increased 1% by merge mining more coins.
• Bittrex trading was in error for months after they upgraded their servers to a newer version of SSL. We finally figured out a fix for how to connect with their system. Chris expects profitability to increase by 2% because more coins will be able to be mined.
• The program that inserts shares into the database previously operated synchronously, which was fine when the number of shares to be inserted was low. Now, there are so many shares that WAMP requests are delayed up to 2s when database inserts occur. We modified this program to insert to the database asynchronously, so that WAMP requests can be serviced in real-time. The upgrade will also prevent the mining server from running out of memory from queued shares during periods of high database load, as occurred on Friday.
• Deprecated API functions were removed from the website to cause immediate errors instead of querying the database and then returning an error.

Is it safe to say come late May early June we will have sha256d?
Is it even profitable to mine said cyrpto now with btc being so unbearable with fees?

SHA-256d coins have no connection to the Bitcoin transaction fees. The great thing about this pool is that you don't need to earn bitcoin and pay the fees to get your earnings. How much more profitable than bitcoin will the SHA-256d pool be? I don't know.

GregoryGHarding wrote:Is it safe to say come late May early June we will have sha256d?
Is it even profitable to mine said cyrpto now with btc being so unbearable with fees?

No. Chris plans to install the servers to support SHA-256 mining on May 26, but it's going to take at least two weeks just to install the 175 coins after that - and that assumes that the new servers work great and there are no problems with their hardware.

Independence Day is a more reasonable estimate. But keep in mind that our top priority right now is resolving mining server bugs, improving performance, and increasing reliability. Every time one of these balance issues happens, we need to investigate the cause and make sure that it won't occur again.

When we can get the server running for a week without any restarts or corrections, then we will have achieved our goal and will be able to move on.

Steve Sokolowski wrote:

GregoryGHarding wrote:Is it safe to say come late May early June we will have sha256d?
Is it even profitable to mine said cyrpto now with btc being so unbearable with fees?

No. Chris plans to install the servers to support SHA-256 mining on May 26, but it's going to take at least two weeks just to install the 175 coins after that - and that assumes that the new servers work great and there are no problems with their hardware.

Independence Day is a more reasonable estimate. But keep in mind that our top priority right now is resolving mining server bugs, improving performance, and increasing reliability. Every time one of these balance issues happens, we need to investigate the cause and make sure that it won't occur again.

When we can get the server running for a week without any restarts or corrections, then we will have achieved our goal and will be able to move on.

sounds great! thanks