Installing DigiVault for DigiAssets on Windows

This is a brief starter guide to get you going with a very early pre-release of DigiVault for DigiAssets, running from a Windows PC. There will be bugs, but there will also be much joy, excitement, enthusiasm, and you’ll hopefully learn a few things.

NOTE: This guide uses the DigiByte Testnet, so HDD / RAM requirements are very minimal at this point in time. Mainnet launch in future will no doubt differ.

There are 5x things you’re going to need:

  • Redis server
  • Git
  • Node.js
  • DigiByte Core Wallet
  • DigiAssets

To start with, download a Windows version of Redis, courtesy of Microsoft. I’ve been using this one myself because it’s the most recent and stable Redis server that comes with Windows executables. Grab the Redis-x64–3.2.100.msi from here:

Then, get yourself the latest version of Git:

You’ll also want to download version 8.11.3 of Node (node-v8.11.3-x64.msi):

Also then download the latest test version of DigiByte-7.17.1 (beta 5 right now). This is needed due to the fact the Testnet is now running Odocrypt, and the Testnet is what we’re going to be using:

WARNING: Do not use this build for anything but testing DigiAssets. You should not be using 7.17.1 on mainnet as of April 2019. We specifically set it to use Testnet later in this guide, but consider this a warning that this is not to be used with your main funds, and is only for Testnet.

Getting DigiByte Core ready

So once it’s downloaded, install 7.17.1

Launch the DigiByte Testnet version:

You’ll see it looks a little different when launching it, with the purple colors:

Loading up TestNet

Once it’s open, go in to Settings → Options → Open Configuration File

Open it in Notepad or Wordpad, and you want the contents to be as follows:

rpcuser=rpcuser
rpcpassword=rpcpass
rpcallowip=127.0.0.1
rpcport=14023
server=1
listen=1
txindex=1
deprecatedrpc=accounts
testnet=1
addnode=testnet-1.us.digibyteservers.io
addnode=seed2.digibyte.io

It should look like this:

Your digibyte.conf

This gets DigiByte ready to be used by the DigiVault on the Testnet.

Go to File → Save, so it saves the .conf file.

Relaunch DigiByte Testnet so that you can watch it sync up fully. On a mediocre PC it will probably take 5–15 minutes as of April 2019, depending on your CPU, internet connection etc

You may now close the DigiByte Testnet app, because DigiVault will automatically open it up itself.

On to the Redis-server.

Run the setup file, you’ll be fine to just mash the “Next” button a bunch of times, but you specifically want to install to the default directory, and add it to the PATH environment variable:

Add Redis to the PATH environment variable, it’s convenient for troubleshooting

If you install it to “C:\Program Files\Redis” then it will be automatically launched by DigiVault in the background, and you won’t have to do it manually each time you want to use DigiVault.

Install Git

Git is needed to get the latest parts of the DigiVault server. Install the latest version. When prompted, ensure you choose “Git from the command line and also from 3rd-party software”.

All of the other defaults are going to be fine, so just hit the “Next” button a bunch of times to complete the installations.

DigiVault time

Next, download the DigiVault zip from GitHub:

Click on “Clone or download” then click “Download ZIP”:

Once downloaded, you then want to extract it to %UserProfile%. Do this, push the WinKey + R and enter it in:

%UserProfile%

This will open Windows Explorer and show you a folder that contains your Desktop, Documents, Downloads, Pictures etc. Extract it here and it will put it into the “DigiVault-master” folder:

You’re almost there!

Keep this window open though because we’ll come back to it.

Getting node.js ready

Next, run through the installer for node.js

Installing Node.js

Just hit the “Next” button a bunch of times, the defaults will be fine.

Now, launch the node.js command prompt:

Then type:

cd DigiVault-master
npm install

This is going to get it prepped and ready to be run on your PC. This process will take another minute or two.

Now you can fire it up:

npm start

You’ll see it working away for a moment launching. If you’re prompted, you want to allow the Electron app through your firewall:

Allow this access out your firewall on both Private and Public networks

You’ll be greeted with the DigiAssets DigiVault:

Tell it to create a new wallet for you.

DigiVault will now load up a few things in the background, such as the redis server.

This is currently loading up the DigiByte Testnet in the background. After a few minutes while DigiByte loads the blocks in the background there, you’ll then see:

You’ll then be greeted with a QR code and a freshly generated address:

Copy this address and head on over to https://testnet-1.us.digibyteservers.io to get yourself some Testnet DigiByte.

These Testnet DigiByte are completely worthless in every sense, because people can generate their own blocks with Testnet DigiByte with basically zero effort. This is simply an easier and faster way for non-technical people to get them.

Paste your address in and hit Submit.

You should get a transaction confirmation. The Testnet DigiByte will take approx 60–90 seconds for this to show up in to your wallet.

Unfortunately at present DigiVault does not automatically notice when you’ve received the initial DigiByte so you need to close down DigiVault and reopen it 90 seconds later with “npm start” again. Give it a good few seconds to close off the redis-server and DigiByte Core Testnet before running that again.

It will take a few seconds to fire up DigiByte Core, redis-server and syncing the new testnet transactions. Once done, you’ll be greeted with a success window:

You are now ready to both issue DigiAssets, and you can also receive them on the address you funded earlier too.

I write interesting things about cryptocurrency, especially DigiByte