• ​Overview of Master Node​
• ​New User Guide​

  • Step 1 Server​
  • Step 2 Server Prep​
  • Step 3 Download Binaries​
  • Step 4 Run the Beldex Daemon​
  • Step 5 Open a Beldex Wallet​
  • Step 6 Register Node​
  • Step 7 Check Registration​
• ​Express Setup Guide​

• Master Nodes are full nodes on the Beldex network
• Full nodes become Master Nodes when the owner locks the required amount of Beldexand submits a registration transaction.
• Once accepted by the network, the Master Node is eligible to win block rewards.
• Multiple participants can be involved in one Master Node and can have the reward automatically distributed

• Route end user’s internet traffic, either as an exit node or relay in a novel mixnet.
• Receive, store and forward encrypted user messages.
• Monitor other Master Nodes and vote on their performance.
• Be called into quorums which give them authority over instant transactions
• Act as remote nodes for users.

• A stable, relatively fast connection to be able to respond to ping requests to avoid being booted off the network.
• We recommend 2GB of RAM to cope with running the software reliably (Note: This requirement may be much greater once services are live). 1GB is fine for testing.
• At Least a 20GB SSD or Hard disk drive, this will be used to store the blockchain (Note: to future proof yourself against blockchain growth and message storage we recommend a 30 - 40 GB drive).
• A stable power supply. If your server goes down during the staking period, you may get kicked off the network, and not receive rewards while your funds are still locked for the remainder of the staking period.

Note: We do not officially endorse any of these providers, this list is simply illustrative of some of the options currently available*

