Hello everyone, I hate to be that new guy. But I just thought I should make an account, to thank everyone for the ongoing support and also see if I can double check my configuration. I put up a masternode about a week ago on the 29th using u3mur4's script. At the time I noticed a lot of masternodes in error states, but I guess I didn't think very much of it as it was late and the one line script had worked it's magic.

Over the next few days, I noticed the active nodes drop. Puzzled I looked up what had happened. I was worried when I heard sentinel was the cause for the break in the network as a separate user account on my vps required to run it for a different masternode coin. Even though this had all occurred seemingly a few days after the stormchain I thought I should come clean about it anyway in case it can help any of the developers. I assumed that separate user accounts would help to prevent any conflicts but please let me know if necessary and I will move the node to a dedicated vps.

I removed the script and immediately pulled the github for the current version and configured sentinel,
since then I voted and re-indexed my wallet which removed the pseudo payments and got the core wallet back on the right chain.
Iv'e just restarted and re-indexed daemon on the vps so hopefully that will sync eventually too.

Should we be allowing any additional ports for sentinel?

Also, currently I have sentinel installed as:

(Coin 1) /home/user1/sentinel
(Coin 2) /home/user2/sentinel

Please let me know if this is a problem as I currently have at least one instance of sentinel on most of my vps's configured with a few different coins, in this fashion.
When I run separate tests they both give me the expected outputs.

I hope that I can do my part in keeping the network secure in the future, this seems like a great project and i'm really glad to see such an active community through this development.

Sorry to take up a post.