Confidentiality is having the agency to decide when you reveal personal information. It is a particularly valuable quality today, when the collection and storage of personal data are taking place at unprecedented levels in history.

Beldex is a confidential currency based on Monero, Beldex currently offers incentive based Master Nodes and in future Beldex will be using POS instead of POW.

Beldex is mainly focused on utilities where you can spend beldex freely, we are in the process of creating a crypto ecosystem to eliminate the middleman and perform financial transactions with absolute freedom

More information on the project can be found on the website

If you are unsure where to start check out our "Getting Started" page by clicking here

Community Channels

• Telegram Channel:

• Telegram Chat:

• Discord:

Copyright

Copyright (c) 2019 The Beldex Project.

Portions Copyright (c) 2014-2018 The Monero Project. Portions Copyright (c) 2012-2013 The Cryptonote developers.

The Beldex wallets are a gateway into confidential, decentralised transactions and communications. They allow you to hold private keys and secure, mine, stake or trade Beldex. Each wallet is designed specifically for different users depending on their goal and level of expertise.

The different wallets currently available are the:

• Graphical user interface wallet (GUI)

• Command-line interface wallet (CLI)

• Mobile wallet

• Web wallet

Use cases

Before deciding which wallet you want to use, you must first know what you want the wallet for.

Receiving and sending Beldex

All Beldex wallets can receive and send Beldex, however some are much easier to use for this specific purpose.

The easiest wallets to use for sending and receiving Beldex are:

• Graphical user interface wallet (GUI), or the

• Mobile wallet

The GUI wallet can be downloaded

Hosting a Master Node as an Operator

If you want to host and operate a Beldex Master Node, there is only one wallet that offers the ability to register a Master Node: the command-line interface wallet (CLI) which can be downloaded .

To better understand how to prepare, register and maintain a Master Node, check out this guide .

Staking to a Master Node as a contributor.

Do you have at least 25% of a Beldex Master Node staking requirement, and want to contribute to a Master Node pool?

If so, you will want to either use the:

• Graphical user interface wallet (GUI) - Currently under development, or the

• Command-line interface wallet (CLI)

You can download the cli-wallet from

1. Educate Yourself

Confidentiality is having the agency to decide when you reveal personal information. It is a particularly valuable quality today, when the collection and storage of personal data is taking place at unprecedented levels. We are in an age where data is of high value, and Beldex aims to equip individuals with tools to obfuscate their information and interactions with the internet. Protecting your data keeps power on your side.

Beldex's confidentiality tools offer free communication by incentivising indviduals through its cryptocurrency block reward to keep the network confidential, secure and untraceable.

Before you start using Beldex, you should on how Beldex will help you obfuscate your data.

2. Choose Your Wallet

The Beldex wallets are a gateway into confidential, decentralised transactions and communications. They allow you to hold private keys, secure Beldex, stake Beldex and trade peer-to-peer.

If you are unsure about which wallet to choose, you should go to the page.

3. Acquire Beldex

Beldex can be purchased on exchanges (currently listed on MEXC, Gate.io, KuCoin and other exchanges which can be found here: ).

You can also aquire Beldex by staking it on masternodes & earning rewards in BDX for your contribution. Staking BDX on masternodes is process by which users can participate in the Beldex network and earn rewards by validating transactions made on the Beldex blockchain.

4. Stake and Earn Beldex

You can stake Beldex to receive rewards by running a Master Node with peers or by yourself.

To operate a , an operator and provides a minimum level of bandwidth and storage to the network. In return for their services, Beldex Master Node operators receive a portion of the from each block.

Wallets

The Beldex wallets are a gateway into confidential, decentralised transactions and communications. They allow you to hold private keys, secure or mine Beldex, and trade peer-to-peer.

Beldex wallets store a collection of public and private keys which can be used to receive, view, or spend Beldex.

The wallet uses the private keys through a daemon which synchronises with the Beldex Network to scan for incoming transactions and to send outgoing transactions.

Command Line Interface Wallet (CLI)

The Cli Wallet is for more advanced users and offers the most tools when interacting with the Beldex Blockchain.

CLI Guides

Integrated addresses are ideal for accepting Beldex in an automated fashion - like in online stores and exchanges.

