Quote from: nesic1 on June 20, 2014, 10:28:57 PM

when will this forking end?

Quote from: thelonecrouton on June 20, 2014, 09:10:57 PM

Quote from: Simcom on June 20, 2014, 08:59:47 PM

Hi all, I have been been following todays events closely and I have few (maybe controversial) remarks:

First, the hardfork implemetation went perfectly as far as I can tell. The network never became forked at any point. Immediately following the hardfork a couple of the pools were 1-5 minutes behind the highest block, but at no point did any of the pools ever fork - despite repeated claims to the contrary by people that should know better ::cough cough::. I believe Evan mistakenly interpreted this 1-5 minutes of lag on certain pools and masernodes as a fork, when in fact it was not (probably due to the differences in blockheight reported by the pools and those reported to him by masternode owners). As others have suggested, the reason for this lag is probably because the solved blocks were just taking longer than usual to propagate through the network because there were a lot of old clients on the network, something not entirely unexpected.

This minor issue solved itself approximately 15-20 minutes after the hardfork took effect, and the network hummed along perfectly fine for another 30 minutes before the reversion was released on github. During this time masternode payments were also working perfectly. In retrospect, the decision to revert the code was probably a mistake, but I understand the decision as Evan was acting out of an abundance of caution and that bit of lag spooked him.

If anyone has any evidence to suggest that the network was "forked" at any point, please share - I have reviewed IRC transcripts and have read every post, and was monitoring the pools throughout the hardfork implementation and there was never any evidence that I am aware of to suggest that the network had actually forked. Hopefully Evan will re-release the same code and we can try to fork RC3 in a couple days.

+1

I think you're right, the network seemed to be sorting itself out, but maybe Evan spotted something we didn't? I've noticed a minute or two of lag both locally and on my masternodes before, they all always catch up, no forks, no problems.

Also, in case anyone hasn't figured out how to update and restart their masternodes with the newfangled cold/remote setup, here is what worked for me:

On remote:

darkcoind stop
mv darkcoind darkcoind-old-version-number
wget http://www.darkcoin.io/downloads/rc/darkcoind
chmod 755 darkcoind
darkcoind

...wait for it to sync up if needed

On local:

Stop local client if running
Edit your darkcoin.conf and put back in:
masternode=1
masternodeprivkey=your-priv-key-for-that-masternode
masternodeaddr=x.x.x.x:9999

Rename your copy wallet for that masternode back to wallet.dat and fire up the local client or daemon
Wait for it to sync up if needed, then
masternode start 'your-wallet-passphrase'

- you should get 'masternode started sucessfully' and you can now take the local wallet offline again, your masternode should appear at http://drk.poolhash.org/masternode.html within a minute or two.