As announced earlier, hosted masternodes will be provided as service to the community. The rationality is you have the funds (DMD), I have the resources to run it and the inclination to fiddle with compiling code and administering servers. You don't have to do any of that.
The service will be provided for a fee. I was educated it's not nice to provide free services
Today, the fee is 5 DMD/month.
The procedure to rent a masternode is as follows (short instruction):
1. You contact me, with your order. Use PM here.
2. I provide you with an address where to pay the fee.
3. You pay the fee.
4. I provide you with the IP address/port and key of the masternode.
5. You send 10k DMD to your own address. You then obtain the transaction output, with the following console command:
masternode outputs
6. In the masternode.conf file in the directory where your wallet.conf is located, you enter:
LABEL IP:PORT KEY TRANSACTION INDEX
The label is anything you care to remember. The IP:PORT and KEY you get from me, and the last two pieces come from "masternode outputs"
(you may have more than one, if you sent more than one 10k pile to yourself).
7. Restart your wallet.
8. You then open the Masternodes tab, where your new masternode will be visible under "My Masternodes". An inactive masternode is with status "MISSING". Click the "Start Missing" button or right-click each "MISSING" entry and select "Start-Alias".
Important: Wait at least 15 blocks after step 5. A masternode collateral needs to be at least 15 blocks old in order to start the masternode. Don't worry -- it will eventually start all by itself, later.
9. In a while (such as after 15 blocks), check your Masternode list again -- Active should be ticking. If you don't intent to actively stake with that wallet, lock it up and shut it down.
You are done. Enjoy DMD pour in your wallet.
10. You might want to set up MultiSend to make the earned coins go to your "main" staking address and be grouped with/staking with the rest of your DMD.
Please note, that it is advisable to do steps 5 and 6 one by one, because after seeting the transaction in masternode.conf upon start, the wallet locks it, so it's less likely you re-send the same 10k over and over.
When other hosted masternode services start appearing, they will use pretty much the same procedure, so if someone finds ways to improve this instruction, please feel free to contribute.