BelStar
Member
I believe now is a critical time to look back at the past months and carefully consider options for the future of Darkcoin. While there still is a core group of people living in the "Cult of Evan" I am starting to think that DRK is in trouble. Talk about cognitive dissonance.
The initial hype is gone and the next step should be real-world adoption. While DRK has been a flagship and an incubator of the most creative ideas in crypto over the past months the implementation is severely lacking. In the current context it is hard to imagine it will ever really "work" and not be some kind of gimmick.
Based on information found on this forum, on the official DRK Jira, and on the IRC channel, I have considered several critical points that got me doubting the future of DRK:
Taking all the above-mentioned points that I have tried to describe as objectively as possible in the interest of Darkcoin, are we really ready to opensource RC5 and expose these blatant weaknesses? Are we really intending to kill DRK?
The initial hype is gone and the next step should be real-world adoption. While DRK has been a flagship and an incubator of the most creative ideas in crypto over the past months the implementation is severely lacking. In the current context it is hard to imagine it will ever really "work" and not be some kind of gimmick.
Based on information found on this forum, on the official DRK Jira, and on the IRC channel, I have considered several critical points that got me doubting the future of DRK:
- Team work: although several people have been added to the dev team and have done a great job, Evan remains a bottleneck and single point of failure. This has concretely translated into consecutive missed deadlines and botched releases to mainnet. flare is a great addition to the team and he tries to fulfill his role as best as he can but what to do when the lead dev does not follow the advice of the guy in charge of QA? Also, something has to be said about Evan not listening to the testing community pleading to have a stable product for a couple of days on testnet before releasing to mainnet. flare even drafted a testnet rollback & go-live plan that was purely and simply ignored. See https://darkcointalk.org/threads/closed-rc4-testing.1830/page-88#post-15693 , https://darkcointalk.org/threads/closed-rc4-testing.1830/page-88#post-15700 and https://darkcointalk.org/threads/closed-rc4-testing.1830/page-89#post-15710
- Technical solution: RC2 and RC3 where evident failures due to hard forks. RC4 is also a failure but a more discrete one as there was no hard fork. It was the release that could not fail... This said it is far from the "great success" that blinded supporters are promoting. A reflection of this is that the communication campaign mentioned by Eltito has never taken place (https://darkcointalk.org/threads/status-update-7-1-2014.1675/)
As we move into RC4, we will engage in a significantly more organized campaign to disseminate information than we have with any previous RC launch.
- Darksend is still not working correctly; it was a catastrophe after the RC4 release to mainnet and it is now working adequately under specific conditions but this is still insufficient for real-world use by lambda users. Only hardcore users dare to denominate their coins on mainnet. See examples at https://darkcointalk.org/threads/rc4-issues-bugs-feature-requests.2039/page-13#post-18249 and http://www.reddit.com/r/DRKCoin/comments/2f01r2/issues_with_the_lastest_version/
- The core of the solution (masternodes and payment of masternodes) is under heavy fire by no one else than Evan and flare. The payment system was considered flawed in RC3, hence the rework in RC4. One of the most fundamental components of DRK is still not stable... On Jira, Evan now candidly posts at http://jira.darkcoin.qa/browse/DRK-24?jql= :
It turns out the masternode voting system is over complicated and somewhat risky to the network, so I've removed it and am using the RC3 masternode payment system. This means we won't have enforcement, but it fixes all of these issues and removes the risk to the network.As for me, i am still searching for a new approach to make the payments more network intrinsic - MNs should actually mine their coins by proof of service, not rely on good acting miners to share their mined coins. If we can somehow create a model where miners (PoW) and masternodes (PoSVC) mine independently from each other, we will even have a solution for further payments for "DarkTor" relays and exit nodes. The current approach (divide PoW reward) seems not flexible enough to achieve this.
- No enforcement: enforcement of masternode payment was already promised in RC3 but quickly put aside due to hard fork risks. The spork alternative has been interesting but let's not fool ourselves, most masternode owners have been waiting for the possibility to enforce masternode payments for a long time, like vertoe. Most of us have the feeling that leaving things to the pools' generosity is a doubtful strategy. See http://jira.darkcoin.qa/browse/DRK-19?jql= and https://darkcointalk.org/threads/rc4-issues-bugs-feature-requests.2039/page-13#post-18199. Additionally, when asked what would be done about pools that decide not to pay masternodes Evan answered (https://darkcointalk.org/threads/closed-rc4-testing.1830/page-78#post-15352):
They'll update or we'll kick them off the network.
- For the first time, users are actually losing DRK due to corrupt wallets that even Evan is unable to salvage while the root cause remains unknown. See http://jira.darkcoin.qa/browse/DRK-27?jql= where Evan states:
Sorry, but this wallet is not recoverable. At some point during the darksend process, it looks like it was overwritten with invalid data and corrupted. It's missing transactions that happened, including you that contain the 571 darkcoin that are missing.
The debug information you sent was useful but it didn't contain the transactions in question (it doesn't go back far enough). So I wasn't able to tell what the root cause was. - Useability issues: the wallet redesign that could have improved the user experience and was initiated by DRKLord has been on hold for several days or weeks. Initially, supporters were hoping to see this redesign coincide with the RC4 release; it is now unclear whether it would even be considered for RC5. It is not mentioned by Evan in his August 19 development update. See https://darkcointalk.org/threads/development-update-august-19-2014.2086/ and https://darkcointalk.org/threads/enhanced-darkcoin-wallet-ui.1705/
Taking all the above-mentioned points that I have tried to describe as objectively as possible in the interest of Darkcoin, are we really ready to opensource RC5 and expose these blatant weaknesses? Are we really intending to kill DRK?
Last edited by a moderator: