Re: [ANN][DRK] DarkCoin | First Anonymous Coin | First X11 | First DGW | DarkSend+ Is Live!
People here go from circle jerking to panic mode very fast. I don't see the problem 
.
It all depends on what Evan meant by that statement. I think we can all agree that no enforcement is very very problematic. Miners do not necessarily have to be sympathetic to DRK. Additionally, no enforcement would open up an attack vector on the Masternode network. Someone who doesn't like DRK can simply mine at a 20% advantage to everyone else, while undermining the system that lets DRK function. .There has to be enforcement. I suppose the advantage of the RC3 voting method is that is has been tried and tested so in that regards surely less risky to turn on?
Let's wait to hear from the captain..
+1
Moreover we use the soft-fork strategy since June (test then enforce)
https://darkcointalk.org/threads/rc3-relaunch-strategy-and-testing.1482/
Quote
The last couple of days I've been working on implementing the hashing algorithm for the last issues we had on the 20th and I've come up with a strategy that I think will much better suit us for launching the masternode payment system.
Instead I propose the following plan for launching RC3 in stages, which will be much safer and more stable:
We'll introduce an "enforcing" setting for masternode payments. This will be turned off at launch making it the equivalent of a soft fork, but will allow us to use the full infrastructure of the darkcoin network for testing. In the debug log, the system will complain when any issues arise and users can report such issues. After a period of time passes with no issues, we'll set a date to begin enforcing. At this time all issues should be dealt with so we'll have a much smoother launch.
In the past launches all problems have come from the client checking the block to possible forging of masternode votes. With enforcing mode off, the system will still detect these and report them but it won't reject the block. So once we stop seeing these messages (except for valid forged blocks) the system is ready.
This also allows us to turn on masternode payments much sooner. I believe it will take us just a few days to test this new setup, then we can turn them on for mainnet.
Instead I propose the following plan for launching RC3 in stages, which will be much safer and more stable:
We'll introduce an "enforcing" setting for masternode payments. This will be turned off at launch making it the equivalent of a soft fork, but will allow us to use the full infrastructure of the darkcoin network for testing. In the debug log, the system will complain when any issues arise and users can report such issues. After a period of time passes with no issues, we'll set a date to begin enforcing. At this time all issues should be dealt with so we'll have a much smoother launch.
In the past launches all problems have come from the client checking the block to possible forging of masternode votes. With enforcing mode off, the system will still detect these and report them but it won't reject the block. So once we stop seeing these messages (except for valid forged blocks) the system is ready.
This also allows us to turn on masternode payments much sooner. I believe it will take us just a few days to test this new setup, then we can turn them on for mainnet.
The RC3 system was maybe never enforced because a system change was scheduled for RC4.