eltito
Active member
In the interest of improving communication with the Darkcoin community, we’ve created a new ‘Announcements’ sub-forum at darkcointalk.org. Though permissions to create threads on this sub-forum will be limited to certain key members, anyone is welcome to comment and offer their feedback. Moving forward, it is our intention to disseminate important information from this sub-forum, linking back to it from our various social media presences and other appropriate outlets.
We understand the frustration that several users have expressed in the last few days regarding the lack of new information coming from the development team. Please consider this a step toward addressing the cause of that frustration.
Rest assured that there are some very important things going on behind the scenes. Some of these things are absolutely unique ideas and solutions that, up to now, have not existed in the cryptocurrency community. The development team has, understandably, been hesitant to offer specific details on these features in order to protect Darkcoin’s significant first-mover advantage and reputation for innovation. To put it more directly: we’d prefer to be the first coin to implement our own unique ideas and innovations.
A few people have asked for a more precise look at what RC3 included. Here is the official word:
Implemented with RC3:
Looking ahead...
In the works for RC4:
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.
For a number of reasons, including time demands on the developers following the infiltration of the official mining pool and the fact that extensive changes and optimizations are being written into the Masternode payout election protocol, we expect RC4 to come online sometime in late July.
In regards to Masternode payment enforcement: There have been some talks with Evan about the possibility of implementing code to blacklist pools which haven’t updated. Though it would certainly be possible, such an implementation would significantly detract from the time he requires to implement the actual fix. We believe his time is better spent creating a permanent fix.
In the meantime, we will endeavor to produce a white list of known good pools as soon as possible, and we will continue to ‘out’ known bad actors as best we can. This is where the community can make a significant contribution. Please check out GhostPlayer’s (aka Yidakee) thread here: goo.gl/lD1FGh
As was mentioned yesterday on the bitcointalk thread, there are some very exciting and important things on the table for Darkcoin. We’re in a bit of a lull at the moment, and we’ll be looking at ways to keep the community engaged until some of the inevitable fireworks start up again.
The best is yet to come.
Thanks,
The Darkcoin Team
Addendum: To be clear, the question on everyone's mind in regards to the Masternode enforcement mechanism built into RC3 is, "Why don't we just flip the switch?" The answer is that RC3's enforcement mechanism has caused issues on the network twice now. Knowing that, enabling it a third time in its current state because we're annoyed by some non-paying pools would be quite irresponsible. Instead, Evan has chosen to build a simpler, safer, new enforcement mechanism, to be implemented with RC4. --Chris Rimoldi (eltito)
We understand the frustration that several users have expressed in the last few days regarding the lack of new information coming from the development team. Please consider this a step toward addressing the cause of that frustration.
Rest assured that there are some very important things going on behind the scenes. Some of these things are absolutely unique ideas and solutions that, up to now, have not existed in the cryptocurrency community. The development team has, understandably, been hesitant to offer specific details on these features in order to protect Darkcoin’s significant first-mover advantage and reputation for innovation. To put it more directly: we’d prefer to be the first coin to implement our own unique ideas and innovations.
A few people have asked for a more precise look at what RC3 included. Here is the official word:
Implemented with RC3:
- Added ‘sporking’ logic to turn on/off enforcement of hard forks
- Fixed Masternode ‘ghost’ issues where Masternodes appeared online, but were not
- Added cold/hot Masternode setup for secure, offline storage of funds
- Optimized Masternode communications traffic (removed spam)
Looking ahead...
In the works for RC4:
- Removal of Masternode payment votes in blockchain
- Addition of Masternode voting consensus system
- Live ‘spork’ for enforcing consensus system
- Anonymity enhancements
- For a more detailed explanation of the changes to the Masternode consensus protocol, please check out the “New Enforcement Strategy” section in this article: goo.gl/pDG9W3
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.
For a number of reasons, including time demands on the developers following the infiltration of the official mining pool and the fact that extensive changes and optimizations are being written into the Masternode payout election protocol, we expect RC4 to come online sometime in late July.
In regards to Masternode payment enforcement: There have been some talks with Evan about the possibility of implementing code to blacklist pools which haven’t updated. Though it would certainly be possible, such an implementation would significantly detract from the time he requires to implement the actual fix. We believe his time is better spent creating a permanent fix.
In the meantime, we will endeavor to produce a white list of known good pools as soon as possible, and we will continue to ‘out’ known bad actors as best we can. This is where the community can make a significant contribution. Please check out GhostPlayer’s (aka Yidakee) thread here: goo.gl/lD1FGh
As was mentioned yesterday on the bitcointalk thread, there are some very exciting and important things on the table for Darkcoin. We’re in a bit of a lull at the moment, and we’ll be looking at ways to keep the community engaged until some of the inevitable fireworks start up again.
The best is yet to come.
Thanks,
The Darkcoin Team
Addendum: To be clear, the question on everyone's mind in regards to the Masternode enforcement mechanism built into RC3 is, "Why don't we just flip the switch?" The answer is that RC3's enforcement mechanism has caused issues on the network twice now. Knowing that, enabling it a third time in its current state because we're annoyed by some non-paying pools would be quite irresponsible. Instead, Evan has chosen to build a simpler, safer, new enforcement mechanism, to be implemented with RC4. --Chris Rimoldi (eltito)
Last edited by a moderator:
