Status as of Monday, April 30, 2018

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.
Locked
User avatar
Steve Sokolowski
Posts: 4585
Joined: Wed Aug 27, 2014 3:27 pm
Location: State College, PA

Status as of Monday, April 30, 2018

Post by Steve Sokolowski » Mon Apr 30, 2018 3:49 pm

Good afternoon!
  • We are issuing a new mining server release this afternoon, and will release another one tomorrow. We discovered a flaw in how the parallel mining servers work. When a block is found by one of the mining servers, it is sent to the daemon. Then, once the daemon has finished processing the block, the next block is sent to all servers. However, if the coin being mined is very easy, the amount of time the daemon is processing the blocks becomes significant, and during that time, the other servers (which don't know about the block that one server has found) continue to credit miners with shares. With this release, the system will immediately mark the block as stale across all mining servers before even sending it to the daemon, so that no miners at the other servers are credited for shares that one of the servers already knows are stale.
  • We also discovered that some types of errors, like when a daemon has a large number of rejected blocks in a row, were not being sent across all mining servers, which meant that the other servers continued to mine the coins despite one server knowing that the coin's blocks would never be accepted. Now, all servers will be in the same state, ensuring that money isn't wasted by the other servers until every one finds the same block and hits the same error.
  • There are a few more of these issues that I'll be working on tomorrow. The goal is to get the mining servers into as much of the same state as possible, and then to make sure that profitability becomes more uniform and less disturbed by random circumstances between the servers.
  • Chris has been hard at work adding and updating coins to improve profitability, now that we support more exchanges. When Novaexchange returns, we expect to be able to add another 90 coins.
ZiGen
Posts: 64
Joined: Wed Oct 04, 2017 7:29 pm

Re: Status as of Monday, April 30, 2018

Post by ZiGen » Mon Apr 30, 2018 11:53 pm

Are you serious ???
User avatar
Steve Sokolowski
Posts: 4585
Joined: Wed Aug 27, 2014 3:27 pm
Location: State College, PA

Re: Status as of Monday, April 30, 2018

Post by Steve Sokolowski » Tue May 01, 2018 9:47 am

ZiGen wrote:Are you serious ???
Could you elaborate more?

I hate to delete this post, but this is the type of post that could be considered by some to be "low effort." We want all posts to contribute some new ideas to the forum.
ZiGen
Posts: 64
Joined: Wed Oct 04, 2017 7:29 pm

Re: Status as of Monday, April 30, 2018

Post by ZiGen » Wed May 02, 2018 1:47 pm

When the NEW block is found ...the daemon FIRST job is to communicate THIS FACT to the rest of the crypto network ...It's called "synchronization" ...consensus algorithm ...You could continue from here ...To long to explain ...and I am sure that you know that already ...Just wandering about your last post ...
Locked