Beldex integrated address embeds a payment ID. This allows you to learn for what you are being paid.

Please note these are Beldex technical payment IDs and must not be confused with business identifiers like order number or invoice number.

The transaction to integrated address will not reveal the payment ID publicly. Payment ID in a transaction will be encrypted with a shared secret (one-time random key known only to sender and recipient). Only the recipient will be able to match the transaction against payment ID.

Beldex integrated address obsoletes the former practice of using full 32-bytes payment ID in a transaction extra field (where it was not encrypted).

Address

A Beldex public address is what you publish to get paid.

An address can be generated offline and for free. It boils down to generating a large random number representing your private spending key.

Publishing your Beldex address does not endanger your confidentiality. That's because in Beldex transactions go to stealth addresses which are decoupled from your public address.

In cryptocurrencies, multisig feature allows you to sign a transaction with more than one private key. Funds protected with multisig can only be spent by signing with M-of-N keys.

A stake involves holding a specific cryptocoin in a wallet for a particular period of time. A staking requirement is the minimum amount of said cryptocoin that is required to stake.

Master Node Staking Requirement

A Beldex staking Requirement is the collateral requirement an operator stakes through a time-locked output, which can be unlocked as per the contributor's request. Upon a request to unlock the funds they will stay locked for an additional 15 days where the contributor will still receive rewards. In the extra field of the transaction, the Master Node operator includes the Beldex address which may receive Master Node rewards. This address will also be used as the public key for Master Node operations such as swarm voting.

Before each node joins the Master Node network, other nodes must individually validate that the said nodes collateral outlay matches the required amount, as per the decreasing collateralisation requirement. If the node is offline for a reasonable time, its uptime proof will not be sent to the other nodes resulting in a deregister of the node. Deregistered nodes will have their collateral requirement locked for 30 days.

The staking requirement is 10,000 bdx during Master Node launch (block height 56240). The staking amount is constant at the moment. The amount may vary based on the future emmision.

Getting Super Powers

Becoming a super hero is a fairly straight forward process:

Remote Nodes

On any given cryptocurrency network, storing a full copy of the blockchain is not possible or practical for many users. In Bitcoin and Ethereum, users can choose to connect to a public full node that holds a copy of the blockchain and can query and submit transactions to the network. This works because Bitcoin and Ethereum full nodes can efficiently search the blockchain for transactions that have the users public key as the target.

Due to the construction of CryptoNote currencies, public full nodes (called remote nodes) are put under much more stress. When a user connects to a remote node, they must temporarily download every block (upon wallet creation or since last checked block) to their local machine and check each transaction for a public transaction key which can be generated from the users private view key. This process can cause a significant performance impact on remote nodes. Considering that there is no reward for this service, it can dissuade users from operating syncing services for light clients. CryptoNote mobile wallets are often unreliable and sometimes have to switch between remote nodes multiple times before establishing a reliable connection to either scan the blockchain or to submit a transaction.

The easiest and most efficient way to set up a master node is by using Docker. Follow these two simple steps to set up a master node with Docker. We have provided a shell script to handle all the heavy lifting for you.

Note: This guide assumes some familiarity with the command line and running a Linux server. For a more detailed walkthrough, check out our full Master Node setup guide.

Step 1 : Create or Download the shell file

Copy the below code to a shell file master-node-deploy.sh

OR

Step 2: Register Master Node

Make sure the node is fully synced before run this command

Check the node status

You should receive an output similar to the screenshot provided. Ensure that the height of your node matches the current network height, which can be verified at . If the heights do not match, allow the node to fully sync, which may take 4-5 hours.

Prepare for Registration

Once the node is fully synced, run the below command to register the master node

After successfully running the command, you will receive an output similar to the screenshot below. To complete the registration, execute the master node command from the output in your wallet.

The server specifications such as storage and bandwidth for hosting an MNApp are dependent on the user's requirements. For example, a video streaming platform may require more storage than an information sharing platform.

However, you need a Linux system with Ubuntu 18.04 or 20.04 to run an MNApp.

Step 1: Install BelNet on Your System and Generate Your Belnet Address

Download and run the binaries

