Set it up using the binaries from MIP and the quick sync script and it was fast and effortless! Used the Dash method from scratch (bit more complicated) and here it is...
"33ff087061fad94af7e4f1f73ff56af47f9b34e802cd845f5cf765b13944d453-1": {
"proTxHash": "520ebc4e8fb36d335e89d3527c88e0096bb605983efbd339f78d17be12ce453e",
"address": "104.167.113.181:40001",
"payee": "yXhRHuA2YsV44K5VZJyQSxZurQ8s7diKbq",
"status": "ENABLED",
"posescore": 100,
"posescoretries": 0,
"posescoresuccesscount": 0,
"lastpaidtime": 1564615177,
"lastpaidblock": 182751,
"owneraddress": "ygXsP7NRxDJtKKqRc2i1JXvxKZmXysYf76",
"votingaddress": "ya5TqeZC7GRbibSzT8jbfHCLEQNTKT6LDL",
"collateraladdress": "ydbZ7ppEEbq28Awyt2iQXTnM3JSn5fxKHF",
"pubkeyoperator": "90856729abbe57866ec136e1505b59bf2fb5c399e04581df8264ba0ce49709cccd8c3e74c45ea1815e71572d602110c0"
}
Thats awesome. I see .181 in my sanc list now also, with 0 POSE.
Just a guess, but maybe it was your masternodeblsprivkey on the old one, not matching? In both of my cases it was using externalip=. I found after I recreated without that, they stay up.
Yes, good to know you were able to use the Dash method. The pro for the dash method is you have more control over the operator and voting keys (which, we can expose in the future in our upgradesanc command, for more versatility). The con is you have to remember to save those private keys in a file by yourself. (In the case of a person who has a lot of sancs, the deterministic.conf might be convenient. In my case, the deterministic was more useful for me to write a monitoring program to manage the sancs later - I need to loop through them and control them, etc.)
Great, we have 5 sancs now enabled! We can start testing chainlocks pretty soon.
MIP, is yours up?
Have I forgotten to answer any questions about .14 other than making a test-list?
Btw, how did you lose your testnet controller wallet, was it a rabid animal, or a mad family member?