Can someone summarize how the remote/local masternode setup is affected by the last changes? Where do private keys need to be generated and where do they need to be included in the config file?

Also, can the local wallet be put in cold storage after starting the masternode?

Thanks!

LOCAL/REMOTE MASTERNODE SETUP WITH COLD WALLET UNDER THE LAST UPDATE

I would like to report that I was able to update and run my masternodes, using the local/remote wallet setup. The process was the same, but you need to remember that the local wallet is also going to need its own masternodeprivkey=[output from genkey]. So once you have the server side ready. On your local wallet darkcoin.conf change masternode=1, to 0. Get the masternode privkey, add it to the darkcoin.conf and change back to masternode=1. After that, follow the same process we used before to start the masternode remotely. From humanitee:

Start darkcoind on the remote machine.
On your local machine, send 1000 DRK to a newly generated wallet. Send it to the 0th address. If you use darkcoin-qt version to make your wallets, send it to the first (and only if it was newly generated) address.
On your local machine specify the server IP at launch with:
./darkcoind -masternodeaddr=YOUR_SERVER_IP:9999
Unlock your local machine's newly generated 1000 DRK wallet with your passphrase, ## is the time in seconds before the wallet will be once again locked:

 ./darkcoind walletpassphrase 'your wallet passphrase here' ##

On your local machine,

./darkcoind masternode start

For the above to work your local wallet must already have its own privkey on the darkcoin.conf (this key is different from the server one). I hope this helps.