Enter the following command into the terminal to download the Belnet binaries from cloud

Unzip the file using the following command

Run the Belnet binary

Then, copy and paste the following command to open the belnet.ini file.

Scroll down to the [network] section and configure the keyfile by giving it a name of your choice. Your MNApp private key will be stored in the following path. Here, we’ve named our keyfile, mnappkey.private

Enter the following command and restart the Belnet client

Step 2: Find Your MNApp’s BelNet Address

To find your MNApp address, enter the following command.

For example, this is the MNApp address for the Beldex explorer hosted on BelNet cw41adqqhykuxw51xmagkkb3fixyieat1josbux13jn6o973tqgy.bdx

Step 3: Download and Install Nginx

Nginx is a dependency. So download and install it using the following commands

Use the following command to check whether nginx is working

Step 4: Setup Your MNApp Web Page

Your web content goes into this directory

Create a directory using the following command. Give a name to your directory. You can do this by replacing your_own-directory in the command below with your directory name.

Place your html web page into this directory

Step 5: Configure Nginx

Below is a sample configuration of Nginx

Enter the following commands

Now enter your directory’s name (established in Step 4) in place of your_own_directory in the command below.

Add the index file of your webpage here using the following command.

Note: Replace your_webpage with the filename that you want to assign to your index html file.

index your_webpage.html;

Now choose a server name by entering the following command. Replace the sample BelNet address below with your MNApp’s BelNet address generated in Step 2.

Save it by pressing Esc and then :wq

Restart Nginx using the following command

To access your MNApps, connect to BelNet and enter the MNApp’s BelNet address into a browser’s address bar

e.g.

Note: You cannot host a masternode and an MNApp in the same server. You cannot host a BelNet exit node and an MNApp in the same server.

If you have a Mnemonic Seed Phrase, restoring your wallet from it would probably be a good option. Otherwise, you can restore your wallet from private keys. You will need to have the following keys to proceed:

• Wallet public address

• Spend Key

• View Key

Step 1: Download and unzip CLI wallet

• Download the latest release of wallet CLI software for your desired operating system: https://github.com/beldex-coin/be/reldex/releases

• Unzip beldex-[operating-system]-[platform]-[version].zip file

Step 2: Run wallet in restore mode

• Open a (Windows) or (Linux / OSX) and navigate to the wallet folder

• Run wallet with --generate-from-keys argument:

./beldex-wallet-cli --generate-from-keys [New Wallet Name]

Where [New Wallet Name] is a new wallet name. You can enter any name here, use something rememberable and meaningful.

Step 3: Enter wallet address, view and spend keys

On the next step, specify all 3 wallet keys, one by one:

• Enter Standard address and press [Enter]

• Enter Secret spend key and press [Enter]

• Enter Secret view key and press [Enter]

Step 4: Enter wallet password

• You will be prompted for a password. Enter a new password that follows the and press [Enter].

• Confirm password and press [Enter].

Step 5: Specify a blockchain height

If you know the block height at which wallet was created or a first transaction was made, you can enter it here. Specifying a blockchain height will help to scan the wallet faster.

If you don't know a specific blockchain height, press [Enter] for scanning from block height 0.

Step 6: Wait for the refresh process to finish

For refresh process to start, you need to have your daemon running. Another option would be to use a remote node. For that, use the following command, replacing and with the host and port number of the remote node you are connecting to:

Once refresh is done, you can use your full functioning restored wallet. Your public wallet address will remain the same.

Windows

Download BelNet GUI for windows from the .exe file below:

https://deb.beldex.io/Beldex-projects/belnet-gui/belnet-gui-2.0.0-win64.exe

Linux

Download BelNet GUI for Linux using the guide below:

Step 1: Add the key

Enter the following command to add the keys

Step 2: Update the certificate

Enter the following command into the terminal to install and update the certificate

Step 3: Install BelNet GUI

Enter the following command to complete the BelNet GUI installation

The beldex-wallet-cli is the “Command Line Interface” wallet software that is used to run Beldex accounts through command prompt or terminal. The CLI wallet only uses text to do operations, where the oki-wallet-gui wallet offers a graphical user interface with buttons to do most of the operations the beldex-wallet-cli does.

