Quote from: cgt99 on September 28, 2016, 02:13:37 PM

I cant get masternode started with new version 2.1.3

Windows standalone MN on Windows 7 64bit.

"Not capable masternode: Could not connect to xx.xx.xxx.xx:51472"
Fully connected with other peers both In and Out.

Switching back to version 2.1.2.3 and masternode starts without issue:
"Masternode successfully started"

Didnt have this issue with the previos upgrades

I am in the same boat as cgt99. win7-64 same error message. I tried sync from scratch, no improvement.

my masternode.conf is empty (only the example), I didn't need to configure it with previous dnet version. If I switch back to the previous version, the masternode works perfectly.

However staking is working, it's specifically the masternode, the little lock icon never appears (tried to create new masternode too without success).

What should I do? any advices?

Quote from: s3v3nh4cks on September 29, 2016, 07:06:57 PM

Quote from: berron on September 29, 2016, 06:18:49 PM

Quote from: s3v3nh4cks on September 29, 2016, 04:24:12 PM

Quote from: berron on September 29, 2016, 04:15:15 PM

Quote from: jakiman on September 29, 2016, 12:22:44 PM

I have now updated all my masternodes & wallets to v2.1.3.0.

It was a very easy and smooth upgrade. Had no issues whatsoever.

DNET is getting more mature and resilient over time! Love it. Great work devs!

Same here, all my MN's are already paying and I'm starting to stake the aprox. expected amount of blocks, so for the moment everything seems to be right. Only thing is that I continue having the impression obfuscation never pass from 87 % (5000 Dnet/4 rounds here), but maybe only a personal impression.

Salute

The issue is the higher the rounds, the more people that are required for you to be able to freshly swap coins with. which is why it is taking so long. I am doing 10k/8 rounds and have been at 39% for quite awhile. As the network grows, it should become a much faster process.

Oh, thank you, now I understand it. So obfuscation speed, quantity can be also used as a pseudoindicator of the waelth of the network. Good.

Well, or at least of the people would OPT in to participate.

I tried obfuscation, and effectively it's a little bit slow. Sadly I can't run it on the same wallet as a masternode. Or is there an option? Because the daemon says deactivate when masternode is activated.