• Don't try copying something by using the usual Ctrl + C hotkey! If you want to copy something, do so by highlighting text and then right clicking it. Pasting works by right clicking a blank area in the console.
• If you want to kill a process or stop something from running, press Ctrl + C. (This is why you shouldn't try copying something with this hotkey.)
• You can always check the directory you are in by typing pwd and list its contents by typing ls.
• You can always return to your home directory by typing cd.
• You can move into a given directory by typing cd <name> or move back up one level by typing cd ...
• PuTTY allows you to easily duplicate or restart a session by right clicking the top of the window. Handy if you’re trying to do a few things at once.

• Port 29089 (storage server to storage server)
• Port 29090 (client to storage server)
• Port 19090 (blockchain syncing)
• Port 19095 (Master Node to Master Node)
• Port 1090 (UDP, not TCP, unlike all of the above; Belnet router data)

NOTE: If you’re nervous about trusting the binaries or the download link, you should build it from source yourself. Instructions for that can be found in the README of https://github.com/beldex-coin/beldex​

1. 1.

   Create the beldexd.service file:

   1

   sudo nano /etc/systemd/system/beldexd.service

   Copied!
2. 2.

   Copy the text below and paste it into your new file:

(If you want to run a testnet master node, append --testnet to the end of the ExecStart line. Alternatively, if you want to be able to run both a testnet and mainnet master node simultaneously you can use two service files: beldexd.service and beldexd-testnet.service and add --testnet to the ExecStart= line in the latter. You would then use beldexd-testnet.service instead of beldexd.service in the commands below when you want to control the testnet master node.)

1. 1.

   Once completed, save the file and quit nano: CTRL+X -> Y -> ENTER.
2. 2.

   Reload systemd manager configuration (to make it re-read the new service file):

   1

   sudo systemctl daemon-reload

   Copied!
3. 3.

   Enable beldexd.service so that it starts automatically upon boot:

   1

   sudo systemctl enable beldexd.service

   Copied!
4. 4.

   Start beldexd.service:

   1

   sudo systemctl start beldexd.service

   Copied!

1. 1.

   Create the storage-server.service file:

   1

   sudo nano /etc/systemd/system/storage-server.service

   Copied!
2. 2.

   Copy the text below and paste it into your new file:

1. 1.

   Once completed, save the file and quit nano: CTRL+X -> Y -> ENTER.
2. 2.

   Reload systemd manager configuration (to make it re-read the new service file):

   1

   sudo systemctl daemon-reload

   Copied!
3. 3.

   Enable storage-server.service so that it starts automatically upon boot:

   1

   sudo systemctl enable storage-server.service

   Copied!
4. 4.

   Start storage-server.service:

   1

   sudo systemctl start storage-server.service

   Copied!

1. 1.

   Get the bootstrap signed file to communicate with the master nodes in the network. Use the below command to get the signed file:

1. 1.

   Once completed, save the file and quit nano: CTRL+X -> Y -> ENTER.
2. 2.

   Reload systemd manager configuration (to make it re-read the new service file):

   1

   sudo systemctl daemon-reload

   Copied!
3. 3.

   Enable belnet.service so that it starts automatically upon boot:

   1

   sudo systemctl enable belnet.service

   Copied!
4. 4.

   Start belnet.service:

   1

   sudo systemctl start belnet.service

   Copied!

You do not have to run this wallet on the server and you should not! Download the software and run it from elsewhere for security reasons!

If you are on testnet run the command with the --testnet flag: ~/beldex/beldex-wallet-cli --testnet

Note: When typing the password, the characters will not appear. It will seem as if you are typing and no text is appearing however the terminal is logging every character you type including if it is capitalised or lowercase.

Write down your wallet name and password on a piece of paper as this information will be required every time we want to enter our wallet.

Use a password with uppercase letters, lowercase letters, numbers, symbols and make the password at least 9 characters long.

NOTE: Do not use CTRL + C to copy your address, it will close the wallet down. Simply highlight the address and this will automatically save the portion you highlighted into your clipboard.

• A fully synchronized, up-to-date Beldex daemon running with the --master-node flag (see step 4).
• A beldex-wallet-cli primary address with enough Beldex in your account to meet the Master Node Staking Requirement (see step 5).

NOTE: You must run the command outputed by your daemon and not the command shown above.

Note: At this point you now have locked stakes! To unlock your stake run the following

• Operator contributes 50% of the requirement (5,000 Beldex)
• The next contributor must contribute at least (⅓ * 5,000) Beldex i.e. 1667 Beldex to become a participant.
• If this contributor had reserved a spot for more than 1667 Beldex, their Minimum Contribution would be that amount.

• Jump into section 6.2.1 - Operator if they are running the daemon and hosting the pool;
• Jump into section 6.2.2 - Pool Contributor if they are contributing to someone's Master Node.

NOTE: It is advised to read both sections of "6.2 - Pool Staking" to have a better understanding of the process.

• A fully synchronized, up-to-date Beldex daemon running with the --master-node flag (see step 4) at all times.
• A beldex-wallet-cli primary address with enough Beldex in their account to meet 25% of the Staking Requirement.
• 1-3 other contributors who also have a wallet (beldex-wallet-cli or the desktop GUI wallet) with enough Beldex in their accounts to meet 25% of the staking requirement.
• If the operator wants to reserve contribution spots for specific contributors: The address and contribution amounts the 1-3 contributors will stake.

NOTE: The other contributors addresses are optional to have as you can create your pool to be open to anyone to contribute to, however they are recommended to have to avoid any issues of other individuals stealing their spots. On the other hand, a reserved contribution spot can only be filled by that contributor: if they change their mind before submitting a stake your master node will be stuck inactive, so it is recommended to use reserved contribution spots only with contributors you trust.

NOTE: It is possible to reserve only some of the required stakes for specific contributors while leaving the remaining stake open.

NOTE: You must run the command outputed by your daemon and not the command shown above.

NOTE: the final amount will typically be slightly lower than what you entered in the prepare_registration command. This is expected: the required amounts are based on the registration block height which has usually advanced by a couple blocks between the time you prepared the registration and the time it gets mined into the blockchain.

If you are staking please do not use Subaddresses. They are currently unsupported by the Beldex wallet

If you are running your Master Node on testnet go to http://testnetexplorer.beldex.io/ instead.

Where <VERSION> is mentioned replace with the latest version, example v3.0.2

1. 1.

   Address
2. 2.

   Seed Phrase
3. 3.

   Pass-phrase