Bear in mind that the CLI wallet, while harder to use, is generally faster and more reliable. If you are still interested in the 'beldex-wallet-cli' you can find it . Download the latest release for your specified Operating System, for this user guide we are going to assume you are running Linux.

This document is for Master Node Operators who have used the previous Master Node Full Guide and wish to update the version of their Master Node.

Note that this update guide is for individuals running their Master Node as a Service on linux. If you are using any screen's you will need kill the screens and go back to the Master Node Full Guide and follow it once more.

It is highly recommended running your Master Node as a Service due to the ease of updating.

Step 1: Load and Update your VPS.

If you are updating your VPS you would by now have a good understanding of how to log in to your server. If you don't check out how you prepared your server in this guide .

Once we have logged in to our VPS we should update our package lists, the below command downloads the package lists from the repositories and "updates" them to get information on the newest versions of packages and their dependencies. It will do this for all repositories and PPAs.

You will notice a bunch of package lists were downloaded, once this is complete run the below command to fetch new versions of any packages we currently have installed on the system.

You will be prompted to authorise the use of disk space, type y and enter to authorise.

If you are prompted during the upgrade that a new version of any file is available then click the up and down arrows until you are hovering over install the package maintainer’s version and click enter.

Alright, good to go. Our server is now up to date. On to the fun part!

Step 2: Download the new Beldex Binaries

To download the Linux binaries use the following command:

Where <link> is the download link of the latest linux release. To find the link go to , right click the latest linux release and click Copy Link Location.

Your command should look something like:

To unzip the downloaded zip file run the following command (changing 7.0.0 to whatever version you downloaded above):

You will see something like this:

Note that they are unzipped into the beldex-linux-x86_64-v7.0.0 folder; you can check they are unzipped by running the following to change into the folder and then listing the files:

We now want to replace our "symlink" to the new extracted beldex-linux-x86_64-v7.0.0 folder. If you are unfamiliar with what the "symlink" was doing previously have a look at the where you first set it up.

Otherwise, run the following command.:

Where <folder_name> is the new folder we created when unziping the release. In this case if we were to update to v7.0.0 the commands we would use would be:

This replaces our virtual beldex folder that pointed to an old folder to the beldex-linux-x86_64-v7.0.0 folder we created.

At this point it is wise to restart your system with the following command:

Once the system has restarted it will reboot the new version of beldexd.

Log back in to your VPS and double check the new version of beldexd is running smoothly by running the following command:

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

Excellent! You have now updated your Master Node.

Although Beldex implements novel changes on top of the CryptoNote protocol (ASIC Resistance, Dynamic Block Size & Static Ring Signatures), much of Beldex’s networking functionality and scalability is enabled by a set of incentivised nodes called Master Nodes. To operate a Master Node, an operator time-locks a significant amount of Beldex and provides a minimum level of bandwidth and storage to the network. In return for their services, Beldex Master Node operators receive a portion of the block reward from each block.

The resulting network provides market-based resistance to Sybil attacks, addressing a range of problems with existing mixnets and confidentiality-focused services. This resistance is based on supply and demand interactions which help prevent single actors from having a large enough stake in Beldex to have a significant negative impact on the second-layer confidentiality services Beldex provides. DASH first theorised that Sybil attack resistant networks can be derived from cryptoeconomics. As an attacker accumulates Beldex, the circulating supply decreases, in turn applying demand-side pressure, driving the price of Beldex up. As this continues, it becomes increasingly costly for additional Beldex to be purchased, making the attack prohibitively expensive.

To achieve this economic protection, Beldex encourages the active suppression of the circulating supply. In particular, the emissions curve and collateral requirements must be designed to ensure enough circulating supply is locked and reasonable returns are provided for operators to ensure Sybil attack resistance

Master Node Activities

Right now Master Nodes are full nodes on the Beldex network. Full nodes become Master Nodes when the owner for 30 days (2 days on testnet) and submits a registration transaction. Once accepted by the network, the Master Node is eligible to win . Multiple participants can be involved in one Master Node and can have the reward automatically distributed.

Guides & Resources

Step 1: Install Docker and Docker-Compose

Docker and docker-compose are prerequisites to download and run the docker images and container.

