Take a look at your masternode.conf file, just in case you involuntary change or erase port number.

Seems that sometimes is difficult to find a suitable MN to do de mixing. I was at 90% yesterday, now I'm at 94% abd I'm getting lot of not compatible MN found as last obfuscation message.

Ok, Paul, will do. Sorry.

Invest in it is the real bounty

Hi Antho,

I would love a multialgo, multicoin with internal exchange pool similar to yiimp or zpool, but with continued code development to improve their features.

Pool seems not to have any worker, it's a info updating problem or the info is good? Maybe during the first week you can put the pool as no fee and announce them in the ann threads of DGB, and point some of the company cards to them to get some hash (and info about possible problems).

Salute

I'm on v2.1.2.2 so will wait to the next mandatory, too much problems to restart my MN's in 2.1.2.2 to make all the process again   

Jakiman has just announced that new version to correct some problems syncing from scrach and other minor changes has been launched as I was writing my post. To use new version instead v2.1.2.2 simply change these two code lines:


for these


Notice that the version number has changed.

Salute

Hi Paul,

All the MN's seems to be working right now quite well, I don't know if you have done any king of changes but they seem to work, thanks.

If anyone is interested on updating their MN's to v2.1.2.2 version and while Paul prepare the scrypt here goes the instruction list. If your MN is working fine and you only want to update it use this command list:


and if you have a corrupted, stucked or similar blockchain use this:


Some people has found problems restarting the MN's from the controller wallet, controller wallet shows the MN's as ENABLED but when you enter in the MN and type


you found the message "Hot masternode waiting for remote activation". Jakiman found the solution stopping and starting again the daemon. And I find that it you make it very fast it doesn't work. So in that case you have to do:


And restart the MN's from the controller wallet. I have found some problems also using start-all instead of start-alias to restart them, but I think this is not a general problem.

If anyone find any kind of mistake, please tell.

Hope this helps.

Edited for typos and small corrections in code.

Hi crackfoo,

I have solved  my diff problem eliminating decred algo  from the scrypt. Seems that put it on the multialgo hash power setting generate some kind of problem. Sentence was:


Do you see something incorrect in the algo name or similar??

Thanks

Solved, I have resync from scratch (but after solving the problem I think it was no necessary) and I have done two things. The least important I think is to add "addnode=coin-server.com" to the darknet.conf file, that has no nodes since the blockchain problems in version v2.0.x. And more important, I have started the wallet, wait for sync, stopped the wallet, WAIT FOR A MINUTE, and started it again. I thinks that when I have stopped the wallet in the first attempts I tried to restart it again too fast, and the stopping action make something that allow the MN to be activated. I will inform again as soon as I have the first payments.
Thanks, Jakiman, your indication gives me a clue that my problem could be there.

On the other hand I have obfuscation completed at 93%, what happens when it reach 100%?

I have the impression I'm stacking blocks faster since I have obfuscation activated.

And as we approachh firsr block reward decrease in POS phase price seems to go up.

Did like you said and the result is the same, only change is that now my MN's has a value on "vin" : "CTxIn(COutPoint(0000000000000000000000000000000000000000000000000000000000000000, 4294967295), coinbase )", diferent to 00000....
I have activated obfuscation, can be related with it, devs? darknet.conf and masternodes.conf are ok in the controller wallet, only coin-server.com as node and correct Privkeys and associated collaterals, and the same in the MN's, each ip has its asociated privkeys. But they don't change from the waiting remote activation state, nor with start-alias [MN alias] neither with masternode start-all.

I have also stop and start a mn as jakiman said and it didn't worked. After work I will try to resync again from scratch and start them again to see if that solved the problem. Any idea, suggestion is welcome. Anyone with similar problems or I am the original guy?

Of course, masternode.conf file has not been changed in my controller wallet and the same for darknet.conf in my MN's. And ./darknet-cli getinfo gives me the same block in controller wallet and MN's, same as http://178.254.23.111/~pub/DN/DN_Info.html.

I have already updated my controller wallet and my MN's to v2.1.2.2, but when I try to restart the masternodes I receive the correct message of:


And when I go to my MN and type


I receive this message


Any thoughts???

EDIT: And when I ask for masternode list-conf in my MN's controller wallet all of them appear as ENABLED.

I have connections, some of them to 2.1.2.1 wallets and some of them to 2.1.2.2 wallets. Is this correct?

And when you have time, devs, could you give a little explanation of what obfuscation is and how it works for dummies?

Thanks

Yes, my phone was unlocked, and I think is the only way to use one of this cards, but maybe anyone on the forum have another solution 

Started here as you asked. Some questions:

I need to do anything more than change ofuscation amount and rounds and push the button?

Why the button doesn't look like a button?

Where is the option to stop the anoying sound that happens everytime a transaction happens? I REALLY need it...  

Are you continuing development, krile???

Could you told us if you are working in any new feature in the wallet?

I use a no call card of this type in my last travel to Japan (with the advantage that in Japan I didn't have any limitation in consumed bandwith by the provider) and the result was really, really good. DOn't know the Belgium company, but probably you have a lot of reviews in the net.

https://www.prepaidzero.com/product/belgium-2gb-prepaid-sim/

Exactly, you told it much better than me.

Paul, I restarted the MN's when the update happened. If I remember correctly I did it about ten times before the devs were finally able to fix everything. I helped trying to install the new version of the wallet everytime it was changed as soon as I could and informing about the results. And of course, that was not your responsibility at all, and I think no one told anything in this thread during those days. But there has been in these months a lot of server restarting, due changes in configuration, external attacks and so on. And avoid that is your responsibility as to have a strong pass to my servers is mine.

Sorry, Paul, but if things don't start to change, I will migrate all my MN's to vultr once the contracted time expires. I have one there during two months, and yes, I had to do all the config work and in that moment it was really expensive compared to yours. But the MN's didn't fail a day in those two months. It's frustrating to have to redo all once and once again. As I told you, I'm losing time and money everytime this happens. Don't take this as any kind of personal attack, simply the quality of the contracted service is less than expected lately. Hope you being able to sort all the things out, but in other case, I will have to abandone your servers. In only some days reward is going to decrease and we will have lost a good amount of DNET in this period. And I only have half docen of MN's. People with a lot of them has the right to be really upset wtih this.

Ah, I will not create a ticket again for this, I have problems in nodes in the same ip ranges than others, so put another ticket in the queue would not help to any of us.

Salute

Please, include a darknet-update-blockchain.sh in your scrypt list to avoid us to sync the complete blockchain everytime that this kind of shit happens. Your server are horrible slow updating, and I can't stay half an hour waiting for the sync. These problems make me lost money and a lot of time.