Post
Topic
Board Announcements (Altcoins)
Re: |ANN| DAS - Decentralized and Secure. Private Send. Masternodes.
by
crypto_patriot
on 18/09/2017, 00:44:02 UTC
Re: mining, difficulty algo and rewards

a.) the difficulty algo needs to be fixed with a "x" block lookback WITH TTF taken into account to balance an average TTF of 2.5 mins regardless of hashrate for the life of DAS mining until max coin achieved. *edit* If difficulty rises over time and reaches new ranges (which it is apparently doing), more hashpower is needed to continue the blockchain progression to keep things moving. A masternode network is useless unless there is a constant progression of the blockchain.
b.) The current difficulty algo is NOT working. Was something changed from the original DGWv3? It is supposed to prevent exactly what is happening. Have you looked at MIDAS? (an alternative to DGW when looking to upgrade the Kimoto's Gravity Well (KGW) limitations)
c.) The current mining block rewards is NOT working as spec'd. Was something changed from the original default? (I have the #'s to prove the calc is WRONG)
d.) HIGH difficulty blocks (harder to solve, more time, more hashrate, more cost) SHOULD be rewarded with higher block rewards. LOW difficulty blocks (easy to solve; lower cost/hashrate) should have LOWER rewards. Doesn't this make sense? It seems something is inverted somewhere in the code.
e.) IF the algos worked as they were intended and some MINOR adjustments were made, this will balance out the mining, create equitable rewards, keep the blockchain consistently timed for transactions and confirmations (reliability), create regular expected MN rewards like clockwork and prevent huge hashrate mega autoswitching x11 multipools from even getting interested in DAS to exploit EXACTLY these problems to their profit.

*edit*But ALL of this is addressed in your DAS whitepaper, right? (It SHOULD have been....) Also, just because the code works without errors (from a coding standpoint) doesn't necessarily means the output of the code is as was intended. That's what testnets and verification and calculation of all outputs compared to intended algorithm and specs are for and is what should have been done before any ANN or sale of DAS. I wasn't around at that time, but I AM analysing the outputs compared to your documented specs in the ANN. And diving into the mining this past week was a real eye-opener on what has been going on with DAS and all it's problems recently.

Truckman: THIS IS YOUR JOB TO FIX. Really, bro. IF you really don't understand nor know how to fix it: GET HELP! We can help identify problems and come up with various solutions, but it is YOUR RESPONSIBILITY and OBLIGATION as the SOLE dev (holding approx 25% of all created DAS to date) to fix it. You have premine to contract freelance coders and if you need help in the process, ASK. Sooner rather than later or they may be no DAS to fix. :\

I have been willing to help you with technicals for 6+ weeks but you choose to ignore it or just do not care and minimize what is wrong and what needs to be done. I may not be around much longer to help you nor the DAS community unless you ACT NOW. Thank you.

Things are very off kilter and it is currently detrimental to the future and success of DAS.

Regards,

c_p