Enter the following commands to download and install docker.

Enter the following commands to download and install docker-compose.

Step 2: Pull the Image From Docker Hub

Enter the following command into the terminal to pull the BelNet Exit Node image from the docker hub.

Step 3: Download & Compose yml File

Enter the following command to get the BelNet yml file from Beldex deb.

Step 4: To Run Container

Enter the following command to run the yml file as a container.

Step 5: Login Into Container

Enter the following command to get the container ID and other details.

Enter the following command after replacing your container ID in place of <container -id>

Step 6: To View Exit Node Address

Your exit node is now live. Get your exit node’s BelNet address using the following command.

Outline For Existing Master Node Participants and Operators

Infinite Staking is an incremental upgrade on the existing staking process that is currently available on the Beldex network (currently active in Hardfork 10: Bulletproofs, introduced in Hardfork 9: Master Nodes). With Infinite Staking, Master Nodes do not expire and funds remain locked until a contributor or operator explicitly requests the Master Node to unlock the funds.

Since Infinite Staking is an incremental upgrade, most of the steps necessary to register and participate in a Master Node remain the same. A quick overview for the new staking process is summarised for quick grokking. (Yes, grokking is a word. Google it.)

System Requirements

Below are the system requirements and the minimum specifications of dedicated server or VPS

Step 1: Install BelNet on your VPS

Copy and paste the following link into the terminal

This will download the Belnet binaries from cloud

Unzip the file using the following command

Execution

• install vim editor using the following command

• Install tmux in your system

• Create a tmux session

• Run the Belnet binary

• Download the bootstrap file using belnet-bootstrap

Step 2: Configure Belnet.ini using vim

• Go to Belnet config directory

• Edit the belnet.ini file by entering the following command

Add the following lines under the [router] section or uncomment the following by removing the #.

This will configure the number of connections that an exit node can maintain.

Add the following lines under the [network] section or uncomment the following by removing the #.

Step 3 Enable IP Forwarding via ''sysctl''

Open the following folder

Add the following lines. This will allow IP forwarding for both IPV4 and IPV6

Press ESC + :wq to save and exit to /etc/sysctl.conf

Enable the changes using the following command

Step 4: Setup firewall

Please check firewall status using the following command

Default result should return the following

-P INPUT ACCEPT

-P FORWARD ACCEPT

-P OUTPUT ACCEPT

Add firewall rules for IPv4

Copy and paste the following commands

Add route for Belnet interface's IPv6

It is beneficial to block ports for Simple Mail Transfer Protocol (SMTP), SMTP over Secure Sockets Layer (SSL), SMTP over Transport Layer Security (TLS), Internet Relay Chat (IRC) and IRC over SSL. This is non-mandatory but may protect your exit node from Distributed Denial Of Service (DDOS) attacks. For more details, kindly check with your VPS host.

Now it is completed

Then, enter the following commands,

The above commands unroll to:

Make firewall settings persistent after rebooting the system by using the command given below

Select Yes on the pop-up window to save current rules to install both for IPv4 and IPv6.

Run Belnet

Step 5: Fetch your permanent .bdx address

Enter the following command to fetch your address

To check if your exit node is publicly hosted, enter the following command

Step 6: If you face any errors, you can troubleshoot your DNS using the following command

Open the resolv.conf file

Please add the following nameserver in the file

Save and exit the file using the command ESC + :wq

First, the wallet to be converted to multisig must be empty. It is best to use a brand-new wallet for the purpose, although not required. It is strongly advised to make a copy of the wallet files first, just in case something goes wrong.

Overview

In short, the process is:

Set-up

First, the wallet to be converted to multisig must be empty. It is best to use a brand-new wallet for the purpose, although not required. It is strongly advised to make a copy of the wallet files first, just in case something goes wrong.

Overview

In short, the process is:

Wallet Creation

First, the wallet to be converted to multisig must be empty. It is best to use a brand-new wallet for the purpose, although not required. It is strongly advised to make a copy of the wallet files first, just in case something goes wrong.

Overview

In short, the process is:

Wallet Creation

1. All parties command prepare_multisig and send data to ALL other parties

