2015-01-24 16:42:48 +01:00
#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.
2015-01-25 15:34:08 +01:00
1. [Importing an existing wallet (recommended if you are consolidating wallets). ](#option1 )
2024-02-05 23:00:22 +01:00
2. [Sending 1000 NBY to new wallet addresses. ](#option2 )
2015-01-24 16:42:48 +01:00
2015-01-25 15:34:08 +01:00
## <a name="option1"></a>Option 1. Importing an existing wallet
2015-01-24 16:42:48 +01:00
This is the way to go if you are consolidating multiple wallets into one that supports start-many.
2015-09-09 05:38:45 +02:00
### From your single-instance Masternode Wallet
2015-01-24 16:42:48 +01:00
2015-09-09 05:38:45 +02:00
Open your QT Wallet and go to console (from the menu select `Tools` => `Debug Console` )
2015-01-24 16:42:48 +01:00
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.
2015-09-09 05:38:45 +02:00
### From your multi-instance Masternode Wallet
2015-01-24 16:42:48 +01:00
2015-09-09 05:38:45 +02:00
Open your QT Wallet and go to console (from the menu select `Tools` => `Debug Console` )
2015-01-24 16:42:48 +01:00
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.
2015-01-25 15:27:54 +01:00
[Skip Option 2. and go to Create masternode.conf file ](#masternodeconf )
2015-01-24 16:42:48 +01:00
2015-01-25 15:34:08 +01:00
## <a name="option2"></a>Option 2. Starting with a new wallet
2015-01-24 16:42:48 +01:00
2015-01-25 15:27:54 +01:00
[If you used Option 1 above, then you can skip down to Create masternode.conf file. ](#masternodeconf )
2015-01-24 16:42:48 +01:00
### 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)
2015-09-09 05:38:45 +02:00
* Click *Request payment* button
2015-01-24 16:42:48 +01:00
5. Click the *Copy Address* button
2015-09-09 05:38:45 +02:00
Create a new wallet address for each Masternode.
2015-01-24 16:42:48 +01:00
Close your QT Wallet.
2024-02-05 23:00:22 +01:00
### Send 1000 NBY to New Addresses
2015-01-24 16:42:48 +01:00
2024-02-05 23:00:22 +01:00
Just like setting up a standard MN. Send exactly 1000 NBY to each new address created above.
2015-01-24 16:42:48 +01:00
2015-01-25 15:27:54 +01:00
### Create New Masternode Private Keys
2015-09-09 05:38:45 +02:00
Open your QT Wallet and go to console (from the menu select `Tools` => `Debug Console` )
2015-01-24 16:42:48 +01:00
Issue the following:
```masternode genkey```
2015-09-09 05:38:45 +02:00
*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.*
2015-01-25 17:58:43 +01:00
2015-01-24 16:42:48 +01:00
Close your QT Wallet.
2015-01-25 15:27:54 +01:00
## <a name="masternodeconf"></a>Create masternode.conf file
2015-01-24 16:42:48 +01:00
Remember... this is local. Make sure your QT is not running.
2015-09-09 05:38:45 +02:00
Create the `masternode.conf` file in the same directory as your `wallet.dat` .
2015-01-24 16:42:48 +01:00
2024-02-05 23:00:22 +01:00
Copy the masternode private key and correspondig collateral output transaction that holds the 1000 NBY.
2015-01-24 16:42:48 +01:00
2015-01-25 15:34:08 +01:00
The masternode private key may be an existing key from [Option 1 ](#option1 ), or a newly generated key from [Option 2 ](#option2 ).
2024-02-05 23:00:22 +01:00
*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 NBY on the remote server and defeats the purpose of a hot/cold setup.*
2015-01-24 16:42:48 +01:00
### Get the collateral output
2015-09-09 05:38:45 +02:00
Open your QT Wallet and go to console (from the menu select `Tools` => `Debug Console` )
2015-01-24 16:42:48 +01:00
Issue the following:
```masternode outputs```
2015-09-09 05:38:45 +02:00
Make note of the hash (which is your collateral_output) and index.
2015-01-24 16:42:48 +01:00
2015-09-09 05:38:45 +02:00
### Enter your Masternode details into your masternode.conf file
2024-02-05 23:00:22 +01:00
[From the neobytes github repo ](https://github.com/neobytes-project/neobytes/blob/master/doc/masternode_conf.md )
2015-01-24 16:42:48 +01:00
2015-09-09 05:38:45 +02:00
`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.
2015-01-24 16:42:48 +01:00
```
2015-09-09 05:38:45 +02:00
alias ipaddress:port masternode_private_key collateral_output collateral_output_index
2015-01-24 16:42:48 +01:00
```
Example:
```
2024-02-05 23:00:22 +01:00
mn01 127.0.0.1:11427 93HaYBVUCYjEMeeH1Y4sBGLALQZE1Yc1K64xiqgX37tGBDQL8Xg 2bcd3c84c84f87eaa86e4e56834c92927a07f9e18718810b92e0d0324456a67c 0
mn02 127.0.0.2:11427 93WaAb3htPJEV8E9aQcN23Jt97bPex7YvWfgMDTUdWJvzmrMqey aa9f1034d973377a5e733272c3d0eced1de22555ad45d6b24abadff8087948d4 0
2015-01-24 16:42:48 +01:00
```
2024-02-05 23:00:22 +01:00
## What about the neobytes.conf file?
2015-01-24 16:42:48 +01:00
2024-02-05 23:00:22 +01:00
If you are using a `masternode.conf` file you no longer need the `neobytes.conf` file. The exception is if you need custom settings (_thanks oblox_). In that case you **must** remove `masternode=1` from local `neobytes.conf` file. This option should be used only to start local Hot masternode now.
2015-01-24 16:42:48 +01:00
2024-02-05 23:00:22 +01:00
## Update neobytes.conf on server
2015-01-24 16:42:48 +01:00
2024-02-05 23:00:22 +01:00
If you generated a new masternode private key, you will need to update the remote `neobytes.conf` files.
2015-01-24 16:42:48 +01:00
Shut down the daemon and then edit the file.
2024-02-05 23:00:22 +01:00
```nano .neobytescore/neobytes.conf```
2015-01-24 16:42:48 +01:00
### Edit the masternodeprivkey
2024-02-05 23:00:22 +01:00
If you generated a new masternode private key, you will need to update the `masternodeprivkey` value in your remote `neobytes.conf` file.
2015-01-24 16:42:48 +01:00
2015-09-09 05:38:45 +02:00
## Start your Masternodes
2015-01-24 16:42:48 +01:00
### Remote
If your remote server is not running, start your remote daemon as you normally would.
2015-09-09 05:38:45 +02:00
You can confirm that remote server is on the correct block by issuing
2015-01-24 16:42:48 +01:00
2024-02-05 23:00:22 +01:00
```neobytes-cli getinfo```
2015-01-24 16:42:48 +01:00
2024-02-05 23:00:22 +01:00
and comparing with the official explorer at https://explorer.neobytes.org/chain/NeoBytes
2015-01-24 16:42:48 +01:00
### Local
Finally... time to start from local.
#### Open up your QT Wallet
2015-09-09 05:38:45 +02:00
From the menu select `Tools` => `Debug Console`
2015-01-24 16:42:48 +01:00
2015-09-09 05:38:45 +02:00
If you want to review your `masternode.conf` setting before starting Masternodes, issue the following in the Debug Console:
2015-01-24 16:42:48 +01:00
```masternode list-conf```
2015-09-09 05:38:45 +02:00
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:
```
2024-02-05 23:00:22 +01:00
neobytes-cli masternode status
2015-09-09 05:38:45 +02:00
{
"vin" : "CTxIn(COutPoint(< collateral_output > , < collateral_output_index > ), scriptSig=)",
"service" : "< ipaddress > :< port > ",
2024-02-05 23:00:22 +01:00
"pubkey" : "< 1000 NBY address > ",
2015-09-09 05:38:45 +02:00
"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
2024-02-05 23:00:22 +01:00
Search your Masternodes on
2015-01-24 16:42:48 +01:00
2015-09-09 05:38:45 +02:00
_Hint: Bookmark it, you definitely will be using this site a lot._