Masternode.me masternode POSE_Banned

Bridgewater said:
You cant do an update_service without the privkey which moocowmoo has.
But for update_registrar, you could try protx update_registrar yourprotxhash "" "" "" feesourceaddress (or leave it blank and it uses the payout address if it exists in the wallet you're issuing the command from).
see https://docs.dash.org/en/stable/docs/user/masternodes/maintenance.html#proupregtx for details.
Click to expand...

Sorry I read that incorrectly. Yes I did update_registrar before I reached out for help. It didn't work.
 
wizzard.ng said:
Sorry I read that incorrectly. Yes I did update_registrar before I reached out for help. It didn't work.
Click to expand...
If you can't get in touch with him, you should probably consider a different service provider. You could try https://dashmasternode.io which is run by @splawik21 who is very well known and trusted in this community since the beginning. Every day your masternode is down is costing you money (around $10 per day). You won't need any of the old information from moocowmoo's node. You can just register a new masternode with your same 1000Dash collateral. You'll be at the back of the payment line whether you restart the existing MN with moocow or create a new one with someone else, so there's no advantage to keeping the same registration really, except for convenience (and price, if masternode.me is cheaper).
 
In fact the operator of the service uses masternode operator privkey on the server side and provides the pubkey for the user.
With pubkey you cannot update_service.
If you are able to host it yourself it's even better but I will not tell you no if you decide to host it with me.
Thnx @Bridgewater for pinging.🍻
 
You must log in or register to reply here.
Back
Top