i really dont see why enforcement shouldnt be switched on. theirs 1pool that is paying 10% for months and now they will get even more time. i worry that other pools will switch back to 10% or more drkminers decide to move to the 10% pool. Either way rc4 should have enforcement on no matter what.

Doesn't it mean that a hard fork would be necessary for enforcement? If that's the case, sure, it's not ideal but it's hardly the end of the world.

I took it as no enforcement for the update, not 'no enforcement ever'. Fingers crossed.

I took it as no enforcement for the update, not 'no enforcement ever'.

I am seriously stressing right now.

What I understand is that the voting system was supposed to change from RC3 to RC4 but we stay with the RC3 system hence no enforcement for the RC4...

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..

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.

After a few days of peace, a new FUD offensive seems to have begun. My only comment to this is:

In 2014, a crack dev crypto unit was sent to prison by an organised FUD court for a crime they didn't commit.

This unit promptly escaped from a maximum-security FUD stockade to the crypto underground.

Today, still wanted by the POS coin shill's and FUD'sters, they survive as developers of fortune.

If you have a problem... if no one else can help... and if you can find them... maybe you can hire... the dArk-Team.