2. All parties command make_multisig <threshold> <data1> <data2> and send 2nd batch of data to ALL other parties

3. All parties command exchange_multisig_keys <data1> <data2> with the data from ALL other parties.

Receiving

1. All parties can type address to see the created multisig wallet address. The address will, of course, be the same for all parties since they're all watching the same wallet.

Preparation for Sending

1. To prepare for sending all parties command export_multisig_info <filename> and send the file to all other parties

2. To complete preparation, all parties command import_multisig_info <filename1> <filename2> and import files from other parties

Sending

1. To send, any party can use the usual transfer command, but the result will be a file named multisig_beldex_tx which must be sent to any 1 other signer

2. The other party commands sign_multisig multisig_beldex_tx and the file is updated with the signature.

Below is a step-by-step walkthrough.

Wallet Creation

Requirements:

• 3 empty beldex-wallet-cli wallets

• All parties wallets connected to a beldexd

• Confidential communication channel

Step 1 - Prepare Multisig

All 3 people should open up their beldex-wallet-cli and generate a new wallet. Make sure you do not have any $beldex within your wallet.

Person 1, 2 and 3 runs the following command within their beldex-wallet-cli:

The output will be something like:

Copy the entire line Multisig…...Vozid and be sure to capture the whole thing when copying.

Person 1 to send the Multsig...arg to Person 2 and 3, Person 2 to send their output to Person 1 and 3 and Person 3 to send their output to Person 1 and 2.

Step 2 - Make Multisig

All 3 persons now have the Multisig...arg text from the other 2. With that, each of them can create their part of the multisig wallet. Before you proceed, note that the wallet will lose access to the underlying wallet when converted to multisig. This is not really a problem, since we started with an empty wallet, and if all goes OK with this step, you won't ever need it unless you want to go through the process again for whatever reason (like HDD died, but you have the seed mnemonic of the underlying wallet and want to reconstruct the multisig wallet).

Person 1 commands:

Where <threshold> is the number of signers required out of the 3 people, <data person 2>is the output provided by Person 2, and <data person 3>is the output provided by Person 3.

This should look similar to:

Notice how there are 2 strings starting with Multisig....arg. One is from person 2 and other from person 3. The number at the beginning is the minimum required number of signatures. Since it's a 2/3 scheme - it's 2.

The output from the make_multisig command will be similar to:

With 2/3 there's an additional step to be done here. The new Multisig...arg info must be passed to ALL other participants (persons 2 & 3).

Persons 2 & 3 do the same as above and send the info to other 2 parties.

Step 3 - Exchange Multisig

Here we do one last command to make the wallet ready for receiving. It requires the 2nd batch of Multisig…....arg strings received from other parties.

Person 1 will run the command:

Unfortunately the wallet will not display an output at this point. There's no indication that the process was successfully completed (for now). All 3 persons do the same, and all 3 wallets will show the same address after this step.

Now each person run the command:

And each 3 parties of the multisig wallet should be shown the same address in their wallet.

Receiving

Step 1 Fund The Multisig Account

This is simple. Just send to the shared address. You can send multiple times, just like a normal wallet. You can use payment ID’s as well, or generate an integrated address to receive funds.

Best part, whomever is sending the funds won't be able to tell that the address belongs to a multisig wallet since it looks like any other Beldex address.

Step 2 Check Multisig Account Balance

Just open the wallet and run the refresh command . Once completed, all persons can verify that the funds arrived.

Person 1, 2 & 3 can run the command:

To see incoming transfers or the following command to see the balance of the wallet:

Preparation for Spending

Step 1 - Export Multisig

Without this step, it will not be possible to create a transaction that spends Beldex. As a minimum, the sender needs to get a partial key image from the same person who will sign the transaction with him later. He could get from both parties immediately and then later decide with whom to sign.

Person 1 commands:

Where mi1 can be any filename. The output will be:

The file mi1 will be located in the shell working folder*

Person 1 sends that file to other persons. Persons 2 & 3 do the same.

Optional: Step 1.2 Sending Multisig Info File with terminal - transfer.sh

It is optional to use the terminal to send each person the multisig info files.

UPLOADING MULTISIG INFO FILE

