The question on everyone’s mind is what is the team’s plan for STRAKS?
It’s important to remind everyone STRAKS is an open source project, and anyone is able to contribute to the STRAKS blockchain tools.
We strongly encourage you to leave your comments below. Nothing! is set in stone. We truly want to get feedback from the community. After enough time for collecting comments has passed we will use those to help formalize a specific direction.
We are working on implementing lyra2rev3 as an interim POW solution for testnet. We understand this is a short term solution and may not be the best route. The best solution for the interim is to come up with our own variant that is not implemented by any other coin to minimize the impact of hashrate fluctations on block generation time caused by multi-coin profit switching. However, there would be a lot more work required to implement our own POW algo. Since that would also require mining software support.
Long-term we are evaluating HyperLedger. HyperLedger has many features that would directly support the long-term vision of the STRAKS project as outlined in Squb’s memo that was published November 2018. We will release more details as to why we feel HyperLedger is a good fit for the STRAKS Project in another post in the next few weeks.
Block generation, block times, and stalled network issues. Anyone who has read the STRAKS core details is likely wondering why the blockchain has been struggling to maintain an average of 60 second block generation. We selected the D106 difficulty algorithm due to its dynamic difficulty adjustment in short time-frames. At the time of its selection it had been tested and proven to maintain an average of 60 second block times with hashrate variations of up to 40x average levels. In layman’s terms if the average hashrate on the network was averaging 20 GH/s the difficulty methodology could easily handle up to 800 GH/s mining of STRAKS in bursts without adversely affecting the average block time in a given timeframe. However, since the release of ASICS, and combined with the impact of multi-coin profit mining pools bringing upwards of 1.5 TH/s to the blockchain, when the average hashrate is at times only 8-10 GH/s causes the difficulty to spike to such a level that it can take a few hours for the next block to be generated at which point the difficulty will only fall by 1/4. thereby requiring 2 or 3 blocks before block generation times will decrease. Which then in turn often triggers the multi-coin pools to jump back onto the project. creating a never-ending cycle of fast block generation and then a stall.