How to use Hxify — the Hx GUI Wallet

Please note: this is an alpha version

The developers have been hard at work creating a stable version of the Hx GUI wallet. This wallet enables a convenient and fully secure way of transacting tokens. Currently, the alpha version will be used for testing purposes, and is not intended to be used for any store of value. With the help of the community, our hope is that any issues can be ironed out as soon as possible, which will speed up the release of the official version.

Thanks once again to Hybrid Network for putting together this guide.

Hx RC1 Testnet — GUI wallet alpha

This is the initial release (alpha) for Hxify, the GUI Wallet for Hx. This is a step by step guide show you through:

Creating a new wallet with default and postquantum addresses

Different sections in the wallet and their purpose

Entering a Stake pool on the Hx RC1 Testnet

Using the Hx RC1 Testnet faucet

Checking your transaction on the Hx Block Explorer

Ticket Purchasing

Hxify supports Mac OS, Windows, and Linux using Electron.

**Note**: Hxify has not been tested on various Linux flavors. Please report back with any issues on the integrated issue tracking page found on our GitHub (

Installing Hxify GUI wallet (alpha)

Visit the Hybrid Network GitHub. Navigate to the hybridnetwork/hxify repo and click Releases (

You’ll see a list of different versions of the GUI wallet. Please select the appropriate version based on your operating software. (Mac OS .dmg, Windows .exe, Linux .rpm).

After you’ve downloaded the GUI wallet installation file, open it and click Run.

**Note**: If you are currently running the hxd (Hx Daemon) and hxwallet through Command-line (CLI) in Terminal (Mac OS and Linux), or Command Prompt (Windows), you will need to use Ctrl+C to shut those processes down in each window you have open. This is because the GUI wallet incorporates the node and wallet. If you would still like to PoW mine on the testnet, you can resume hxd and hxwallet by referring to the Advanced level guides to staking and mining. This is an example of the error you would see with the wallet if you’re trying to run the Command-line node and wallet alongside the Hxify GUI wallet

Creating your Wallet

**Note**: This product is in alpha. If you have an feature ideas or questions please email, reach out to us on Keybase( If you have any bugs to report please submit an Issue in GitHub under Hxify(

After installation, open Hxify if it hasn’t already launched.

Select the Create New Wallet tab. Here you can name your wallet. Once we have completed the wallet setup, you will be able to select your new wallet by name through the Select Available Wallet tab. Once you have named your wallet, continue to the next step by clicking Create New Wallet below.

When the Create a Wallet window opens, you’ll notice there are two options near the top-right: New Seed and Existing Seed. Please write your Seed Words down and keep them safe. It is a good habit to instill for your own security.

If you did not make a Command-line (CLI) hxwallet as demonstrated in the Intermediate level guides, please continue with Hxify setup. If you would like to enter an Existing Seed from the CLI hxwallet, select that option. Existing Seeds can be imported by other entering the correct Seed Word or Hex.

There is a notice that pops-up if you attempt Copy to Clipboard. This is to discourage copying or taking a screenshot of your Seed Words, which could expose you to risk if saved to an unsecure computer. If you choose to continue, type “I understand” and click Confirm Seed Copy. Otherwise, click Continue after you have copied your Seed Words.

You are now able to input your Seed Words. When typing in your Seed Words, a list of suggestions based on your inputs will drop down as you are typing. Complete this section.

After entering the correct Seed Words, enter your private passphrase twice. You should also write your private passphrase down and keep it somewhere safe. Click Create Wallet.

At this time, you will see the wallet begin to sync with the Hx RC1 Testnet.

After syncing has finished, you will be prompted to enter your private passphrase again to generate your postquantum address and scan the testnet block chain for any other exisiting accounts (other public keys) created with this wallet. Enter your private passphrase and Submit.

Using Hxify’s GUI interface

Once you have opened your Hxify GUI wallet, you’ll notice there are 4 sections: Overview, Accounts, Transactions, and Tickets. Let’s breakdown and get a basic understanding of each section, and their purpose.


This is the main menu for Hxify. In the RC1 testnet you will be able to see available and locked Hx, recent transactions, and recent tickets. In the upper right there is an example of how your wallet history may be presented. This includes charts based on volume over time of your spendable and locked Hx, Ticket Purchase history and transaction history.


In your Accounts menu, you can see a record history of your default, postquantum, and imported accounts. The imported account is where rewards from Voting and original Ticket Price return until they are spendable (after 256 blocks). Descriptions for sub sections are available by clicking the information icon. Please see the Transactions menu to send and receive Hx.

**Note**: If you receive a transaction sent to your imported account and it seems that the imported balance has not been transferred to your default or postquantum account, please close Hxify as the wallet may have fallen out of sync with the blockchain.


The alpha has two available wallets. From the Transactions menu you can Send, Receive and check the History of your default and postquantum addresses. Within this section you can also see the fee size and size of your transaction in bytes. The History tab allows you to also filter based on types of transactions, Ticket life-cycle, and by age.

If you would like your public key address, go to the Receive tab, and select either default or postquantum. Your public address will be shown for default or postquantum depending on whichever you choose. Post Quantum transactions CAN be sent and received in the Hx RC1 Testnet.


Here is where you may register to participate in a Stake pool, check the status of a Ticket Purchase, active proposals, and Voting records. The Governance and Statistics tabs are to be added to and utilized. Governance would be where you may set your Voting preference within a Stake pool.

How to Purchase Tickets

**Note**: If you are not familiar with how staking works in Hx please refer to our How Staking Works article linked here:

Before you can participate in a Stake pool, you will need to select a pool from the drop-down menu on the Tickets → Purchase Tickets tab and enter an API key.

Currently we have a testnet Stake pool available, so visit the corresponding website that is listed in the description to sign up for the Hx Stake pool(

At the Stake pool landing page, you will need to sign up with an email and password.

After email verification and you’re logged in, go to Settings at the top. Highlight the API key.

Copy and paste the API key from the Stake pool site into Hxify under Tickets → Purchase Tickets.

Add this Stake pool to your wallet.

A pop-up window will appear and display your configuration for the Stake pool with a url, ticket address, script, and the percentage of the pool fee. This Stake pool’s fee is set to 5%.

Click the Add Stake Pool or Cancel button to return to the Purchase Tickets menu.

Unless you’ve already transferred Hx from your miner that we setup in RC1 Testnet Advanced Level guide, you are probably low on funds.

If this is a newly created wallet separate from your CLI wallet and you would like to send funds to either Hxify address, get your public key address associated from the Transactions → Receive menu as shown in the Transactions section of this guide. You can send Hx from the CLI wallet by using this code in your hxctl Terminal or Command Prompt:

hxctl -u user -P pass --testnet --wallet sendtoaddress wallethaddresshere amount

To use the testnet faucet by posting your public key address and hit Send. You’ll receive a confirmation with a transaction ID (txid). You can repeat this for 5 Hx every 50 seconds. The active faucet addresses are:

Faucet 1 (

Faucet 2 (

You can use the txid with the Hx Block Explorer to check whether your request for Hx from the faucet is Unconfirmed or Confirmed. The Hx Block Explorer can be found here (

If you would like to return to your wallet at this point, it should update soon showing the pending transaction.

Unfortunately we still have insufficient funds at this point based on the Ticket Price. Since we have already been mining on the testnet to keep the testnet secure, we can use the CLI code mentioned above to send enough funds to complete a Ticket Purchase.

Now that we have sufficient funds, you can choose the number of Tickets you would like to buy. There are settings to the right of the Purchase Tickets menu to change the Ticket Fee and txfee if you would like to, but it is not necessary.

If you would also like to turn on Automatic Purchase that can also be chosen in this menu. If you have spendable funds, this will trigger your wallet to purchase another Ticket when possible.

After you choose Purchase, enter your private passphrase.

In the next confirmation window, hit Cancel to complete your Ticket Purchase.

You have bought your first Ticket using Hxify on the Hx RC1 Testnet! You can check what stage of the Ticket life-cycle our Ticket is at by viewing the My Tickets tab.

Since the Stake pool manages the process from here in terms of broadcasting your Vote after selection from the Ticket Pool, you can confidently close your wallet without worrying about missing your chance to Vote and still be eligible for rewards by participating in Stake pool PoS on the Hx RC1 Testnet.

That is the Hxify GUI wallet (alpha) available for use on the Hx RC1 Testnet! Please report any bugs through GitHub’s integrated issue tracker at When reporting bugs please include as much information as possible, but not limited to the date, summary of the issue encountered, and suggested workaround.