Person 1 will open up a new terminal and change to the directory mi1 has been saved.*

Person 1 will run the following command:

Person 1 will receive the link to the file as an output, looking similar to:

Person 1 will need to send this link to Person 2 and Person 3. Person 2 will need to do the same and send the link to Person 1 and 3. Person 3 will need to do the same and send the link to Person 1 and 2.

DOWNLOADING MULTISIG INFO FILE

Person 1 should change to the directory of their beldex-wallet-cli and use Person 2 and 3’s download link to run the commands:

Replacing <link> with the link Person 2 and 3 shared with Person 1 and <filename> with the filename of the Multisig info file that Person 2 or 3 generated, for example Person 1 will run the command:

And the command:

Likewise, Person 2 and 3 should do the same, changing directories to their beldex-wallet-cli and downloading with the alternative Persons download link, and filename.

Step 2 - Import Multisig

Now, they must all import each other's file so they can be ready to make a TX later.

For example, Person 2 commands:

The wallet will look for files in the shell working folder and if the files are found the output will look like:

Persons 1 & 3 do the same.

Spending

Step 1 - Transfer (Preparing Unsigned Transaction)

Any of the 3 persons can start a transaction, it doesn't matter. To avoid weird things from happening only do it for 1 transaction at a time. If anything weird happens, do the step 1 & 2 again to fix.

For example, let's say that Person 3 will make the TX.

Person 3 performs the usual transfer command:

The output will look like:

Check in the folder where you started beldex-wallet-cli from. There should be a file named multisig_beldex_tx.

Send the file multisig_beldex_tx to either person 1 or 2.

Person 3 will send the file multisig_beldex_tx to the Person 1 or 2. Person 3 can send this file through email or alternatively use the transfer.sh commands outside of the wallet:

If Person 3 chooses to use transfer.sh command to send the file to Person 1 or 2 they will receive a <link>.

Person 1 or 2 must finish the signature. Person 1 or 2 copies/downloads the file to the same folder from where he started (or will start) beldex-wallet-cli.

Person 1 or 2 can run the command to download the file to the beldex-wallet-cli directory.

Replacing https://transfer.sh/CJqnM/multisig_beldex_tx with the link provided by Person 3.

Step 2 - Sign Multisig

Let's say Person 2 was picked as the partner. He must finish the signature. Person 2 copies the file to the same folder from where he started (or will start) beldex-wallet-cli.

Then, Person 2 commands:

and they will be prompted to check it first:

If ok, answer Y, and the output will look like:

Step 3 - Submit Multisig

Finally, person with the signed file submits the transaction to the network by commanding:

There will be a confirmation prompt:

If ok, answer Y, and the transaction will be sent. The output will look like:

You can check its status by using the show_transfers command.

The person 2 could also send the signed TX to person 3, who could then submit it to the network himself.

If you want to make another one, you have to go back to preparation for spending step (sync the key images again).

The wallet will look for the files and export them to the folder from where it was started, ie where your command prompt / shell was when you called beldex-wallet-cli. It may or may not be the same folder as your actual wallet files or beldex-wallet-cli, depending on how you go about it.

For example, your wallet could be on some USB drive like f:\temp\, and your wallet software on c:\beldex\ and your shell working folder could be c:\.

If you remain in c:\ with the shell, you could start the wallet by its full path and specify the wallet file location:

Source:

Thinking of running a Beldex Master Node? Great! The guide below will help you configure a device with the necessary Master Node software packages, and stake $BDX to register the node on the Beldex network.

Note: This guide assumes some familiarity with the command line and running a Linux server. For a more detailed walkthrough, check out our full Master Node setup guide.

Operating system requirements

One of:

• Ubuntu 20.04 ("focal")

• Ubuntu 22.04.05 ("Jammy Jellyfish")

• Ubuntu 25.04.5 ("Noble Numbet")

Note: There are strict uptime requirements for Master Nodes. It is strongly discouraged to run a Master Node on a device that will not be continuously on-line. We recommend running your Master Node on a VPS with a reputable provider.

Firewall Configuration

If you are using a firewall then you should ensure that the following ports are open and reachable:

• Port 29089 (storage server to storage server)

• Port 29090 (client to storage server)

