ok... I found on first post, there now external cold wallet not working
but... I found this: https://dashpay.atlassian.net/wiki/spaces/DOC/pages/27197442/Guide+using+OS+X+local+Linux+remote
here is one more option ... masternodeaddr - that we need to put in our cold wallet
maybe this is a problem ?
Hi Svirus,
Great find. Yeah, I had gone through that myself, and in the end the only way I could create the masternode was in hot mode, and then I did successfully boot two masternodes up, and they are running in cold mode. In cold mode, I see the masternodes are now being paid through the masternode payment system (not through block subsidy) and the amounts seem to be correct. I have not successfully activated one in hot mode.
You did find the key to the problem, whenever the hot wallet is 'activated' from the controller wallet, then I see this in the log on the *sanctuary*:
Got mismatched pubKeyCollateralAddress and vin
Just like you do. Now it is possible, that my first 7 tests didnt actually honor the 'masternodeaddr'. I do remember this, it is quite different to fully qualify the addr and the port. If you want you can try this: masternodeaddr=YourIP:40001. Note the fully qualifyied port number for testnet.
Could you see if that works? Btw, our port is 40000 for prod and 40001 for testnet, so anytime you see a 9999 for dash its 40001 for our testnet.
Im thinking we try to get hot mode going a little while longer, and eventually over the next day or so, we put someone else here on a mission to keep working on hot mode and we bring up 5 or so in cold mode to keep us moving as a team, so that I can add the code for the sanctuaries on the web site for testnet.
Does anyone here have a dash masternode? I was kind of wondering how long it takes to see the other masternodes in the all sanctuaries list.