How to: Start a single Masternode with start-alias

How to: Start a single Masternode with start-alias

As you can probably tell from one of my recent posts: How to: Issue a remote start for all your Dash MasterNodes, I am a huge fan of start-many. What I didn’t know is that start-many forces your MasterNode to go to the back of the payment queue. I generally use start-missing which if it’s name is indicative won’t start all of them but rather just the ones on a missing state. Seeing that I am not sure that’s the case, I am recommending exploring using start-alias to only start the masternode you are in fact needing to start and not send the rest of them to the back of the queue. This is also useful when you need to restart one which might be in the Enabled state not in the Missing state.

Background

There is new payment logic in Dash v12 which results in sending your masternode to the end of the payment queue everytime you issue a remote start (awesome… NOT):

New Payment Logic

The masternode payments system is entirely rewritten for v12, in a way that doesn’t require the reference node to run. However, a lot has changed and it might get confusing if you don’t understand what’s going on, so I thought I would make a post to show how it works.

SPORK_10_MASTERNODE_PAY_UPDATED_NODES

When this is enabled on the network it means that the masternode network will only elect newer versions to get paid. This has nothing to do with enforcement and payments can still be stolen while this is enabled

In the next stage we wait till the network looks like there is consensus of the order of masternodes to pay. When the network has not gained consensus the masternode winners list will look something like this:

Masternode Winners:

If you look at “masternode winners” right now on mainnet, we have gained consensus and are ready to enforce! When the payment system has consensus it will look like this:

masternode winners

Other new things about the masternode payment system:
When you restart your masternode, you are forced to the back of the queue. When you update from v11 to v12, this goes into effect and you will not be paid for the first payment period.
– The network prefers to pay people that are not subject to this penalty, meaning that when we upgrade the first nodes to upgrade will get substantial rewards when SPORK_10_MASTERNODE_PAY_UPDATED_NODES gets activated due to the small amount of qualifying nodes. Over time the rest of the network will also qualify for payment and the payment period will extend until it is normal again. This is our new “fast upgrade” incentive system, the faster you upgrade the more you get :wink:
– Multiple payments in a row are possible and OK. There should be about a 1/100 chance of this happening and you will not skip your next payment, it’s something like the daily network lottery.

Obtained from: https://dashtalk.org/threads/v12-release.5888/page-21#post-64073. Post by: eduffield – Core Developer

 

Walkaround

As I mentioned there are two walkarounds. The first one is to use start-missing as shown in How to: Issue a remote start for all your Dash MasterNodes, while the second one is to use start-alias as described below:

  1. Open your local Dash QT wallet.
  2. Open the debug console.
  3. Unlock your wallet.
  4. Find the alias of the masternode you want to start by exploring the list of all masternodes available to you: masternode list-conf
  5. Execute the following command replacing <MasterNodeAlias> with the actual alias of the masternode you want to remote start.  masternode start-alias <MasterNodeAlias>

and that should be all!

You may also like...

Leave a Reply

%d bloggers like this:
Skip to toolbar