Permalink
Switch branches/tags
Nothing to show
Find file Copy path
Fetching contributors…
Cannot retrieve contributors at this time
180 lines (107 sloc) 6.09 KB

#start-many Setup Guide

Two Options for Setting up your Wallet

There are many ways to setup a wallet to support start-many. This guide will walk through two of them.

  1. Importing an existing wallet (recommended if you are consolidating wallets).
  2. Sending 1000 DIGIFEL to new wallet addresses.

Option 1. Importing an existing wallet

This is the way to go if you are consolidating multiple wallets into one that supports start-many.

From your single-instance Masternode Wallet

Open your QT Wallet and go to console (from the menu select Tools => Debug Console)

Dump the private key from your MasterNode's pulic key.

walletpassphrase [your_wallet_passphrase] 600
dumpprivkey [mn_public_key]

Copy the resulting priviate key. You'll use it in the next step.

From your multi-instance Masternode Wallet

Open your QT Wallet and go to console (from the menu select Tools => Debug Console)

Import the private key from the step above.

walletpassphrase [your_wallet_passphrase] 600
importprivkey [single_instance_private_key]

The wallet will re-scan and you will see your available balance increase by the amount that was in the imported wallet.

Skip Option 2. and go to Create masternode.conf file

Option 2. Starting with a new wallet

If you used Option 1 above, then you can skip down to Create masternode.conf file.

Create New Wallet Addresses

  1. Open the QT Wallet.
  2. Click the Receive tab.
  3. Fill in the form to request a payment.
    • Label: mn01
    • Amount: 1000 (optional)
    • Click Request payment button
  4. Click the Copy Address button

Create a new wallet address for each Masternode.

Close your QT Wallet.

Send 1000 DIGIFEL to New Addresses

Just like setting up a standard MN. Send exactly 1000 DIGIFEL to each new address created above.

Create New Masternode Private Keys

Open your QT Wallet and go to console (from the menu select Tools => Debug Console)

Issue the following:

masternode genkey

Note: A masternode private key will need to be created for each Masternode you run. You should not use the same masternode private key for multiple Masternodes.

Close your QT Wallet.

Create masternode.conf file

Remember... this is local. Make sure your QT is not running.

Create the masternode.conf file in the same directory as your wallet.dat.

Copy the masternode private key and correspondig collateral output transaction that holds the 1000 DIGIFEL.

The masternode private key may be an existing key from Option 1, or a newly generated key from Option 2.

Note: The masternode priviate key is not the same as a wallet private key. Never put your wallet private key in the masternode.conf file. That is almost equivalent to putting your 1000 DIGIFEL on the remote server and defeats the purpose of a hot/cold setup.

Get the collateral output

Open your QT Wallet and go to console (from the menu select Tools => Debug Console)

Issue the following:

masternode outputs

Make note of the hash (which is your collateral_output) and index.

Enter your Masternode details into your masternode.conf file

From the digifel github repo

masternode.conf format is a space seperated text file. Each line consisting of an alias, IP address followed by port, masternode private key, collateral output transaction id and collateral output index.

alias ipaddress:port masternode_private_key collateral_output collateral_output_index

Example:

mn01 127.0.0.1:9615 93HaYBVUCYjEMeeH1Y4sBGLALQZE1Yc1K64xiqgX37tGBDQL8Xg 2bcd3c84c84f87eaa86e4e56834c92927a07f9e18718810b92e0d0324456a67c 0
mn02 127.0.0.2:9615 93WaAb3htPJEV8E9aQcN23Jt97bPex7YvWfgMDTUdWJvzmrMqey aa9f1034d973377a5e733272c3d0eced1de22555ad45d6b24abadff8087948d4 0

What about the digifel.conf file?

If you are using a masternode.conf file you no longer need the digifel.conf file. The exception is if you need custom settings (thanks oblox). In that case you must remove masternode=1 from local digifel.conf file. This option should be used only to start local Hot masternode now.

Update digifel.conf on server

If you generated a new masternode private key, you will need to update the remote digifel.conf files.

Shut down the daemon and then edit the file.

nano .digifelcore/digifel.conf

Edit the masternodeprivkey

If you generated a new masternode private key, you will need to update the masternodeprivkey value in your remote digifel.conf file.

Start your Masternodes

Remote

If your remote server is not running, start your remote daemon as you normally would.

You can confirm that remote server is on the correct block by issuing

digifel-cli getinfo

and comparing with the official explorer at http://digifel.net

Local

Finally... time to start from local.

Open up your QT Wallet

From the menu select Tools => Debug Console

If you want to review your masternode.conf setting before starting Masternodes, issue the following in the Debug Console:

masternode list-conf

Give it the eye-ball test. If satisfied, you can start your Masternodes one of two ways.

  1. masternode start-alias [alias_from_masternode.conf]
    Example masternode start-alias mn01
  2. masternode start-many

Verify that Masternodes actually started

Remote

Issue command masternode status It should return you something like that:

digifel-cli masternode status
{
    "vin" : "CTxIn(COutPoint(<collateral_output>, <collateral_output_index>), scriptSig=)",
    "service" : "<ipaddress>:<port>",
    "pubkey" : "<1000 DIGIFEL address>",
    "status" : "Masternode successfully started"
}

Command output should have "Masternode successfully started" in its status field now. If it says "not capable" instead, you should check your config again.

Local

Search your Masternodes on https://digifelninja.pl/masternodes.html

Hint: Bookmark it, you definitely will be using this site a lot.