BITCORN Masternode Configuration
This guide is for the new BITCORN masternode configuration. After the BITCORN swap to the new chain, you will need to restore your balance. If you already have your balance restored, you can skip this part.
First of all, if you had the wallet of the old chain installed in your computer, you have to rename the Bitcorn folder to prevent it from interfering with the new chain. You will find this folder in the following location:
Rename the folder from Bitcorn to Bitcorn-old.
Then you need to download the new wallet from HERE. There’s two possible ways of getting back your CORN, depending on what you did on the old chain, and both of which require you to have downloaded the new wallet:
- If you sent all your BITCORN to the WEB-wallet, you have to withdraw it. Find the BITCORNHub bot in the Discord server of CTTV. By sending
$bitcornyou can see your balance. Next step is by to withdraw your balance to the local wallet using the withdraw command. The syntax is:
$withdraw <amount> <address>.
- If you applied for a manual swap, please send a DM to TimKim on Discord and you will receive instructions.
We use the Discord chat for assistance and support. Beware that some people might be interested in scamming you for corn by pretending to be someone from the official team and ask you to run certain commands or ask you to send them your wallet.dat file. We will NEVER ask for your wallet.dat file or your private keys.
Part 1: Masternode configuration
The new masternode configuration is different than the previous one based on the PIVX setup. Your masternode config information goes into the BITCORN client directly using the console. No more saving to file using notepad as earlier. If you’re going to install several masternodes, please follow this guide to the dot first to get that single node up and running. Then you can start thinking of your other nodes. Forget everything you think you knew about masternode-configuring, it’s time to learn again!
There is one thing you need to do prior to starting the installation to avoid encountering issues with the payout address if you send funds without using coin control.
- In your wallet, open settings
- On the “Wallet” tab, uncheck “Spend unconfirmed change”
Please close and reopen the wallet before proceeding to step 1.
protx register_prepare HASH INDEX IP:PORT Owner PUBLIC Owner 0 Payout (Payout)
Copy the code into an empty notepad document. We will later collect the data we need and paste over each item as we find it. Just copy and paste for now, nothing else.
Generate 2 NEW addresses in the RECEIVE tab of your wallet with the following labels:
And click “Create new receiving address”. If done correctly, you will see the following:
The “Owner” Address gets copy/pasted into the code you copied in step 1, TWICE (TWO TIMES). The word “Owner” is in two places in the text, and that's where you want to paste the address. If done correctly, it will look something like this:
protx register_prepare HASH INDEX IP:PORT CeH8MdnW9NeQV47fciVG6ZnbGq5mJRPqar PUBLIC CeH8MdnW9NeQV47fciVG6ZnbGq5mJRPqar 0 Payout (Payout)
Open up with debug console which you will find in the “Tools” menu and paste the following code:
Failing to do so will result in an error later.
For multi-masternode users. If you have restarted your wallet after you installed your last masternode, you need to redo the command above. It resets on boot.
Send a transaction of exactly 10 000 000 (10 MILLION) BITCORN to your MN1 address. It is important that you use coin-control for selecting the funds
If you have not previously encrypted your wallet, it’s time to do so (Settings-> Encrypt Wallet).
Once you have encrypted your wallet, go to Tools -> Console and type in “walletpassphrase <your_new_pwd> 600” which will unlock your wallet for 10 minutes (600 seconds) , and allow you to complete the MN setup.
Generate a new p2sh-segwit address. In the Console type the following command:
getnewaddress Payout p2sh-segwit
This address will replace the payout portion in the line of code, in your notepad. There are two places to replace.
If done correctly, it will look like this:
protx register_prepare HASH INDEX IP:PORT CeH8MdnW9NeQV47fciVG6ZnbGq5mJRPqar PUBLIC CeH8MdnW9NeQV47fciVG6ZnbGq5mJRPqar 0 3f4gXqKxyeJnnPEvkWbdmTD7uwyC6JsoWi (3f4gXqKxyeJnnPEvkWbdmTD7uwyC6JsoWi)
Now send some BITCORN to the Payout address you just created in the console in the previous step. 1 CORN is plenty. Now you have 2 pending transactions, one to MN1, and one to Payout.
This payout address need a funding of 1 CORN to pay for the fees to add the masternode data to the blockchain.
Go to the transactions tab and locate the 10 000 000 BITCORN collateral transaction you sent to MN1 earlier. Click the transaction to open the transaction details window. The transaction id of this transaction is your HASH, which you will paste into the notes you made earlier.
Open up your console (Tools-Console) and type “masternode outputs” and press enter. Find your HASH as txid with the corresponding INDEX(next to “n”):
Replace INDEX in the note with the number you see next to “n”.
Setup your server and log in with SSH. If you need instructions, please see this guide:
Run the masternode installer by pasting this command in the console. This will take a few minutes (with no progress-indicator, so please be patient):
It is important you let the installer run for a few minutes. DO NOT TOUCH ANYTHING. DO NOT CTRL + C. You will know when it’s finished.
Once the installation is complete, it will tell you to type the following command:
After that you have two choices. If you’re going to install 1 masternode, type:
Or if you’re going to install several masternodes, type:
And replace <number> with the number of nodes you want to install.
Your BITCORN masternodes will now start to deploy
If you wish to install more nodes in the future, just run the commands above again and the server will do the rest
After a short while you will have the missing pieces of information.
- You will now have the IP:PORT (next to ip:). Replace this in your notes.
- You also have the PUBLIC key (next to “public:”). Replace this in your notes as well.
If the data above disappears from your console, you can manually print it by typing:
Replace number with the node you want to print.
Once you paste the new (and last) data, your note will look something like this:
protx register_prepare d4a6f30236901bcbbeaa129f678801e9346f2dbb4b97d3bed1a896b95618417f 1 18.104.22.168:9333 GUN7JdHhTkFSqmmoPKPVRWMHFnMG6ADVeL 13d5333f92c37cb6beae608411446417c6e3a090c0ed8ae8b94e7dbe89fff1477873cdb922b935a5bb584a273fc8e318 GUN7JdHhTkFSqmmoPKPVRWMHFnMG6ADVeL 0 3dquQf4vSeJBVXVE6mS2E5U5CHj1yN7zAW (3dquQf4vSeJBVXVE6mS2E5U5CHj1yN7zAW)
Open your console and fully unlock your wallet for 10 minutes:
walletpassphrase <password> 600
Replace <password> with the pwd you used to encrypt your wallet. If done correctly, you will see:
If you later in the guide get “Error: Please enter the wallet passphrase with walletpassphrase first. (code -13)” Please run the walletpassphrase <pwd> 600 command again to unlock it.
Next, paste the information from your notes, in the console. It should look like this:
Part 2: ProTx Submission
Part 2 is different than previous masternode configurations. After a few commands, your coins will lock & masternode will start immediately after 1 confirmation.
Step 1: If you did everything correctly in the last step, the “collateralAddress” in the reply should match the address of MN1.
You need to use the “signmessage” command. It’s relatively straight forward, just use the results from the ProTx reply and fill it into this:
signmessage <collateralAddress> <signMessage>
This is the collateralAddress you have to copy and paste:
This is the signMessage you have to copy and paste.
The command should look like this:
signmessage y6TLo4xBZJwDaTj2nJtrYgbyCY5fNUFp1N 8wTRojKoWUveBNjuXKdECutM8FWeaf46ev|0|y5PR1rFxRknMgQfNrf5MbJwwWiBQgyToxc|y5PR1rFxRknMgQfNrf5MbJwwWiBQgyToxc|4a1bf6b9b95bf23ada5b38157ac9e37032a1fce6b75eb598be6d6fb46059efc2
If you’re successful, you’ll see the short line in response as the picture above.
Next you need to use the “protx register_submit” command. This is the final step and will enable your masternode & automatically lock your collateral.
protx register_submit <tx> <signmessage_result>
Copy the “tx” from your ProTx register_prepare results:
And the “signmessage_result” is from the reply of the signmessage command you just entered:
The final command should look like this:
protx register_submit 0200020001c6d045091f1fee36dd592f05db3a48c921ed6533f1be556b214cd839a865a4b70000000000feffffff01c0be9a3b0000000017a914bad961dd938ddc3afde9b97295c2dabc6c18c3fb8700000000cf010000000000a2e1e6107b0bc5e5734141954286a5dcc038e0f781855314a383a10df4c5d3680100000000000000000000000000ffff2d4c8f3623295c363f15458c28ba08094a6ecdd8e8db7c0efed909d1e65b46e419df07618c0d030b4c7c608a42bc1b3be246ef9a1d045842ded53a18d37b1d7dcec200bee6157cc24a3a5c363f15458c28ba08094a6ecdd8e8db7c0efed9000017a914bad961dd938ddc3afde9b97295c2dabc6c18c3fb87114678a1f4dc84071a6da6c2a86522ae28aba2b4b030102cd5cb97acca23f23c00 IBNJyhywgICRV+L8Qxba7GidWEbSKLMTGdv1xU/o6Jw7FNOrka6RkjLO6C92HcbXNEXJuCJlJ0VTsyvz9jgA1zo=
Step 4: After you enter the protx register_submit, your setup is complete. Your wallet will make a transaction and you will get a hash as a result.
Success! Your masternode will be active in one confirmation.
- You don’t need the hash result from the protx register_submit.
- Your masternode will automatically enable after 1 confirmation.
- If you restart your wallet you will see the collateral is locked.
- Check in the Masternodes tab after the confirmation. Check the box that says “My masternodes only” and you will see your Masternode is enabled:
- Your masternode is configured and payouts will begin shortly. There is no need to update the masternode.conf file. Masternode information is now stored directly on the BITCORN blockchain.
Multi-Node VPS Tips:
BITCORN allows multiple masternodes on a single IP. This reduces masternode hosting energy consumption and costs for our community and hosting providers.
- Simply follow the same steps again. You need a unique Owner and MN address every time
- You can reuse the same Payout address
- Re-use the same VPS, and enter this command to generate bitcorn-002:
This gives you a new IP:PORT and PUBLIC key. Everything else about the multi-node process is exactly the same.
For technical support, please speak up in #bitcorn-support in our Discord server.