• Port 19090 (blockchain syncing)

Super Fast guide - New Master Node Setup

Configuring a new Beldex Master Node is pretty simple and straight forward. For running a Master Node you need to get your VPS's public IP address. The Master Node requies a public IP address. You cna get the public IP address of your VPS using the below command.

Copy your public IP address, you may require to add the IP address manually if the deb setup will not fetch your IP address automatically.

Run the below 5 commands on your Linux server (these commands will work on Debian and Ubuntu; modifications may be necessary for other Linux distributions):

The services will run via systemd as beldex-node.service, beldex-storage-server.service and beldet-router.service

Once the blockchain has synced to the server (which can take several hours, If sync from the beginning), your Master Node will be ready to be staked. You can use the beldexd status command to check the sync progress.

Express guide - New Master Node Setup

Step 1: Initial repository set-up

To add the Beldex repository, run the following commands.

Note: You only need to follow this step once, to set up the repository. The repository will subsequently be automatically updated whenever you fetch new system updates.

This first command installs the public key used to sign the Beldex Master Node packages:

The second command tells apt where to find the packages.

Then resync your package repositories with:

Step 2: Beldex Master Node configuration

To configure your Master Node, simply install the beldex-master-node package:

This will detect your public IP (or allow you to enter it yourself) and automatically update the /etc/beldex/beldex.conf configuration file with the necessary additional settings to run a Master Node.

Step 2: Belnet Status Check

Check whether your Belnet router setup is done correctly or not using the below command.

If the Belnet router is setup correctly you will get the message shown in the below screenshot.

If the Belnet router is not setup correctly you will get the error message as shown in the image below

The issue is because the public IP and port of your VPS is not set in belnet.ini file, so you need to set it manually, the file is located in the path /var/lib/belnet/router/belnet.ini . Add the IP address and port in the file as follows

Congratulations! Your Master Node is now ready to be registered and staked.

Staking your Master Node

Preparing your Master Node for registration

To prepare your master Node for registration, run the following command:

This will prompt you for some registration details, then output a registration command. Copy the output from this command in preparation for the next step.

Note: You can safely run this command multiple times if you change your mind about some of the registration questions before you submit the registration.

Staking and registering your Master Node

To stake and register your Master Node, open the Beldex Electron wallet. Make sure your wallet has a balance of at least 10,000 $BDX to meet the Master Node staking requirement (less if you're configuring a shared Master Node). Navigate to the Master Nodestab > Registration section, and paste the output from the above command, then click Register Master Node.

Done! Your staking transaction will now be submitted to the network. After a short delay, your Master Node will be registered and start contributing to the network (and receiving rewards!).

Checking registration status

You can easily check if your Master Node is registered on the network. First, connect to the VPS where the Master Node is running and run the following command to retrieve your Master Node's public key:

This will output a bunch of information about your Master Node, but there's one part we're interested in at this stage: The long string of random letters and numbers after the characters MN: . This string is your Master Node's public key, used to identify your Master Node on the list of registered and operational Master Nodes. Select and copy the public key (do not copy any of the surrounding information).

You can now jump onto , open the full list of active Master Nodes, and use Cmd+F/Ctrl+F to check if your Master Node's public key appears in the list.

Upgrading - For Existing Master Node

When a new release is available, upgrading is as simple as syncing your repositories:

Then installing any updates using:

Note that this will install both updated Beldex packages and any available system updates (this is generally a good thing!)

During the upgrade, the running instance of beldexd will be restarted to ensure that the updated beldexd is now active.

If, for some reason, you want to install only updated Beldex package upgrades, but not other system packages, then instead of sudo apt upgrade you can use:

Back-ups

Backing up your Master Node's secret key. Will allow you to easily recover or migrate your Master Node

Reveal MN secret key:

Restore from MN secret key:

Having trouble? Just .

Subaddress is what you should be using by default to receive Beldex.

Learn for what you are being paid

By providing a unique subaddress for each anticipated payment you will know for what you are being paid.

This use case overlaps with integrated addresses. Subaddresses are generally prefered for reasons outlined below.

Server Requirements

• Operating System: Ubuntu 18.04 or higher

• Storage: Minimum 40GB